Hi Jeffrey,
I did read the documentation, several times, but unbeknownst to me at the time,
it was the wrong version - v11.3. Your reply prompted me to look for more
recent documentation, and in the documentation for v12, CA added the following
sentence to the description of DSNPFX='batch.dsn.prefix.': "This hlq must match
the hlq for the BATCHI#x and BATCHO#x data sets that are defined to the CA 7
started task."
IMHO, it seems nonsensical that the program would let you specify a prefix that
didn't match the started tasks ones and not give some sort of a warning or
error message. Why else would you have such an option if not to specify your
own datasets (and perhaps this is how it worked prior to v12).
Regards, Bob
-----Original Message-----
Date: Wed, 8 Mar 2017 10:43:15 -0600
From: Jeffrey Holst <jeffrey.ho...@pnc.com>
Subject: Re: Problem Generating CA-7 SASSBSTR Batch LJOB Output
If you read the documentation, DSNPFX must match the DSNPFX for the BATCHI#n
and BATCHO#n datasets that are defined to the CA7 started task. If DSNPFX is
not specified, the prefix specified for the COMMDS is used. DSNPFX need only be
specified if those prefixes do not match. There is no intent that one can
create his own BATCHI#n and BACTHO#n datasets.
That it gives RC=0 shows it is probably working as designed, What is documented
is that it copies the SYSIN to the BATCHI#n dataset that you specified, and
puts something in the COMMDS to tell CA-7 to process the BATCHI#n that it has
defined. There is nothing there, so it quickly writes something to its BATCHO#n
and puts something in COMMDS to tell your BTI that it is done processing, and
with what return code. (It is documented that unless there is a message table
defined, most results produce RC=0). Finally BTI reads your BATCHO#n (which is
empty) and writes it contents to SYSPRINT.
Jeffrey Holst
On Tue, 7 Mar 2017 14:14:37 -0500, Robert S. Hansel (RSH)
<r.han...@rshconsulting.com> wrote:
>Greetings all,
>
>I was able to get SASSBSTR running successfully, but in the process may have
>discovered a bug in the program. SASSBSTR allows you to specify your own
>pair of BATCHIN DD and BATCHOUT DD datasets using PARM DSNPFX. SASSBSTR
>allocates datasets for BATCHIN and BATCHOUT using the prefix specified by
>DSNPFX and appending .BATCHI#n and BATCHO#n ('n' is a pseudo terminal ID
>number). If you don't specify DSNPFX, SASSBSTR by default uses the BATCHIN
>and BATCHOUT datasets specified in CA7's configuration. When I run the job
>with my own DSNPFX, I get no output. When I use the ones in CA7's
>configuration, I get output as expected. Yet, the job runs successfully with
>RC=0 in both cases, and there are no error messages of any sort.
>
>Thank you to all who offered suggestions and advice.
>
>Regards, Bob
>
>Robert S. Hansel *** Celebrating 30 years working with RACF ***
>Lead RACF Specialist
>RSH Consulting, Inc.
>617-969-8211
>www.linkedin.com/in/roberthansel
>http://twitter.com/RSH_RACF
>www.rshconsulting.com
>
>-----Original Message-----
>From: Robert S. Hansel (RSH) [mailto:r.han...@rshconsulting.com]
>Sent: Friday, March 03, 2017 3:16 PM
>To: IBM-MAIN (ibm-m...@bama.ua.edu)
>Subject: Problem Generating CA-7 SASSBSTR Batch LJOB Output
>
>Greetings all,
>
>I am trying to generate listings of job information from CA-7 with the LJOB
>command using the Batch Terminal Interface (BTI) program SASSBSTR (PROC
>CA7BTI). The job runs successfully, but the output in SYSPRINT simply shows
>the LJOB command I executed and not, as I'd hoped, the output from the LJOB
>command. I've searched the manuals and cannot figure out how to the get the
>output I desire and was hoping someone could be of assistance. TIA.
>
>Regards, Bob
>
>Robert S. Hansel *** Celebrating 30 years working with RACF ***
>Lead RACF Specialist
>RSH Consulting, Inc.
>617-969-8211
>www.linkedin.com/in/roberthansel
>http://twitter.com/RSH_RACF
>www.rshconsulting.com
>----------------------------------------------------------------------------
>Upcoming RSH RACF Training - WebEx
>- RACF Audit & Compliance Roadmap - MAY 15-19, 2017
>- RACF Level I Administration - APR 25-28, 2017
>- RACF Level II Administration - FEB 27 - MAR 3, 2017
>- RACF Level III Admin, Audit, & Compliance - APR 3-7, 2017
>- RACF - Securing z/OS UNIX - OCT 23-27, 2017
>----------------------------------------------------------------------------
>
>----------------------------------------------------------------------
>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
