Viewing the IEAOPTxx settings currently in use through RMF Monitor

IEAOPTxx is a PARMLIB member that significantly influences processing by WLM, SRM, and the Supervisor.

To view your active IEAOPTxx parameters, go to RMF Monitor II, select Option L (Program Library and OPT Information), and then choose Option 4. Alternatively, once you are in RMF Monitor II, you can simply type OPT on the command line to display all IEAOPTxx parameters.

From Option L, you can also view the LNKLSTxx, LPALSTxx, and IEAAPFxx lists.

                     RMF Monitor II Primary Menu                   z/OS V2R5 RMF

 Selection ===>                                                                 

                                                                                

          

   1 Address Spaces      Address space reports                                  

   2 I/O Subsystem       I/O Queuing, Device, Channel, and HFS reports          

   3 Resource            Enqueue, Storage, SRM, and other resource reports      

                                                                                

   L Library Lists       Program library and OPT information                    

   U User                User-written reports (add your own...)                 

                                                                                

           RMF Monitor II Library List and OPT Settings Selection Menu          

 Selection ===>                                                                 

                                                                                                                                                     

   1 Link list         LNKLSTxx - Link Library list                        (LLI)

   2 LPA list          LPALSTxx - LPA Library List                     (LLI LPA)

   3 APF list          IEAAPFxx - Authorized Program List              (LLI APF)

                                                                                

   4 OPT               IEAOPTxx - OPT Settings                             (OPT)

                                                                                

                                                                                

                             RMF - OPT Settings                    Line 1 of 41 

 Command ===>                                                  Scroll ===> CSR  

                                                                                

                         CPU= 12/ 12 UIC= 65K PR=   0         System= XXXX Total

                                                                                

 OPT: 00            Time: N/A                                                   

 -- Parameter --  - Default - -- Value -- Unit ---------- Description ----------

                                                                                

 ABNORMALTERM             Yes         Yes Y/N  Abnormal terminations in routing 

 ABSMSUCAPPING             No          No Y/N  Absolute, permanent MSU capping  

 BLWLINTHD                 20          20 sec  Time blocked work waits for help 

 BLWLTRPCT                  5           5 0/00 CPU cap. to promote blocked work 

 CCCAWMT                 3200        3200 usec Alternate wait management time   

 CCCSIGUR                  45          19 msec Min. mean-time-to-wait threshold 

 CNTCLIST                  No         Yes Y/N  Clist commands count individually

 CPENABLE                 0,0        5,15 %    Threshold for TPI (low,high)     

 DVIO                     Yes         Yes Y/N  Directed VIO is active           

 ERV                      500    50000/CB SU   Enqueue residency CPU Service/DP 

 FULLPRESYSTEM             No          No Y/N  System AS can preempt other work 

 HIPERDISPATCH            Yes         Yes Y/N  Hiperdispatch is desired/active  

 IFAHONORPRIORITY         Yes         Yes Y/N  Allows CPs to help zAAPs         

 IIPHONORPRIORITY         Yes         Yes Y/N  Allows CPs to help zIIPs         

 INITIMP                    0        1/F0 #    INITIMP value/DP for initiators  

 IRA405I             70,50,50    70,50,50 %    Fixed storage of <16M,16M-2G,tot 

The above information was copied from https://community.ibm.com/community/user/blogs/anthony-giorgio2/2020/04/02/viewing-your-current-ieaoptxx-settings

XCOM Data Transfer experiencing dataset contention

Recently, we encountered an issue where an XCOM data transfer from a production batch job was failing due to dataset contention. At first glance, this was puzzling—because the dataset involved was used by only this single job. This post walks through the root cause of the problem and the simple yet effective solution, with reference to JCL behavior.
 
Job Overview
 
The batch job in question consisted of the following steps:
 
Step 1 – Delete the dataset TEST.XCOM.FILE
Step 2 – Executes some COBOL program to create TEST.XCOM.FILE
Step 3 – Perform XCOM data transfer using TEST.XCOM.FILE
Step 4 – Send an email with TEST.XCOM.FILE as an attachment
 
Importantly, no other job uses TEST.XCOM.FILE.
 
