I do not know the zPDT environment. However, my basic process is Before CANCEL or FORCE, take a console dump of the TSO ASID. Issue D GRS,C to see if there are any enqueues.
Look in SYSLOG for any messages. Once a cancel is issued, you will lose the info needed to determine the cause of the hang. Note - TSO accepted the logon it, it ran into an issue/event that prevented the process from continuing. Enqueues are the biggest contributor. Lizette -----Original Message----- >From: Scott Ford <[email protected]> >Sent: Nov 20, 2012 10:10 AM >To: [email protected] >Subject: TSO hang > >All: > >I am running on z/OS 1.12 on z/PDT and have encounted the TSO deadly enbrace >talked about in IBM's Reference Doc # >1379523 ...I have cancelled the userid as 'C U=SFORD', still avtive 10+ mins >lateter, issued a 'FORCE U=SFORD' and the >id finally ended. Tried to Logon same situation. How do I get TSO to accept >logons. > >Scott J Ford >Software Engineer >http://www.identityforge.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
