WAG time...
Are you sure that the debug server needs to be started? Have to looked to see if it's still running?
Did you even try the ENDDBGSVR command as recommended?
Did your admin defer the IPL this weekend? Perhaps some other changes, like PTFs.
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Koester, Michael
Sent: Tuesday, May 17, 2011 8:50 AM
To: midrange-l@xxxxxxxxxxxx
Subject: STRDBGSVR worked until last week
I, and the other developer, can no longer start the debug server with STRDBGSVR, either from within WDSCi or from the 5250 command line. Worked fine for both of us until last Thursday. SysAdmin can successfully run the command but does not arrive for an hour after I start, so I'd really like this function back.
When we try, we get the following:
strdbgsvr
Job 141463/MKOESTER/QB5ROUTER submitted to job queue QUSRNOMAX in library
QSYS.
Object QB5ROUTER in QGPL type *DTAQ deleted.
An error occurred using the control socket for the debug server.
Ownership of object QB5JOBLST in QTEMP type USRSPC changed.
Replaced object QB5JOBLST type *USRSPC was moved to QRPLOBJ.
Job 141464/MKOESTER/QSYSJOBD submitted to job queue QSYSNOMAX in library
QSYS.
The "An error occurred using the control socket for the debug server." is CPFAC14. Message detail is:
Cause . . . . . : The control socket used to communicate with the debug
server router function could not be used.
Recovery . . . : Using the WRKOBJLCK command, check to see which job is
holding a lock on object QSYS/QB5ROUTER, type *PGM. End all jobs holding a
lock and retry the ENDDBGSVR command.
The prescribed recovery is useless - no locks found, and we're not running ENDDBGSVR anyway...
Search of web has not yielded any answers. We've not been able to determine what changed to cause this. We're running v6.1
SysAdmin has not had time to pursue this yet, so I'm hoping to assist by tapping the wisdom of this list. Has anyone else encountered and conquered this?
Many thanks.
Michael Koester
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
