Messages

16

z/OS Server / Re: ODF Customized e-mail Subject

« on: January 24, 2020, 07:05:56 AM »

It's been in production since Christmas.  Working as we use it.  We caught it in v9.5 first.  While it was in the works at IBM we upgraded one of our instances (we support multiple CMODS on One LPAR) and the same issue was in v10.1.  IBM Tech support said that the APAR would be for both version.

17

z/OS Server / Re: ODF Customized e-mail Subject

« on: January 23, 2020, 09:29:41 AM »

Nice to see others are using that functionality.  That APAR was ours.  We changed Java from 7 to 8, being that it was being unsupported.  The "recipient" check was not getting hit any longer.  Glad we could expedite your implementation.  We waited 4+ months for the fix.

18

z/OS Server / Re: System log Timestamp extraction from UTC to EST

« on: January 03, 2020, 01:37:48 PM »

Two options:
1) upgrading the system log will add a DB2 timestamp in addition to the CMOD timestamp.  Makes life much easier.  We support multiple CMODS. I haven't upgraded it, but when building a NEW instance it is defined that way.
2) In addition to the "System Log" there is a "System LOAD" AG.  Seeing that you are looking at 87 records, that is exactly what it has in it.  Again with DB2 timestamps.  It break out the TEXT into separate columns.

19

z/OS Server / Re: ARS1109E Unable to allocate enough memory

« on: June 04, 2019, 12:24:10 PM »

have you looking into this exit on your LPAR?  We have gotten bit with it before.

IEFUSI — Step Initiation Exit

z/OS MVS Installation Exits
SA23-1381-00


Topics for This Exit Appear as Follows:

Comparing IEFUSI with IEALIMIT when Limiting Region Size
Defining the Exit in SMFPRMxx
Controlling the Exit Routine Through the Dynamic Exits Facility
Exit Routine Environment
Exit Recovery
Exit Routine Processing
Programming Considerations
Entry Specifications
Registers at Entry
Parameter Descriptions
Return Specifications
Registers at Exit
Examples
Example of Using IEFUSI to Limit Region Size
Examples of Storage Allocations Based on Values Set by IEFUSI

20

z/OS Server / Re: ODF Banner Exit performance on V10.1

« on: May 16, 2019, 01:30:12 PM »

Something to look forward to - Not.  The ARSBANNER seems to be the worst part of the last couple of upgrades.

21

z/OS Server / Re: System Log query

« on: May 16, 2019, 01:28:31 PM »

I would probably go with jsquizz's recommendation.  Using ARSDOC to retrieve the data transcends the various Segments associated to the System Log.  If you are looking at LOAD data (87 records), then you could build the SYSTEM LOAD application group.  (similar to building the system log).  It very nicely breaks out the data for type 87 records.

22

z/OS Server / Re: CICS Client configuration non-zero port

« on: May 03, 2019, 01:24:30 PM »

One way I was playing around with the same thing is to write a simple program.  This program would just provide the specifics based on how it was invoked.  You won't be able to use ARS1 for both instances anyway.

File  Edit  Edit_Settings  Menu  Utilities  Compilers  Test  Help
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
VIEW       DSYS.OLTP.TEST.SOURCE(ARSRMDS) - 01.03          Columns 00001 00072
Command ===>                                                  Scroll ===> CSR
003100 003100 77  FILLER PIC X(27) VALUE 'ARSRMDS - WORKING STORAGE>'.
003200 003200 77  WK-REFRESH-INTERVAL       PIC  X(2)      VALUE SPACES.
003210 003210 77  WS-OND32T-IP      PIC  X(25) VALUE 'ARS1 xx.xx.xx.xxx:4632'.
003220 003220 77  WS-OND32P-IP      PIC  X(25) VALUE 'ARS1 xx.xx.xx.xx:1445'.
- - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 19 Line(s) not Displayed
005510 005510     EVALUATE EIBTRNID
005600 005600         WHEN 'O32T'
005610 005610             EXEC CICS
005700 005700                 RETURN
005800 005800                    TRANSID('ARS1') INPUTMSG(WS-OND32T-IP)
005810 005810                    IMMEDIATE
005900 005900             END-EXEC
005910 005910         WHEN 'O32P'
005920 005920             EXEC CICS
005930 005930                 RETURN
005940 005940                    TRANSID('ARS1') INPUTMSG(WS-OND32P-IP)
005941 005941                    IMMEDIATE
005950 005950             END-EXEC
005951 005951         WHEN OTHER 

23

z/OS Server / Re: Too many tables in Appl. group

« on: October 16, 2018, 01:57:07 PM »

As Greg had said, we have collapsed tables.  Can give you details if needed.  Something else we did was to generate a report of how frequently Application Group Segments we being created by CMOD.  Creating too many active will cause this problem as well.  Throwing multiple Application Groups in one folder speeds up the process too.
Sizing the "Maximum Rows" properly goes a long way.  Our general rule of thumb is a Segment per Year's worth of index records.  This also depends on how long you are retaining them.  That way, proper growth is manageable.

fyi:

