Hello, I have a little ghost between JES2 conversion and WLM inits...
Once upon a time... a system (SYS2) was IPLed, it lived in a sysplex and it had some WLM inits. IPL automation executed "$PXEQ" and four secs later appeared "*$HASP222 XEQ DRAINING". All seemed correct. Then, IPL automation continued. 15min later was executed "P TSS" and 6secs later the TSS ended. But... the scheduler of this sysplex (started in another system) continued sending jobs (without affinity) to execution and one of them was sent to IPLed system. ¿?. Then, the specified job was cancelled because JES2 couldn't create the security environment for the job to be converted due to TSS had been stopped. So, the problem seems to be related to job conversion phase. Chronology: =========== SYS2 04:00:50.71 BB200000 $PXEQ SYS2 04:00:54.54 *$HASP222 XEQ DRAINING SYS2 04:15:05.76 BB200000 P TSS SYST 04:15:11.47 JOB20327 $HASP100 IMED7401 ON INTRDR FROM STC11701 SYS2 04:15:11.54 JOB20327 TSS7181E End of Day - No Further System Access Allowed SYS2 04:15:11.55 JOB20327 $HASP313 IMED7401 JES2 IS UNABLE TO CREATE THE SECURITY ENVIRONMENT SECURITY PRODUCT RETURN CODE = 0000001C REASON CODE = 00000000 SYST 04:15:12.47 JOB20327 $HASP250 IMED7401 PURGED Thanks in advance Regards Chr. Blesa ---------------------------------------------------------------------- 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
