AW: Re: SUBSYS= ?
>... it is the interface that JES2 (and presumably JES3) use to provide DD* and >SYSOUT. Those have an implied SUBSYS=JES2/3 (even though coding it is >illegal). I have not really tried to find out how DD * and SYSOUT work under the covers. I was happy to understand OPEN does recognize it and prepares accordingly. SUBSYS=JESx makes sense. Duhhh, this just never occurred to me. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: SUBSYS= ?
>I don't think it is hidden information, I just found: >z/OS MVS Using the Subsystem Interface SA38-0679-00 >One chapter is called: Why Write Your Own Subsystem? Yes, it is well documented how to write your own subsystem, and it is well documented, what functions you can support. What is missing is the whole set of functions that you need to support in order to make your own support for DD SUBSYS=. That was once documented in an orange book. >Each subsystem can deliver support for SUBSYS= in the JCL to handle DD >statements if it is useful, like Panvalet, Librarian, LOGR and others >mentioned. They have to document the interface for their SUBSYS= JCL parameter. Yes. For me this is proof enough that the interface itself will not disappear anytime soon, or more probably, never. But it does not help to write your own code and that is what the OP wanted, I understood. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: SUBSYS= ?
>My comment about deprecation was limited to the SUBSYS= keyword. I saw from >other replies that Panvalet and Librarian use the keyword. Just to remember: z/OS MVS's system logger provides support for SUBSYS JCL keyword to read either logrec or SMF directly from the logstream: >From the z/OS MVS Tools and Service Aids manual: SUBSYS=(LOGR[,exit_routine_name][,'SUBSYS-options1'][,'SUBSYS-options2']) Specifies that processing of this DD is to be handled by the LOGR subsystem. The exit_routine_name is the second positional parameter and specifies the name of the exit routine to receive control from the LOGR subsystem. o Specify or use the default value to IXGSEXIT to use the log stream subsystem exit routine. o Specify IFBSEXIT to access records from the logrec log stream. See SUBSYS-options2 for logrec-specific paramters. o Specify IFASEXIT to access records from SMF log streams. See SUBSYS-options2 for SMF-specific parameters. I guess (I'm not a vendor) that vendors might get access to documentation related to SUBSYS= SSI function under some nondisclosure agreement or what ever. Curious to understand where the problems with SUBSYS= lie. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: Subsys not down while Shutdown
> Thanks Lucas & Lizette. I have terminated the Task from list and performed > the Load. > Now is systems is up and running fine. Great. Now that this has been sorted out, you should invest some time to find out what ought to be brought down before an IPL what not. Automation (if you're using automation) should know and do what is necessary, but you should be prepared for the case when something does not work as intended. There are tasks (STCs) that you better try to stop in the proper way, or you might get into troubles at next startup (e.g. DB2 which might need some long lasting recovery). On the other hand, there are some tasks which you really don't need to care about, and there are tasks which cannot be stopped at all. The list is depending on your setup and the products you use. It is also useful to have a list of tasks to start, and in what order, in case you need to perform an IPL manually. Again automation may fail to complete the startup for whatever reason. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
