I hope you can help me out again, I seem to have borked something during the process.

FEKSETUP has ran correctly with no problems. I removed the testing statement and ran it again.
Created and modified start up procedures as described for JMON, LOCKD, and RSED.
Edited COMMONDB, LPALSTCI, and PROGDB as described in the guide.

When I went to run TSO OMVS to edit /usr/lpp/rdz/etc/rdz/rsed.envvars, everything fell apart on me.

FSUM2055I The OMVS command cannot use the message catalog.+ FSUM2056I Function = catopen(), catalog name = '/usr/lib/nls/msg/C/fsumucat.cat ', return value = -1, errno = 129 (X'00000081'), reason code = 0594003D, descrip tion = 'EDC5129I No such file or directory.' ... FSUM2319 No session was started.  The program to start the shell could not be in voked. Function = execl(), program name = '/bin/login', errno = 129 (X'00000081'), reas on code = 053B006C, message = 'EDC5129I No such file or directory.' ... FSUM2194I The end of the session was not recorded.  The recording program could not be invoked.+ FSUM2195I Function = execl(), terminal name = '/dev/ttyp0000', program name = ' /bin/fomtlout', errno = 129 (X'00000081'), description = 'EDC5129I No such file or directory.'

At this point I decided to IPL the system, and I'm getting some other oddball errors.

IEA712I LPALST LIBRARY DATA SETS IGNORED RDZUT.SFEKLPA                                 -UNABLE TO LOCATE

BPXI029I AN OMVS= PARMLIB MEMBER WAS NOT FOUND OR IS IN ERROR. IEA341A RESPECIFY OMVS PARM OR PRESS ENTER

@16.48.08 STC00027 @02 DFHPA1909   CICS     DATA /usr/lpp/cicsts/cicsts41 @ IS INVALID FOR KEYWORD USSHOME=. RESPECIFY KEYWORD AND DATA.

Vance,
You may have multiple problems. Check the syntax of your BPXPRMxx member that you updated for the RDz HFS. It looks like you may have corrupted something in the file when you edited it. Double check all edited members to ensure there are no extraneous characters. The message about LPA is likely because you need to ipl with a cold start to get the module loaded into LPA.

RDzJohn

Sorry to dig up an old post, but I'm seeing this error again right at the start of IPL.

IEA712I LPALST LIBRARY DATA SETS IGNORED RDZUT.SFEKLPA                                 -UNABLE TO LOCATE

When I do a cold start the message does not appear, but then restarting again into the DC operational mode it reappears.

Apologies for my daftness, but I'm assuming there is something I need to do during cold start operation to register the module into LPA so it works find in my normal IPL.

Thanks in advance for the assistance.
-Vance

Make sure the offending dataset, 'RDZUT.SFEKLPA' is contained in an LPALSTxx member pointed to by the IEASYSxx member you are using. Also make sure the phycial device where RDZUT.SFEKLPA resides is active and online in your configuration.

RDzJohn

Hi John,

I'm using DB to IPL my system, so inside ADCD.Z111S.PARMLIB(IEASYSDB), I see
000016 LPA=CI, SELECT LPALSTCI

So I added 'RDZUT.SFEKLPA' to ADCD.Z111S.PARMLIB(LPALSTCI), but the message still appears:

IEA712I LPALST LIBRARY DATA SETS IGNORED RDZUT.SFEKLPA                                 -UNABLE TO LOCATE

Make sure the dataset exists on the volume you expect it to be on. Make sure it is cataloged and that the volume is online. After you ipl you should be able to do a D PROG,LPA and you should see all of the datasets added to LPA. A D PROG,LNKLST will show you all of the datasets added to lnklst and those that are APF authorized. If you still make no headway, append your LPALSTCI member here.

RDzJohn