REXX LMDLIST fails with RC 8 after z/os1.7 upgrade

Jaco · Posted: Wed Dec 16, 2009 3:50 pm

Good day.

I need some assistance regarding a REXX LMDLIST issue that we started to experience after upgrading from z/OS 1.4 to z/OS1.7.

After the upgrade, LMDLIST with 'option(save)' failes with rc 8 when allocating the output dataset. The LMDLIST REXX looks as follows:
/* REXX * LMF-BEFEHLE FUER SEQUENTIELLE DATEIEN ********************/
TRACE ?R
L = 'ZA06417.**'
G = 'OOOOOO'
D = ' '
/*"CONTROL ERRORS RETURN" */
ADDRESS ISPEXEC
"LMDINIT LISTID(IN) LEVEL("L")"
SAY 'RC1: ' RC

ADDRESS ISPEXEC
"LMDLIST LISTID("IN") OPTION(SAVE) DATASET(D) STATS(YES) GROUP("G")"
SAY 'RC2: ' RC

ADDRESS ISPEXEC
"LMDFREE LISTID("IN")"
EXIT

The REXX works as normal on one of the other z/os1.7 lpar, so I am suspecting that it might be due to either a usermod or exit that is missing. It also works when a pre-allocated dataset is specified for the 'option(save)', which makes me believe that the allocation of the output dataset is causing the rc 8.

Can someone please assist and advise.

Thanks for your help and assistance in advance.

Regards

Jaco

MBabu · Posted: Wed Dec 16, 2009 3:59 pm

what message(s) does the SAVE command in DSLIST show?

ofer71 · Posted: Wed Dec 16, 2009 4:27 pm

Change "SAY 'RC2: ' RC " to "SAY ZERRSM ; SAY ZERRLM" to see the exact message, or use dialog trace options.

O.

Jaco · Posted: Wed Dec 16, 2009 4:55 pm

Thank you for the quick response.

I am getting the following error message:

13 *-* SAY ZERRSM
>>> "Data set not cataloged "
Data set not cataloged

ofer71 · Posted: Wed Dec 16, 2009 4:57 pm

I guess it's something with your PREFIX. Try to turn it on/off.

O.

PeterHolland · Posted: Wed Dec 16, 2009 5:15 pm

No dot between the *?

L = 'ZA06417.**'

dsname-level
You may use this value to specify the level or levels of data sets displayed with
the dslist ID. The dsname-level is a string containing valid TSO data set name
qualifier patterns, separated by periods (‘.’). You can use an asterisk as a
wildcard in the qualifiers. The LMDINIT service does not select data sets with
fewer levels than the dsname-level. You may also use an optional data set list
exit to control which data sets are included in the list.

Jaco · Posted: Wed Dec 16, 2009 5:33 pm

Turned the prefix on and off, but still the same error. I also found that if I am writing output to pre-allocated dataset, it works. So the problem seems to be related to the allocation bit of the dataset for the output.

PeterHolland · Posted: Wed Dec 16, 2009 5:44 pm

Turned the prefix on/off?
Did you code the dots between the * ?
Did you use a fully qualified name ?

With the little info you are handing out
resolving this will be a little hard.

You as MVS Systems Programmer should
know that.

Jaco · Posted: Wed Dec 16, 2009 6:14 pm

Turned prefix on - rc 8.
Turned prefix off - rc 8.
Used fully qualified name - rc 8.

Same REXX works on another z/os1.7 lpar. I am looking to see how the datasets gets allocated in ISPF.

Unfortunately I have no more details.

expat · Posted: Wed Dec 16, 2009 6:59 pm

Pedro · Posted: Wed Dec 16, 2009 8:28 pm

Can you allocate a dataset manually?

Does your userid have a prefix defined?

What is ZERRLM say? Issue MSGID ON prior to running.

Jaco · Posted: Wed Dec 16, 2009 8:56 pm

There does not seem to be an entry available on the system, as three different users have tried to do the list, but had the same issue.

The ZERRLM looks as follows:

11 *-* ADDRESS ISPEXEC

12 *-* "LMDLIST LISTID("IN") OPTION(SAVE) DATASET(D) STATS(YES) GROUP("G")"
>>> "LMDLIST LISTID(ISR00002) OPTION(SAVE) DATASET(D) STATS(YES) GROUP
(OOOOOO)"
+++ RC(8) +++

13 *-* SAY ZERRSM
>>> "Data set not cataloged "
Data set not cataloged

*-* SAY ZERRLM
>>> "'ZA06417.OOOOOO.DATASETS' was not found in catalog.

"
'ZA06417.OOOOOO.DATASETS' was not found in catalog.

I am suspecting that the problem is related to something to do with ISPF, but I hav done an ALLOC of a dataset using REXX and that worked without any issues.

Robert Sample · Posted: Wed Dec 16, 2009 8:57 pm

Wild thought -- could there have been a missed user catalog in the conversion? If you're trying to allocate a new file that should be in a user catalog, and that user catalog wasn't set up properly as part of the conversion, you could be attempting to write directly to the master catalog. This usually fails since the user catalogs are supposed to be used.

This would be a question for your site support group. There should be a security package message in the console messages indicating the problem if that is the source of your error.

MBabu · Posted: Thu Dec 17, 2009 7:32 am

also the wild thought crossed my mind that maybe there are some ISPF exits or ACS routine that are not working. There are exits that change names, usually used to add qualifiers with the lpar name or similar and I'm wondering of the data set is being created under a slightly different name.