MVSFORUMS.com

[Okonita]

Hello everyone, I am new to REXX and need help with a REXX routine for use to monitor my OS-390 DB2 DASD usage. I am having the following errors when I try to execute the REXX program:

(1) ALLOC DD(SYSPRINT) DSN("NULLFILE") SHR REUSE"
>>> "ALLOC DD(SYSPRINT) DSN(NULLFILE) SHR REUSE"
IKJ56228I DATA SET USERID.NULLFILE NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSE +++ RC(12)

(2) "CALL 'SYS1.LINKLIB(IDCAMS)'"
>>> "CALL 'SYS1.LINKLIB(IDCAMS)'"
+++ RC(16) +++

(3) 67 *-* "EXECIO * DISKR OUTDS (STEM X. FINIS"
>>> "EXECIO * DISKR OUTDS (STEM X. FINIS"

IRX0250E System abend code 002, reason code 00000004.
IRX0255E Abend in host command EXECIO or address environment routine TSO
IRX0670E EXECIO error while trying to GET or PUT a record.
+++ RC(20) +++

(4) 140 *-* "ISPEXEC TBERASE DASDMON"
>>> "ISPEXEC TBERASE DASDMON"
+++ RC(8) +++

(5) 253 *-* "ISPEXEC TBSKIP DASDMON"
>>> "ISPEXEC TBSKIP DASDMON"
+++ RC(8) +++

(6) 268 *-* ADDRESS ISPEXEC "PQUERY PANEL(DASDMON) AREANAME(SGDATA) DEPTH(DEPTH)
>>> "PQUERY PANEL(DASDMON) AREANAME(SGDATA) DEPTH(DEPTH)"
ISPP100 Panel 'DASDMON' error -/-Panel not found.

MVS OS reports the error as follows:

IEC036I 002-04,IGC0005E,AO11063V,ISPFBTCH,OUTDS, 7C05, SYSDA6,SYS05174.T160036.RA000.AO11063V.R0261902

Please let me know if you need additional information. I will be very grateful for any assistance in resolving this problem. If an example is available, that will be very very helpful.

Thanks

Okonita

[semigeezer]

Okonita,
The 1st error is because TSO is adding your TSO prefix. Treat NULLFILE as a regular data set name (be sure it resolves to being in single quotes). Alternatively, use the DUMMY keyword instead of DSN(NULLFILE). They mean the same thing.
Further information: read up on TSO PREFIX usage in TSO and ISPF. Also, check ALLOC command in TSO regarding DUMMY files.

The RC 16 frim IDCAMS is probably just a side effect of the previous error.
Further information: allocate SYSPRINT to DA(*) instead and read the messages. If this is running in batch, just allocate SYSPRINT to SYSOUT=* directly in the JCL and read the output in SDSF.

RC8 from ERASE and TBSKIP probably is OK. It just means the table doesn't exist and you are at the bottom of the table respectively.
Further Information: ISPF Services Guide

PANEL NOT FOUND: If this is batch, your JCL probably has the wrong libraries allocated to ISPPLIB. If this is foreground, you need to add a LIBDEF for ISPPLIB.
Further info: ISPF Developer's Guide and maybe the ISPF Customization guide

IEC036I could be anything based on the previous errors, but ...
Further information: look up the message id and abend code in the MVS Messages and Codes books

I suspect someone here could help with the exact problems, but these skills are something you will need in almost everything you do in MVS, so I'd strongly suggest learning about them. Once the small stuff like this is understood, using MVS can become rather fun.