What a coincidence. We IPLed a sandbox system this morning and saw a
similar problem with SSHD. It appeared to us that OMVS had not yet fully
initialized. Automation complained about SSHD, and several minutes later it
was (re)started manually with no problem. The original return code 255 may
just be a simple-minded representation of the -1 that Unix is famous for.
Our case plus the FTPD case has made us rethink the trigger for
OMVS-dependent tasks. For whatever reason, we have historically triggered
some of these tasks on TCP/IP initialization. But IP seems to come up
earlier than it used to--this was a 1.9 system. We're now looking at
triggering on this message:
BPXI004I OMVS INITIALIZATION COMPLETE
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
John Hooper
[EMAIL PROTECTED]
.COM To
Sent by: IBM IBM-MAIN@BAMA.UA.EDU
Mainframe cc
Discussion List
[EMAIL PROTECTED] Subject
.EDU BPXAS RC=255
01/31/2008 07:27
AM
Please respond to
IBM Mainframe
Discussion List
[EMAIL PROTECTED]
.EDU
We had an occurrence where BPXAS on behalf of FTPD ended with a return
code of 255. There were no error messages in SYSLOG or the log for BPXAS.
There were no software records in Logrec. It appears that it stopped as it
normally does but had this return code. Nothing appears to have failed. I
know very little about this process - it just works. Our AO product caught
the
return code and, of course, they want an explanation. Has anyone else seen
this return code or know where they are documented. I have looked on
IBMLINK, Google, and IBM-Main. Help!!
--
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
