If you got the all available functions complete to shut down JES I would not be to worried about it. That is normal to see that when you do a D OMVS,ASID=ALL after BPXAS FORK SERVICE has been shutdown.
D OMVS,ASID=ALL BPXO040I 18.41.50 DISPLAY OMVS 454 OMVS 000E FORK SHUTDOWN OMVS=(00,FS) USER JOBNAME ASID PID PPID STATE START CT_SECS OMVSKERN BPXOINIT 002A 1 0 MRI--- 18.15.40 59.041 LATCHWAITPID= 0 CMD=BPXPINPR SERVER=Init Process AF= 0 MF=00000 TYPE=FILE Michael Saraco Systems Consultant Baer Consulting, Inc. Work - 507-526-2566 Cell - 507-525-0530 From: Mark Yuhas <[EMAIL PROTECTED]> To: [email protected] Date: 01/19/2008 11:05 PM Subject: Re: BPXOINIT shutdown failure I apologize for the lack of completeness: The only active address spaces were: DLF LLA VLF APPC JES2 OPSMAIN (CA OPS/MVS) I did cancel APPC but to no avail. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