So the natural question arises:
 
How can an XCOM data transfer run into dataset contention when the job that created the file is the one initiating the transfer?
 
 
The Unexpected Cause of Contention
 
The key lies in how XCOM handles data transfer requests.
 

The XCOM step has PARM='TYPE=SCHEDULE' which means it queues the file transfer request and ends the job step when the transfer request is queued. So, the XCOM step in the job (Step 3) does not perform the data transfer synchronously. Instead, it submits the transfer request to the XCOM started task and immediately completes. This allows the job to continue executing Step 4 without waiting for the actual data transfer to finish.

 
While Step 4 was running—sending an email and attaching TEST.XCOM.FILE—the XCOM started task attempted to access the same dataset to perform the transfer. At this point, the dataset was still held by the job in exclusive mode, resulting in contention and a failed transfer.
 
Why the Dataset Was Still Locked
 
This behavior is clearly explained in the JCL Language Reference Manual, specifically in Chapter 12.19 (DISP parameter).
 
Key points from the manual:
 

• Before a job starts, the initiator issues an ENQ (enqueue) for every dataset used in the job.

• The highest level of control required by any step determines the ENQ type:

• DISP=SHR → Shared (SHR)

• DISP=NEW, MOD, or OLD → Exclusive (EXCL)

• ENQs cannot be downgraded during job execution.

• The ENQ is released only at the end of the last step that references the dataset.

 
Since the job creates TEST.XCOM.FILE, it had exclusive (EXCL) control over the dataset.  Because Step 4 also references TEST.XCOM.FILE, the ENQ remains held until Step 4 completes.
 
As a result, when the XCOM started task attempted to transfer the file, the dataset was still exclusively locked by the job itself.
 
The Solution
 
The fix was straightforward:
 
✅ Move the XCOM data transfer step to the very end of the job.
 
By doing so:

• When the XCOM started task begins the actual transfer, the dataset is no longer held by the job.

• The transfer proceeds without contention.

 

From the JCL Language Reference Manual, Chapter 12.19 (DISP parameter):

DISP and ENQ: Before starting the first step of a job, the initiator requests control of all of the data sets in that job by issuing an ENQ for each of them, using the value specified for DISP to determine the kind of ENQ issued. The initiator issues the ENQ for each data set at the highest level required for that data set by any step of the job. For example, if all steps of the job request shared control of a specific data set (DISP=SHR) then the ENQ for that data set is requested as SHR. If, on the other hand, any step of the job requests exclusive control of a specific data set (DISP=NEW, DISP=MOD, or DISP=OLD), then the ENQ for that data set is requested EXCL.

The ENQ for each dataset is released at the end of the last step of the job referencing it. Since ENQs cannot be downgraded from EXCL to SHR, if one step needs the ENQ EXCL and a following step only needs it SHR, the ENQ is still issued as EXCL and held until the end of the last step which references that data set, at which point the ENQ is released entirely.

COBOL Binary search

We had a situation where we loaded a large VSAM file into memory to be searched by online CICS application. We encountered problems trying to emulate the VSAM START verb using COBOL SEARCH ALL verb when the key does not exist in the array. To get around this we had to write our own BINARY SEARCH in COBOL. 

The array which we are searching contains about 240,000 entries. 

We found that the hand coded BINARY SEARCH was significantly more efficient in terms of CPU usage than the COBOL "SEARCH ALL" verb. 

The code was modeled after KNUTH's binary search, see this link 

http://www.z390.org/contest/p21/P21DW1.TXT 

the key to maximizing the performance of the code below was to use PIC S9(8) COMP for all the binary fields. This avoids the check for binary overflow in the generated code. Also we used the compiler option TRUNC(OPT) to avoid the code generated to check for truncation. 

