Thank you All for sharing thoughts on this topic! It seems this is an interesting topic. Keep fire!
> 在 2014年10月22日，12:45，Ed Gould <edgould1...@comcast.net> 写道： > > Anthony: > > I believe (but cannot prove) that there are *OTHER* reasons for the message. > Example: *NONE* of the jobs in my shop were started tasks (outside of inits > etc) yet I still (intermittently) got the message. I never did zero in on the > cause. Although a job ending might have caused it (like I said I never traced > it down) and since I was practically the only person that had all authority > to view jobs I didn't hunt for the cause too much as I had other problems and > intermittent issues were the least of my worries. > > Ed > > >> On Oct 21, 2014, at 11:14 PM, Anthony Thompson wrote: >> >> The JCT is a JES control block. That message is entirely appropriate. As you >> surmise, it is because the work unit has not been started under JES auspices >> (it was started before JES became the primary job entry sub-system, or >> deliberately afterwards with the SUB=MSTR parameter, or it's some spawned >> z/Unix process). >> >> There is usually a very good reason for that. The started task provides a >> service that is required before JES is available, or it's functionality is >> such that it doesn't need, or more particularly, want to rely on JES >> services, for whatever reason. It is entirely *WRONG*to think that such a >> started task might be better off started under JES purely for the >> convenience of being able to view it's job-log. I cannot begin to describe >> what a horribly bad idea that is. >> >> For such a started task (master scheduler initiated), you'll have to use >> whatever monitoring facilities it provides, or search SYSLOG / OPERLOG for >> messages it issues. z/Unix stuff has its own ideas about things. >> >> Ant. >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Alex Wang >> Sent: Wednesday, 22 October 2014 12:38 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: JCT is not available! >> >> Hi folks, >> I'm wondering if you guys met the message 'JCT is not available!' >> on the up right hand side in SDSF panel before? >> >> Recently, I tried to check a job log by entering 'S' in front of the job >> name in SDSF. >> >> However, the SDSF prevented me from browsing the job log by issuing a >> similar message listed above. >> >> I checked the manuals and found this explanation: >> >> JCT NOT AVAILABLE >> >> Explanation: Either the object has no job control table (JCT) or an error >> occurred trying to process the JCT for the object. >> >> User Response: Delete the command or type RESET on the command line. >> >> I have two questions. >> 1. Under what circumstance, will the job have no job control table? >> I'm thinking if we start a ST with SUB=MSTR, and the *MASTER* scheduler will >> manage the starting of the ST. Then there may be no JCT of that ST. >> Could you please share with me what's your opinion? >> >> 2. Is there any way/method to get the job log back? If my previous thinking >> is right, could I stop the ST and start it again without SUB=MSTR? >> >> I'm looking forward to hearing from you. Thank you very much! >> >> WXD >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send email >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
