Page 2 of 2

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Dec 18, 2013 6:01 am
by Pedro
I suggest you send a rexx program to each system:
//GENER   EXEC PGM=IEBGENER                                 
//SYSPRINT  DD SYSOUT=9                                     
//SYSIN     DD DUMMY                                       
//SYSUT1    DD DDNAME=MYREXX                               
//SYSUT2    DD DISP=(NEW,PASS),DSN=&&TMP(MYREXX),           
//             UNIT=SYSVIO,SPACE=(TRK,(1,1,1)),             
//             DCB=(DSORG=PO,RECFM=FB,LRECL=80,BLKSIZE=3120)
//MYREXX    DD *                                           
  /*rexx */                                                 
  say 'Hello World'                                           
  exit   0                                                 
/*                                                         
//STEP2    EXEC PGM=IKJEFT01,DYNAMNBR=45                   
//SYSPROC   DD DISP=(OLD,DELETE),DSN=&&TMP                 
//SYSTSPRT  DD SYSOUT=H                                     
//SYSTSIN   DD *                                           
 %MYREXX                                                   
/*                                                         

But instead of 'hello world', you should write rexx program to:
1. trap command response from LISTDSD command
2. build another job with the command response inline
3. with /*ROUTE XEQ so it runs on the originating system
4. perhaps IEBGENER to copy command response to sequential dataset with disp=MOD. maybe add a header line so you know which system the response is from.
5. submit job

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Dec 18, 2013 6:59 am
by steve-myers
Something like

//SYSTSPRT DD SYSOUT=...,DEST=node.user

is only valid if the node is a VM/370 system. In MVS, DEST=node.user is done under the covers by XMIT. Period. End of story.

//SYSTSPRT DD SYSOUT=dataset

is simply not valid. Period. You can send the output to a data set using the method I showed in my first post.

Pedro - I'm not a JES3 expert, but as far as I know there is nothing like SYSOUT=dataset in JES3. I grant that both JES2 and JES3 assign data set names to SYSIN and SYSOUT data sets, but you cannot specify or use them in any way.

Now I'm going to bow out of this thread; I doubt I have anything more I can contribute.

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Dec 18, 2013 10:56 pm
by NoSleep319
that was something I was trying to get to work, which was very unsuccessful... what is currently in its place is the following:

//SYSTSPRT DD SYSOUT=*,OUTPUT=(*.OUTRPT)

Right now, it's sending the return to $AVRS, but I need to retrieve it to another dataset that doesn't exist yet (RJYW.AUDIT). The changes I've made within /SYSTSPRT have made a difference, because it's not sending it to $AVRS anymore, but it's not creating the dataset either...

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Dec 18, 2013 11:15 pm
by dick scherrer
Hello,

If you want the data both in a dataset and in the spool, write the dataset and then copy that dataset to sysout . . .

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Dec 18, 2013 11:34 pm
by NoSleep319
...

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Thu Dec 19, 2013 12:09 am
by NoSleep319
Previous quick response was a glitch...

The IBM User's Guide says that the following should work to save the output to a new dataset:

//SYSTSPRT DD DSN=RJYW.AUDIT.OUTPUT,DISP=NEW,SPACE=(TRK,5,5),UNIT=SYSDA

no luck...
I found it on
http://pic.dhe.ibm.com/infocenter/zos/v ... %2Fjcl.htm

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Thu Dec 19, 2013 12:58 am
by dick scherrer
Hello,

What you have is on the right track. Suggest you write a "complete" DD statement.

When you say "no luck" you need to post whatever diagnostic info was presented.

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Thu Dec 19, 2013 4:01 am
by NicC
Default DISP is NEW,DELETE,DELETE so your dataset is getting deleted at end of step.

Re: Retrieve covering profile from other system? LISTDSD?

PostPosted: Wed Feb 12, 2014 9:52 pm
by NoSleep319
I actually ended up using DMBATCH. the entire code is a little specific to our system(s), but the short story is this:

It does an LU/LG/LD command
It stores it locally on that system in a personal dataset
DMBATCH pulls it back to one system, in a naming convention like sys1.audit.sysname where the sysname would be specific to the system it originated from
It then scans those datasets looking for the specific access I'm looking for