I am not entirely sure on this, but functionality for all
JES2 SYSOUTs
seems to have changed with our latest upgrade to z/OS 1.6
IIRC, it was around ESA 4.0.
-teD
Me? A skeptic? I trust you have proof!
--
For IBM-MAIN subscribe
Hate to reply to myself, but I was wrong and it appears
that the space is
truly only freed when a SYSOUT is coded as FREE=CLOSE.
Sorry, but even
though it separates the output to another entry, the space
is not freed
when purging or printing the output of a non-FREE=CLOSE
SYSOUT.
NOT true. It
In [EMAIL PROTECTED], on 11/25/2005
at 03:10 PM, Bruno Sugliani [EMAIL PROTECTED] said:
It cannot be freed because what you purge is a JOE ( Job Output
Element ) Unfortunately JOE belongs to JQE ( Job Queue Element ) and
the allocation (the number of trackgroups used by the JOE's) is
written
We're talking real spin-off data sets here, right?
The way I do it is with a started job (in other words: Give the STC a
jobcard) and putting JESLOG=(SPIN,'00:00') in the job card.
It looks a little strange via SDSF DA and ? and gives me a JESYSMSG and
JESMSGLG per day. Comes in mighty handy for
Hello:
For years, JES2 wouldn't release spool space allocated to a given job
until all of the job was purged - i.e. freeing SPOOL space seemed to be
an all-or-nothing proposition. I learned today that JES2 frees up
SPOOL space for spin-OFF SYSOUT data sets (FREE=CLOSE) as soon as
they're
-For years, JES2 wouldn't release spool space allocated to a given job
-until all of the job was purged - i.e. freeing SPOOL space seemed to be
-an all-or-nothing proposition. I learned today that JES2 frees up
-SPOOL space for spin-OFF SYSOUT data sets (FREE=CLOSE) as soon as
-they're printed or
On Fri, 25 Nov 2005 13:46:16 -0600, Hank Medler [EMAIL PROTECTED]
wrote:
-For years, JES2 wouldn't release spool space allocated to a given job
-until all of the job was purged - i.e. freeing SPOOL space seemed to be
-an all-or-nothing proposition. I learned today that JES2 frees up
-SPOOL space
On Fri, 25 Nov 2005 14:28:48 -0600, Hank Medler [EMAIL PROTECTED]
wrote:
On Fri, 25 Nov 2005 13:46:16 -0600, Hank Medler [EMAIL PROTECTED]
wrote:
-For years, JES2 wouldn't release spool space allocated to a given job
-until all of the job was purged - i.e. freeing SPOOL space seemed to be
-an
On Fri, 25 Nov 2005 14:28:48 -0600, Hank Medler [EMAIL PROTECTED] wrote:
Hate to reply to myself, but I was wrong and it appears that the space is
truly only freed when a SYSOUT is coded as FREE=CLOSE. Sorry, but even
though it separates the output to another entry, the space is not freed
when
On Fri, 25 Nov 2005 14:28:48 -0600, Hank Medler [EMAIL PROTECTED]
wrote:
On Fri, 25 Nov 2005 13:46:16 -0600, Hank Medler [EMAIL PROTECTED]
wrote:
-For years, JES2 wouldn't release spool space allocated to a given job
-until all of the job was purged - i.e. freeing SPOOL space seemed to be
-an
10 matches
Mail list logo
