Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of retired mainframer
Sent: Tuesday, August 21, 2018 2:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JES2 Spool Data Set Browse (SDSB) sample
It sure would be nice to know which suggestion was so awesome
> -Origi
It sure would be nice to know which suggestion was so awesome
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Chris Cantrell
> Sent: Tuesday, August 21, 2018 12:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2 Spool Data Set Br
This works awesome!
It is what I ended up using.
Thanks for everyone's comments.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
I have written some REXX to inventory all running jobs and STCs on a given LPAR
and search for certain messages in the JESMSGLG DD for each job/STC. This
Redbook provided helpful examples: Implementing REXX Support in SDSF.
--
please excuse the brevity.
> Original message From: Paul Gilmartin <
> 000433f07816-dmarc-requ...@listserv.ua.edu> Date: 8/19/18 4:21 PM
> (GMT-05:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 Spool Data Set
> Browse (SDSB) sample
> On Sun, 19 A
(GMT-05:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 Spool Data Set
Browse (SDSB) sample
On Sun, 19 Aug 2018 12:51:54 -0700, Ed Jaffe wrote:
>
>It's pretty trivial if you already know how to do allocation via SVC99.
>Looking at (E)JES code, I see we use the following keys:
On Sun, 19 Aug 2018 12:51:54 -0700, Ed Jaffe wrote:
>
>It's pretty trivial if you already know how to do allocation via SVC99.
>Looking at (E)JES code, I see we use the following keys:
>
>DALRTDDN (let the system choose DD name)
>DALDSNAM (owner.jobname.jobid.dsnum.dsname)
>DALSTATS (SHR)
>DALSSREQ
On 8/19/2018 12:51 PM, Ed Jaffe wrote:
DALSSREQ (technically only needed for secondary JES)
Actually, I think it's probably required for spool browse and optional
when submitting to internal reader.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 902
On 8/16/2018 7:00 AM, Chris Cantrell wrote:
We are on release 2.2. I am wanting to read the JCL in the first step of the
job and perform very specific (which may change) verifications to the JCL and
abend the job if the 'standards' are not met.
It's pretty trivial if you already know how to d
On Sun, 19 Aug 2018 13:56:41 -0400, scott Ford wrote:
>You can in Rexx and SDSF , we do it via our DevOPS process we use from
>bitbucket where our source and CI processes are stored.
>It takes some work..but works well,
>
There are some examples at or about:
https://www.ibm.com/support/knowle
You can in Rexx and SDSF , we do it via our DevOPS process we use from
bitbucket where our source and CI processes are stored.
It takes some work..but works well,
Scott
On Thu, Aug 16, 2018 at 3:13 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Thu, 16 Aug 2018 1
On Thu, 16 Aug 2018 11:26:14 -0500, Kirk Wolf wrote:
>
>You don't need to use the SSI to read a spool data set, although you do
>need a way to get the JES SSID and jobid (like from the current JSAB).
>
>It is not too complicated: you just allocate it using SVC99 (and some
>special purpose keys) and
: Re: JES2
Spool Data Set Browse (SDSB) sample
Didn't the OP want to change the dataset?
CharlesSent from a mobile; please excuse the brevity.
Original message From: Kirk Wolf
Date: 8/16/18 11:26 AM (GMT-06:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:
JES2 Spool Dat
Didn't the OP want to change the dataset?
CharlesSent from a mobile; please excuse the brevity.
Original message From: Kirk Wolf
Date: 8/16/18 11:26 AM (GMT-06:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:
JES2 Spool Data Set Browse (SDSB) sample
On Thu, Aug 16, 2018
On Thu, Aug 16, 2018 at 9:20 AM, Charles Mills wrote:
> A short answer is check out the SSI (Subsystem Interface) manual. Not for
> the feint-hearted.
>
You don't need to use the SSI to read a spool data set, although you do
need a way to get the JES SSID and jobid (like from the current JSAB).
PRINT CLOSE
//*
This prints the JESMSGLG put you could change that to JESJCL.
Thanks
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Thurs
nTek Solution Partners
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Chris Cantrell
Sent: Thursday, August 16, 2018 9:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: JES2 Spool Data Set Browse (SDSB) sample
I want to rea
I want to read the JCL for the job as it is running. I want to execute a
program as the first step that reads the JCL of the actual job that it is being
executed in.
--
For IBM-MAIN subscribe / signoff / archive access instructi
On Thu, 16 Aug 2018 09:00:15 -0500, Chris Cantrell wrote:
>We are on release 2.2. I am wanting to read the JCL in the first step of the
>job and perform very specific (which may change) verifications to the JCL and
>abend the job if the 'standards' are not met.
>
Is SDSF an option?
-- gil
---
@LISTSERV.UA.EDU
Subject: JES2 Spool Data Set Browse (SDSB) sample
Does anyone have a somple program which reads the currently running jobs JCL
using the Spool Data Set Browse (SDSB) function? I would be extremely greatful
in anyone could post a sample! Thanks
We are on release 2.2. I am wanting to read the JCL in the first step of the
job and perform very specific (which may change) verifications to the JCL and
abend the job if the 'standards' are not met.
--
For IBM-MAIN subscribe /
t; To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: JES2 Spool Data Set Browse (SDSB) sample
>
> Does anyone have a somple program which reads the currently running jobs JCL
> using the Spool Data Set Browse (SDSB) function? I would be extremely
> greatful in anyo
Does anyone have a somple program which reads the currently running jobs JCL
using the Spool Data Set Browse (SDSB) function? I would be extremely greatful
in anyone could post a sample! Thanks!
--
For IBM-MAIN subscribe / signo
23 matches
Mail list logo
