Re: JES2/JES3 Difference
Gil,
To get a copy of the system log (syslog) to the output Q type in ("W
#" where # is the sysout class you wish to place the syslog).
Ed
On Jul 7, 2006, at 7:52 AM, Paul Gillis wrote:
Hi,
I am trying to determine if JES2 has a similar functionality to JES3.
The JES3 inish deck allows on a SYSOUT definition the keyword
TYPE=DSISO. This means that any spool dataset allocated with
TYPE=DSISO is allocated its own unique track allocation table. This
allows a dataset to be either printed or removed from the spool,
and then that spool space returned to JES3 for other use, before
the job concerned has terminated.
I can see that JES2 has a track allocation group but have not been
able to determine if it has the ability to allocate a unique group
for a specific sysout class.
Maybe I am barking up the wrong tree, but what I suspect, but have
not yet confirmed, is that SYSLOG accumulates in the spool until
JES2 is restarted. SDSF is only showing me a single dataset of
about 60,000 lines, but then also shows me that SYSLOG has almost
4,000,000 lines.
Regards,
Paul Gillis
Retired JES3 bigot, now JES2/SDSF apprentice.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2/JES3 Difference
On Fri, 7 Jul 2006 22:52:07 +1000, Paul Gillis <[EMAIL PROTECTED]> wrote: > >Maybe I am barking up the wrong tree, but what I suspect, but have not >yet confirmed, is that SYSLOG accumulates in the spool until JES2 is >restarted. SDSF is only showing me a single dataset of about 60,000 >lines, but then also shows me that SYSLOG has almost 4,000,000 lines. > It will accumulate under the same STC number until restart. But it will separate into different output groups (that can be printed, purged, offloaded, written to external writer, etc.) when the LOGLMT is reached (specified in IEASYSxx)or the WRITELOG operator command is manually issued. Even if the syslog is split off, SDSF will still show it as one continuous entity via the LOG command if the older logs are still in the spool. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2/JES3 Difference
> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of Paul Gillis > > I am trying to determine if JES2 has a similar functionality to JES3. > > The JES3 inish deck allows on a SYSOUT definition the keyword > TYPE=DSISO. This means that any spool dataset allocated with > TYPE=DSISO is allocated its own unique track allocation > table. This allows a dataset to be either printed or removed > from the spool, and then that spool space returned to JES3 > for other use, before the job concerned has terminated. Maybe something like //OUT DD SYSOUT=*,FREE=CLOSE,SPIN=UNALLOC is what you're looking for? -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2/JES3 Difference
JES2 - HASP JES3 - ASP JES2 is only half ASP! >>> [EMAIL PROTECTED] 7/7/2006 8:52:07 AM >>> Hi, I am trying to determine if JES2 has a similar functionality to JES3. The JES3 inish deck allows on a SYSOUT definition the keyword TYPE=DSISO. This means that any spool dataset allocated with TYPE=DSISO is allocated its own unique track allocation table. This allows a dataset to be either printed or removed from the spool, and then that spool space returned to JES3 for other use, before the job concerned has terminated. I can see that JES2 has a track allocation group but have not been able to determine if it has the ability to allocate a unique group for a specific sysout class. Maybe I am barking up the wrong tree, but what I suspect, but have not yet confirmed, is that SYSLOG accumulates in the spool until JES2 is restarted. SDSF is only showing me a single dataset of about 60,000 lines, but then also shows me that SYSLOG has almost 4,000,000 lines. Regards, Paul Gillis Retired JES3 bigot, now JES2/SDSF apprentice. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
JES2/JES3 Difference
Hi, I am trying to determine if JES2 has a similar functionality to JES3. The JES3 inish deck allows on a SYSOUT definition the keyword TYPE=DSISO. This means that any spool dataset allocated with TYPE=DSISO is allocated its own unique track allocation table. This allows a dataset to be either printed or removed from the spool, and then that spool space returned to JES3 for other use, before the job concerned has terminated. I can see that JES2 has a track allocation group but have not been able to determine if it has the ability to allocate a unique group for a specific sysout class. Maybe I am barking up the wrong tree, but what I suspect, but have not yet confirmed, is that SYSLOG accumulates in the spool until JES2 is restarted. SDSF is only showing me a single dataset of about 60,000 lines, but then also shows me that SYSLOG has almost 4,000,000 lines. Regards, Paul Gillis Retired JES3 bigot, now JES2/SDSF apprentice. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
