Re: JCT is not available!
In 4454631278560122.wa.szwangxdgmail@listserv.ua.edu, on 10/21/2014 at 10:08 PM, Alex Wang szwan...@gmail.com said: 1. Under what circumstance, will the job have no job control table? STC under MSTR. If you control the source, you could dynamically identify the STC to the primary JES after it starts. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCT is not available!
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
Re: JCT is not available!
I don't know how your data center is configured, but here we regularly get JCT not available when we try to display anything about a job in a different JESPLEX. Apparently JES2 can't share that information across different JESPLEX's, even in the same SYSPLEX, and also not across different SYSPLEXes. HTH Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Alex Wang Sent: Tuesday, October 21, 2014 11:08 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 -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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
Re: JCT is not available!
I see this message routinely in two circumstances. 1. The 'job' is actually a started task running SUB=MSTR, i.e. not under JES. An STC can resemble a job if run from SYS1.STCJOBS, so look at it carefully. 2. The job has steps/tasks that run under OMVS. For example, my ShopzSeries orders always have 'steps' that store PTFs etc. into a ZFS. If I try to select one of those tasks, I get JCT NOT AVAILABLE. Meanwhile, there is at the same time another task in the job that can be selected to show what's going on. For case #1, there is no JOBLOG to recover. However, all messages are recorded in SYSLOG/OPERLOG. You can sift through it by STC number and collect the messages yourself. A bit cumbersome, but nothing is actually lost. For case #2, there is a JOBLOG that can be perused after the fact in the output queue. All messages are collected there ex post facto. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Alex Wang Sent: Tuesday, October 21, 2014 8:08 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
Re: JCT is not available!
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
Re: JCT is not available!
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- m...@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