Note --> the IF statement after the PERFORM loop is to check for a "not found" condition. To emulate the VSAM START command we need to position the INDEX to the first row which is >= the search key. 

           MOVE +1                     TO BIN-LOW. 

           MOVE BCNTR-TCA1-ENTRIES-USED 

                                       TO BIN-HIGH. 

           PERFORM WITH TEST AFTER 

               UNTIL BIN-LOW > BIN-HIGH 

               COMPUTE BIN-RANGE = BIN-HIGH - BIN-LOW 

               COMPUTE BIN-MID = (BIN-RANGE / 2) + BIN-LOW 

               SET TCA1-INDEX          TO BIN-MID 

               EVALUATE TRUE 

                   WHEN TCA1-KEY (TCA1-INDEX) = SRCH-TCA1-KEY 

                       MOVE 1          TO BIN-RANGE 

                       COMPUTE BIN-LOW = BIN-HIGH + 1 

                   WHEN TCA1-KEY (TCA1-INDEX) < SRCH-TCA1-KEY 

                       COMPUTE BIN-LOW  = BIN-MID + 1 

                   WHEN OTHER 

                       COMPUTE BIN-HIGH  = BIN-MID - 1 

               END-EVALUATE 

           END-PERFORM. 

           IF TCA1-KEY (TCA1-INDEX) < SRCH-TCA1-KEY 

               SET TCA1-INDEX          UP BY +1 

           END-IF. 

Row-Value-Expression and Quantified Predicates in Db2

Row-Value-Expression in Db2

A row-value-expression allows you to compare multiple columns (or values) at once as a tuple. Instead of writing separate conditions for each column, you can group them together.

General Syntax

(COL1, COL2, COL3) operator (Value1, Value2, Value3)

·        Both sides must have the same number of values.

·        Data types must be compatible.

·        Comparisons are evaluated pair by pair.

·        If any comparison involves NULL, the result may be Unknown.

Operators Explained with Examples

1. Equality (=)

(COL1, COL2, COL3) = (100, 'X', 2000)

·       Row (100, 'X', 2000) → True

·       Row (100, 'Y', 2000) → False

·       Row (100, NULL, 2000) → Unknown

2. Inequality (<>)

(COL1, COL2, COL3) <> (100, 'B', 500)

·       Row (100, 'B', 500) → False (all equal)

·       Row (100, 'C', 500) → True (COL2 <> 'B')

·       Row (101, 'B', 500) → True (COL1 <> 100)

3. Less Than (<)

(COL1, COL2, COL3) < (100, 'B', 500)

·       Row (100, 'A', 500) → True ('A' < 'B')

·       Row (99, 'Z', 999) → True (99 < 100)

·       Row (100, 'B', 400) → True (400 < 500)

4. Greater Than (>)

(COL1, COL2, COL3) > (100, 'B', 500)

·       Row (100, 'C', 500) → True ('C' > 'B')

·       Row (101, 'A', 300) → True (101 > 100)

·       Row (100, 'B', 600) → True (600 > 500)

5. Less Than or Equal (<=)

(COL1, COL2, COL3) <= (100, 'B', 500)

·       Row (100, 'B', 500) → True (exact match)

·       Row (100, 'A', 500) → True ('A' < 'B')

·       Row (99, 'Z', 999) → True (99 < 100)

6. Greater Than or Equal (>=)

(COL1, COL2, COL3) >= (100, 'B', 500)

·       Row (100, 'B', 500) → True (exact match)

·       Row (100, 'C', 500) → True ('C' > 'B')

·       Row (101, 'A', 300) → True (101 > 100)

The detailed IBM manual can be found at the following link:

 https://www.ibm.com/docs/en/db2-for-zos/12.0.0?topic=predicates-basic-predicate#db2z_basicpredicate__fnocop

 

Quantified Predicates in Db2

A quantified predicate compares a value (or a row of values) against a set of values returned by a subquery (fullselect). It uses operators together with quantifiers like ALL, SOME, or ANY.

General Syntax

expression operator {ALL | SOME | ANY} (fullselect1)

(row-value-expression) operator {ALL | SOME | ANY} (fullselect2)

·       expression → single value compared against a column of values.

·       row-value-expression → tuple of values compared against multiple columns.

·       fullselect → subquery returning one or more values.

Behavior of Quantifiers

1. ALL

• True if the relationship holds for every value returned by the subquery.
• False if the relationship fails for at least one value.
• Unknown if no comparison is false, but at least one is unknown due to NULL.
• Special case: If the subquery returns no rows, the result is True.

