There are lots of symbols for SVC Dump dataset names.

One you might one to consider is 

&JOBNAME

Might help your Automation to focus the assignment easier.

Lizette

> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
> Jim Ruddy
> Sent: Friday, October 25, 2019 8:33 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SVC dump data set layout
> 
> See if IHAPRD has the the information you are looking for.
> 
> Jim
> 
> On Fri, Oct 25, 2019 at 7:31 AM Steve Horein <steve.hor...@gmail.com> wrote:
> 
> > Hi!
> > We have a nightly automated process to search the catalog for any SVC
> > dumps that may not have been processed during the course of the day.
> > Typically, IEA611I is the catalyst to start the post-dump processing,
> > such as creating an event in the Incident/Problem/Change system and
> > deleting the disk data set after successful copy to tape. There are
> > those occasions where a dump may occur where message automation is not
> > available, hence the search of the catalog.
> >
> > To assist our Operations staff in determining who owns the dump, as an
> > automation administrator, I am trying to devise a way to get some
> > information from the actual dump data set itself. From the name, I can
> > determine where and when, but not much else:
> > COM='DD NAME=SYS1.DUMP.&SYSNAME..D&LYYMMDD..T&LHHMMSS..S&SEQ'
> >
> > However, with the name, I can leverage some tools to open and read the
> > data set to get pertinent info. For example, this NetView PIPE recipe
> > can get what appears to be the TITLE and JOBNAME from the first record
> > at columns
> > 89 and 1151:
> > WINDOW PIPE QSAM SYS1.DUMP.CP66.D190419.T043130.S00001|TAKE FIRST 1
> > LINE|EDIT 89.100 1 "¢" NW 1101.8 N "¢" NW 1151.150 N|SPLIT AT "¢"|CONS
> > LINE|ONLY
> >
> > In place of guessing at the layout, I was wondering if there was some
> > (public) documentation describing possible dump layouts?
> >
> > Opening and reading seems to be the *simplest* approach given the
> > tools at hand. Invoking IPCS is an alternative, though the (NetView)
> > environment may not be too conducive. Submitting a batch job to invoke
> > IPCS is also an option, but working that into the automation procedure
> > seems a bit complicated too.
> >
> > Any other ideas?
> >
> > ----------------------------------------------------------------------
> > 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

Reply via email to