That sounds good, Mark, but I don't have the advantage of the level of
automation you seem to have. If I can't get it via JES2 Automatic
Commands or MPF exits, I just plain ain't got it. But a MPF exit to stop
the External Writer when it goes idle doesn't seem like much of a
challenge. :-)
I have one "advantage": in my three-system Basic Sysplex, each system's
SYSLOG goes to a different class, L, M, or N, so I can at least maintain
some degree of separation.
Our job streams that might benefit from automation are constructed so
that each job, when completed normally, submits the next job in the
stream via IEBGENER from the "JOBS" PDS to the internal reader. Reports
are routed to desktop printers as appropriate via TCP/IP. (I don't yet
know all the details here, so forgive me for being a bit vague.) The
first job in each stream is submitted by a JES2 Automatic Command that
starts the process as a specific time.
I'm doing part-time consulting in a university environment, in return
for free access to the system for my own development work (on RACF
reporting tools and ARCHIVER upgrades). But I can't be more specific
than that, because of an agreement with management.
Rick
----------------------------------<snip>------------------------------
Automation does the writelog command at midnight and starts an STC. That
STC is an external writer that picks up the syslog from class L (which
is unique to syslog output in the spool) and writes the syslog to a disk
GDG. After the "idle" message from the external writer, automation stops
the external writer. The next step in STC copies the disk gdg to a tape
GDG. In sysplex environments, one of the LPARs is chosen per sysplex to
have additional steps to dump the operlog to disk and copy to tape. The
GDG limit controls the retention of disk files, tape may be controlled
by GDG limit an / or tape mgmt system retention period control (may not
be the same everywhere). In a few of the LPARs, the disk GDG retention
is set more than 3 or 4 GDGs but HSM migrates those to ML1 (the GDG
limit is not high enough to where they ever end up on ML2). This is
quicker than recall from virtual tape that is not in the buffer.
Oh... in shared spool environments the writelog / STC only executes on
one LPAR and I have a REXX exec I wrote that splits off the syslog into
separate LPARs. This was so we didn't have to dedicate a different class
per LPAR for the syslog. Back in "the day" output classes were hard to
come by.
-----------------------------------<unsnip>-----------------------------
---
Query: why didn't Noah swat those two mosquitoes??
----------------------------------------------------------------------
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