2. SOME / ANY

• True if the relationship holds for at least one value returned by the subquery.
• False if the subquery is empty or the relationship fails for all values.
• Unknown if no comparison is true, but at least one is unknown due to NULL.

Examples

TBLA

COLA
1
2
3
4

TBLB

 

COLB	COLC
2	2
3	–

TBLC

COLB	COLC
2	2

Example 1: ALL

COLA > ALL (SELECT COLB FROM TBLB UNION SELECT COLB FROM TBLC)

·       Subquery returns {2, 3}.

·       Predicate is False for rows 1, 2, 3.

·       True for row 4 (4 > 2 and 4 > 3).

Example 2: ANY

COLA > ANY (SELECT COLB FROM TBLB UNION SELECT COLB FROM TBLC)

·       Subquery returns {2, 3}.

·       Predicate is False for rows 1, 2.

·       True for rows 3, 4 (3 > 2, 4 > 2 or 3).

Example 3: ALL with NULL

COLA > ALL (SELECT COLC FROM TBLB UNION SELECT COLC FROM TBLC)

·       Subquery returns {2, NULL}.

·       Predicate is False for rows 1, 2.

·       Unknown for rows 3, 4 (because of NULL).

Example 4: SOME with NULL

COLA > SOME (SELECT COLC FROM TBLB UNION SELECT COLC FROM TBLC)

·       Subquery returns {2, NULL}.

·       Predicate is Unknown for rows 1, 2.

·       True for rows 3, 4 (3 > 2, 4 > 2).

Example 5: Empty Result with ALL

COLA < ALL (SELECT COLB FROM TBLB WHERE COLB > 3

            UNION

            SELECT COLB FROM TBLC WHERE COLB > 3)

·       Subquery returns empty set.

·       Predicate is True for all rows (special case).

Example 6: Empty Result with ANY

COLA < ANY (SELECT COLB FROM TBLB WHERE COLB > 3

            UNION

            SELECT COLB FROM TBLC WHERE COLB > 3)

·       Subquery returns empty set.

·       Predicate is False for all rows.

The detailed IBM manual can be found at the following link:

https://www.ibm.com/docs/en/db2-for-zos/12.0.0?topic=predicates-quantified-predicate

REXX/JCL to Format DB2 Timeout, Deadlock, and Lock-Related Messages

Below is a simple REXX program and the corresponding JCL used to format the following DB2 messages:

DSNT376I - TIMEOUT

DSNT375I - DEADLOCK

DSNT501I - RESOURCE UNAVAILABLE

DSNI031I - LOCK ESCALATION

DSNJ031I - Unit of Recovery (UR) has written a high volume of log records without a commit or rollback

REXX code : DB2MSGFMT

