× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



SysAdmin had a conversation with IBM -- They had seen this before and directed him to fix the permissions in the IFS root to allow *PGMR the proper authorities. Sorry I don't have more details, but I wanted to get this out there before anyone spends too much time on this.
Thanks again.
Michael

-----Original Message-----
From: Koester, Michael
Sent: Tuesday, May 17, 2011 9: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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.