003400   SELECT
003500       SUBSTR(NAME,1,10)       AS AG_NAME      ,
003600       SEG.AGID  ,
003800       TABLE_NAME,
003900       DATE(START_DT) AS START_DATE,
004000       DATE(CLOSED_DT) AS CLOSED_DATE,
004100       DAYS(CLOSED_DT) - DAYS(START_DT) AS DAYS_TERM
004200   FROM OND03P.ARSSEG SEG, OND03P.ARSAG  AG
004300   WHERE
004400       SEG.AGID = AG.AGID AND
004500       (DAYS(CLOSED_DT) - DAYS(START_DT)) < 200 AND
004600       DATE(CLOSED_DT) > DATE(DAYS(CURRENT DATE) - 90)
004610   ORDER BY AG_NAME, TABLE_NAME;

24

z/OS Server / Re: Manifest print style

« on: June 13, 2018, 08:46:22 AM »

J9,
    Do you customize your Banner and Manifest programs?  The Banner is invoked multiple times and can place the banner at the end.

One of the problems we had with the Manifest is the fact that "assumptions" were made by IBM.  We deal with reports of varying widths (80-133, with others).  I believe they changed the manifest to always print 80.  The spooled output DD was also assumed at one point (the LRECL).
The other thing was the "assumption" that all reports are ANSII printer controls.  Old Cobol programs (can) generate Machine Printer codes.  The Banner program IS passed the RECFM of the Spooled DATASET.  This allowed the Banner for Force a Page Break by added a TOP-OF-FORM character, as needed.  If your Bundle is mixing and matching, that would cause this issue.  The Manifest program was NOT passed the RECFM and could NOT put out a Machine TOP-OF-FORM character. 
Part of the fix from IBM that Greg mentioned changed the communication area passed to the Manifest to include the RECFM of the spooled Dataset.  That way the manifest could intelligently output the correct top-of-form character for the Reports being printed.

25

z/OS Server / Re: ODUG CMOD 10.1 Presentation question

« on: May 08, 2017, 06:51:20 AM »

Thanks for the clarification Ed.
The same code you displayed was a proposed solution, from IBM, for our problem.  The problem with it is that spooling out 3 different DDs (first banner, report, trailing banner) there is no way to insure that the printer actually prints them TOGETHER and IN THAT ORDER.  They come out at the discretion of the printer (size for example).  When sending those 3 separate spooled outputs to another LPAR, forget keeping them together as well.  As long as it is an OPTION and we can still have the spooled output in ONE SYSOUT, that's OK.

26

z/OS Server / Re: UDUG CMOD 10.1 Presentation question

« on: May 04, 2017, 12:42:57 PM »

actual screen shot from presentation.

27

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 12:24:27 PM »

We've had that too.  Is the original report defined in CMOD as VB?  does it need to be?  When ODF outputs VB reports, it seems to use the Maximum record length - for VB, that's about what it is.  If that is the case and it isn't avoidable, I've used one of our INPUT EXITS.  When using OS/390 and an INPUT EXIT, I could force the second Application to 133, FB. (the hoops we jump thru).
Another way of accomplishing the same thing would be to define 2 output cards in the JCL and send one copy to one application group and another copy to the other.  That way it won't matter.  May have to coordinate with JCL prod control people though.

//HSC125MH OUTPUT NAME='XXXXXXXXX',
//         FORMDEF=S0S00,PAGEDEF=SP1B    < WRITER=P11B >
//HSC125DM OUTPUT NAME='XXXXXXXXXX',
//         FORMDEF=S0S00,PAGEDEF=SP1B    < WRITER=P11B >
//HSC125A  EXEC EXEZTP,MEMBER=HSC125
//STEPLIB  DD  DSN=CORPL.HLTHSVCS.BTCHLOAD,DISP=SHR
//BSPWNERR  DD  SYSOUT=*
//CNTLCARD  DD  *
ALLB240        YDN0099N
//PRTFILE   DD  SYSOUT=(J,P11B),
//         OUTPUT=(*.HSC125MH,*.HSC125DM)

28

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 11:18:38 AM »

If you haven't used "full report browse" before, you need to click on a new button on the right side of the screen: "View Full Report".  This is just an OPTION made available to the user.  They will always need to pick the new button (annoying, probably).

Another thought.  When loading the report and breaking on it, you could use ODF to send the report back out to the spool and RELOAD it into another Application group.  That second AG won't have the breaking.  We have done that to overcome various challenges.

29

z/OS Server / ODUG CMOD 10.1 Presentation question

« on: May 04, 2017, 10:25:57 AM »

We had downloaded the ODUG presentation and I went thru it.  Is there anyone at 10.1 that uses ODF's Banner?  On one of the slides (forgot what page) under "SERVER:Miscellaneous", there was a BRIEF reference to ODF, "Banner in separate SYSOUT dataset".  I'm hoping that will be an OPTION like the option for the Manifest to be either/or.

One of the "fixes" that IBM tried to do for us, related to the Banner, was to not have the Banner/Report/Banner/Manifest in the SAME SYSOUT dataset. That didn't go well and they ultimately had to fix is so it was in the SAME SYSOUT.

Any thoughts would be appreciated.

30

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 10:04:02 AM »

If I understand you correctly, it sounds like you are "Breaking" on your Indexed field.  That is where your multiples are coming from.  If you are hiding that field because the user doesn't want it any longer, going forward you should remove that.  What we have done is to rename the original Application group and remove the BREAK on the new one that has the original name.  You would then make sure both applications are in the same folder.

With duplicate records (because of BREAK=YES), each record in the folder view display that you select will only display that part of the report, unless you have the "full report Browse" feature.  There are options to remove duplicates by entering a "Query Restriction" within the Application group.