/* REXX */

 "EXECIO * DISKR IN (FINIS STEM IN_REC."

 TMO_CNT = 0

 DED_CNT = 0

 RSC_CNT = 0

 UCM_CNT = 0

 ESC_CNT = 0

 CALL WRITE_HEADERS

 TRACE N

 DO I = 1 TO IN_REC.0

    IF SUBSTR(IN_REC.I,19,5) = '----' &,

       SUBSTR(IN_REC.I,47,5) = '----' THEN

    DO

       DT = SUBSTR(IN_REC.I,35,11)

       ITERATE

    END

    IF SUBSTR(IN_REC.I,20,8) = 'DSNT376I' THEN

    DO

       CALL EXTRACT_DATA

       CALL WRITE_TIME_OUT_DATA

       ITERATE

    END

    IF SUBSTR(IN_REC.I,20,8) = 'DSNT375I' THEN

    DO

       CALL EXTRACT_DATA

       CALL WRITE_DEADLOCK_DATA

       ITERATE

    END

    IF SUBSTR(IN_REC.I,20,8) = 'DSNT501I' THEN

    DO

       CALL CONCAT_LINES

       PARSE VAR BG_LN . 'CORRELATION-ID=' CORR1 .,

                         'CONNECTION-ID='  CONN1 .,

                         'LUW-ID='         LUW1  .,

                         'REASON'          RSN1  .,

                         'TYPE'            TYP1  .,

                         'NAME'            RSC1  .

       CALL WRITE_RESOURCE_DATA

       ITERATE

    END

    IF SUBSTR(IN_REC.I,20,8) = 'DSNJ031I' THEN

    DO

       CALL CONCAT_LINES

       PARSE VAR BG_LN . 'HAS WRITTEN '        CNT1  .,

                         'CORRELATION NAME = ' CORR1 .,

                         'CONNECTION ID  = '   CONN1 .,

                         'LUWID = '            LUW1  .,

                         'PLAN NAME = '        PLN1  .,

                         'AUTHID = '           AUTH1 .,

                         'END USER ID = '      USR1  .,

                         'TRANSACTION NAME = ' XTN1  .,

                         'WORKSTATION NAME = ' WST1  .

       CALL WRITE_UNCOMMIT_LOG_DATA

       ITERATE

    END

    IF SUBSTR(IN_REC.I,20,8) = 'DSNI031I' THEN

    DO

       CALL CONCAT_LINES

       PARSE VAR BG_LN . 'RESOURCE NAME = '    RSC1  .,

                         'LOCK STATE = '       STAT1 .,

       'PLAN NAME : PACKAGE NAME = ' PLN1 ':' PKG1   .,

                         'COLLECTION-ID = '    COLL1 .,

                         'CORRELATION-ID = '   CORR1 .,

                         'CONNECTION-ID = '    CONN1 .,

                         'LUW-ID = '           LUW1  .,

                         'THREAD-INFO = '      THD1  .,

                         'PARTITION-INFO = '   MSG1  ,

                         'ESCALATED'                 .

       CALL WRITE_LOCK_ESC_DATA

       ITERATE

    END

 END

 IF TMO_CNT > 0 THEN

 DO

    TMO_REC.0 = TMO_CNT

    "EXECIO * DISKW TMO (FINIS STEM TMO_REC."

 END

 IF DED_CNT > 0 THEN

 DO

    DED_REC.0 = DED_CNT

    "EXECIO * DISKW DED (FINIS STEM DED_REC."

 END

 IF RSC_CNT > 0 THEN

 DO

    RSC_REC.0 = RSC_CNT

    "EXECIO * DISKW RSC (FINIS STEM RSC_REC."

 END

 IF UCM_CNT > 0 THEN

 DO

    UCM_REC.0 = UCM_CNT

    "EXECIO * DISKW UCM (FINIS STEM UCM_REC."

 END

 IF ESC_CNT > 0 THEN

 DO

    ESC_REC.0 = ESC_CNT

    "EXECIO * DISKW ESC (FINIS STEM ESC_REC."

 END

 EXIT

 WRITE_TIME_OUT_DATA:

    TMO_CNT = TMO_CNT + 1

    TMO_REC.TMO_CNT = DT TM          || ','||,

                      STRIP(PLN1)    || ','||,

                      STRIP(CORR1)   || ','||,

                      STRIP(CONN1)   || ','||,

                      STRIP(LUW1)    || ','||,

                      STRIP(THRD1)   || ','||,

                      STRIP(PLN2)    || ','||,

                      STRIP(CORR2)   || ','||,

                      STRIP(CONN2)   || ','||,

                      STRIP(LUW2)    || ','||,

                      STRIP(THRD2)

 RETURN

 WRITE_DEADLOCK_DATA:

    DED_CNT = DED_CNT + 1

    DED_REC.DED_CNT = DT TM          || ','||,

                      STRIP(PLN1)    || ','||,

                      STRIP(CORR1)   || ','||,

                      STRIP(CONN1)   || ','||,

                      STRIP(LUW1)    || ','||,

                      STRIP(THRD1)   || ','||,

                      STRIP(PLN2)    || ','||,

                      STRIP(CORR2)   || ','||,

                      STRIP(CONN2)   || ','||,

                      STRIP(LUW2)    || ','||,

                      STRIP(THRD2)

 RETURN

 WRITE_RESOURCE_DATA:

    RSC_CNT = RSC_CNT + 1

    RSN1 = ''''||STRIP(RSN1)

    TYP1 = ''''||STRIP(TYP1)

    RSC_REC.RSC_CNT = DT TM          || ','||,

                      STRIP(CORR1)   || ','||,

                      STRIP(CONN1)   || ','||,

                      STRIP(LUW1)    || ','||,

                      RSN1           || ','||,

                      TYP1           || ','||,

                      STRIP(RSC1)

 RETURN

 WRITE_UNCOMMIT_LOG_DATA:

    UCM_CNT = UCM_CNT + 1

    UCM_REC.UCM_CNT = DT TM          || ','||,

                      STRIP(CORR1)   || ','||,

                      STRIP(CONN1)   || ','||,

                      STRIP(LUW1)    || ','||,

                      STRIP(PLN1)    || ','||,

                      STRIP(AUTH1)   || ','||,

                      STRIP(USR1)    || ','||,

                      STRIP(XTN1)    || ','||,

                      STRIP(WST1)    || ','||,

                      'HAS WRITTEN 'CNT1' LOG RECORDS'

 RETURN

 WRITE_LOCK_ESC_DATA:

    ESC_CNT = ESC_CNT + 1

    ESC_REC.ESC_CNT = DT TM          || ','||,

                      STRIP(PLN1)    || ','||,

                      STRIP(PKG1)    || ','||,

                      STRIP(COLL1)   || ','||,

                      STRIP(CORR1)   || ','||,

                      STRIP(CONN1)   || ','||,

                      STRIP(LUW1)    || ','||,

                      STRIP(THD1)    || ','||,

                      STRIP(RSC1)    || ','||,

                      STRIP(STAT1)   || ','||,

                      MSG1 'ESCALATED'

 RETURN

EXTRACT_DATA:

 CALL CONCAT_LINES

 PARSE VAR BG_LN . 'PLAN='           PLN1  .,

                   'CORRELATION-ID=' CORR1 .,

                   'CONNECTION-ID='  CONN1 .,

                   'LUW-ID='         LUW1  .,

                   'THREAD-INFO='    THRD1 .,

                   'PLAN='           PLN2  .,

                   'CORRELATION-ID=' CORR2 .,

                   'CONNECTION-ID='  CONN2 .,

                   'LUW-ID='         LUW2  .,

                   'THREAD-INFO='    THRD2 .

 RETURN

CONCAT_LINES:

 TM = SUBSTR(IN_REC.I,1,8)

 BG_LN = STRIP(IN_REC.I)

 C_NUM = SUBSTR(BG_LN,LENGTH(BG_LN)-2,3)

 DO J = I + 1 TO IN_REC.0

    IF SUBSTR(IN_REC.J,3,1) = ' ' &,

       SUBSTR(IN_REC.J,7,1) = ' ' THEN

       NUM = SUBSTR(IN_REC.J,4,3)

    ELSE

       NUM = '###'

    IF C_NUM = NUM THEN

    DO

       BG_LN = BG_LN || SUBSTR(IN_REC.J,20,69)

       I = J

    END

    ELSE

      LEAVE

 END

 RETURN

 WRITE_HEADERS:

    TMO_CNT = TMO_CNT + 1

    TMO_REC.TMO_CNT = 'TIME,'                ||,

                      'FAILING PLAN,'        ||,

                      'FAILING  CORRID,'     ||,

                      'FAILING  CONNID,'     ||,

                      'FAILING  LUW_ID,'     ||,

                      'FAILING  THREAD INFO,'||,

                      'HOLDING PLAN,'        ||,

                      'HOLDING CORRID,'      ||,

                      'HOLDING CONNID,'      ||,

                      'HOLDING LUW_ID,'      ||,

                      'HOLDING THREAD INFO'

    DED_CNT = DED_CNT + 1

    DED_REC.DED_CNT = TMO_REC.TMO_CNT

    RSC_CNT = RSC_CNT + 1

    RSC_REC.RSC_CNT = 'TIME,'                ||,

                      'FAILING  CORRID,'     ||,

                      'FAILING  CONNID,'     ||,

                      'FAILING  LUW_ID,'     ||,

                      'REASON,'              ||,

                      'TYPE,'                ||,

                      'RESOURCE NAME'

    UCM_CNT = UCM_CNT + 1

    UCM_REC.UCM_CNT = 'TIME,'                ||,

                      'CORRID,'              ||,

                      'CONNID,'              ||,

                      'LUW_ID,'              ||,

                      'PLAN,'                ||,

                      'AUTHID,'              ||,

                      'END_USER_ID,'         ||,

                      'TRANSACTION_NAME,'    ||,

                      'WORKSTATION_NAME,'    ||,

                      MESSAGE

    ESC_CNT = ESC_CNT + 1

    ESC_REC.ESC_CNT = 'TIME,'                ||,

                      'PLAN,'                ||,

                      'PACKAGE,'             ||,

                      'COLL_ID,'             ||,

                      'CORRID,'              ||,

                      'CONNID,'              ||,

                      'LUW_ID,'              ||,

                      'THREAD INFO,'         ||,

                      'RESOURCE NAME,'       ||,

                      'LOCK_STATE,'          ||,

                      MESSAGE

 RETURN

JCL to run the above REXX code

//DELETES  EXEC PGM=IDCAMS

//SYSPRINT DD SYSOUT=*

//SYSIN    DD *

  DEL 'USERID.DED.OUT'

  DEL 'USERID.TMO.OUT'

  DEL 'USERID.RSC.OUT'

  DEL 'USERID.UCM.OUT'

  DEL 'USERID.ESC.OUT'

  SET MAXCC=0

//*

//STEP01   EXEC PGM=IKJEFT01

//SYSTSPRT DD SYSOUT=*

//SYSOUT   DD SYSOUT=*

//IN       DD DISP=SHR,DSN=File that holds the DB2 master started task’s JESMSGLG output

//DED      DD DSN=USERID.DED.OUT,

//         DISP=(,CATLG,DELETE),

//         DCB=(LRECL=400,RECFM=FB),

//         SPACE=(CYL,(10,10),RLSE)

//TMO      DD DSN=USERID.TMO.OUT,

//         DISP=(,CATLG,DELETE),

//         DCB=(LRECL=400,RECFM=FB),

//         SPACE=(CYL,(10,10),RLSE)

//UCM      DD DSN=USERID.UCM.OUT,

//         DISP=(,CATLG,DELETE),

//         DCB=(LRECL=400,RECFM=FB),

//         SPACE=(CYL,(10,10),RLSE)

//ESC      DD DSN=USERID.ESC.OUT,

//         DISP=(,CATLG,DELETE),

//         DCB=(LRECL=400,RECFM=FB),

//         SPACE=(CYL,(10,10),RLSE)

//RSC      DD DSN=USERID.RSC.OUT,

//         DISP=(,CATLG,DELETE),

//         DCB=(LRECL=150,RECFM=FB),

//         SPACE=(CYL,(10,10),RLSE)

//SYSTSIN  DD   *

 EX 'USERID.REXX.LIB(DB2MSGFMT)'

/*

//*

//XMITIP  EXEC PGM=IKJEFT1B,DYNAMNBR=50

//SYSEXEC  DD DISP=SHR,DSN=xmitip.library

//DED      DD DISP=SHR,DSN=USERID.DED.OUT

//TMO      DD DISP=SHR,DSN=USERID.TMO.OUT

//RSC      DD DISP=SHR,DSN=USERID.RSC.OUT

//UCM      DD DISP=SHR,DSN=USERID.UCM.OUT

//ESC      DD DISP=SHR,DSN=USERID.ESC.OUT

//SYSPRINT DD  SYSOUT=*

//SYSTSPRT DD  SYSOUT=*

//SYSTSIN DD   *

%xmitip xxx.xxx@zzz.com +

        MSGT 'CSV files for DB2 log msgs' +

        From xxx.xxx@zzz.com +

        Subject 'csv files' +

        FILEDD (DED TMO RSC UCM ESC) +

        FILENAME (DED.CSV TMO.CSV RSC.CSV UCM.CSV ESC.CSV)

/*