Would obtaining the data set names from SDSF meet your requirement?

//DFHSM    JOB MSGLEVEL=1                                              
//STARTING EXEC DFHSM,CMD=00                                           
XX******************************************************************** 
XX*          DFHSM 1.3 -  START PROCEDURE                            * 
XX*                                                                  * 
XX* THE FOLLOWING START PROCEDURE COULD BE DUPLICATED, AND RENAMED   * 
XX* FOR ANOTHER CPU IN THE CASE WHERE A MULTI-HOST ENVIRONMENT WILL  * 
XX* BE USED. CHANGES WOULD BE REQUIRED FOR THE CMD= AND THE HOST=    * 
XX* PARAMETERS, AND THE ARCLOGX AND ARCLOGY DATA SET NAMES.          * 
XX*                                                                  * 
XX******************************************************************** 
XXDFHSM  PROC CMD=00,             USE PARMLIB MEMBER ARCCMD00          
XX            EMERG=NO,           ALLOW ALL DFHSM FUNCTIONS            
XX            LOGSW=NO,           DON'T SWITCH LOGS AT STARTUP         
XX            STARTUP=YES,        STARTUP INFO PRINTED AT STARTUP      
XX            UID=DFHSM,          DFHSM AUTHORIZED-USER ID             
XX            SIZE=0M,            REGION SIZE FOR DFHSM                
XX            DDD=50,             MAX DYNAMICALLY ALLOCATED DATA SETS  
XX            HOST=1Y             PROC.UNIT ID AND LEVEL FUNCTIONS     
XXDFHSM  EXEC PGM=ARCCTL,DYNAMNBR=&DDD,REGION=&SIZE,TIME=1440,         
XX        PARM=('EMERG=&EMERG','LOGSW=&LOGSW','CMD=&CMD','UID=&UID',   
XX        'STARTUP=&STARTUP','HOST=&HOST')                             
IEFC653I SUBSTITUTION JCL - PGM=ARCCTL,DYNAMNBR=50,REGION=0M,TIME=1440,
'UID=DFHSM','STARTUP=YES','HOST=1Y')                                   
XXHSMPARM  DD DSN=SYS1.PARMLIB,DISP=SHR                                
XXMSYSOUT  DD SYSOUT=A                                                 
XXMSYSIN   DD DUMMY                                                    
XXSYSPRINT DD SYSOUT=A,FREE=CLOSE                                      
XXSYSUDUMP DD SYSOUT=A                                                 
XXMIGCAT   DD DSN=&UID..MCDS,DISP=SHR                                  
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.MCDS,DISP=SHR                    
XXJOURNAL  DD DSN=&UID..JRNL,DISP=MOD                                  
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.JRNL,DISP=MOD                    
XXARCLOGX  DD DSN=&UID..HSMLOGX1,DISP=MOD                              
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.HSMLOGX1,DISP=MOD                
XXARCLOGY  DD DSN=&UID..HSMLOGY1,DISP=MOD                              
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.HSMLOGY1,DISP=MOD                
XXARCPDOX  DD DSN=&UID..HSMPDOX,DISP=SHR                               
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.HSMPDOX,DISP=SHR                 
XXARCPDOY  DD DSN=&UID..HSMPDOY,DISP=SHR                               
XX*                                                              */    
XX* REMOVE THE NEXT DD STATEMENT IF YOU DO NOT INTEND TO USE     */    
XX* BACKUP AND DUMP.                                             */    
XX*                                                              */    
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.HSMPDOY,DISP=SHR                 
XXBAKCAT   DD DSN=&UID..BCDS,DISP=SHR                                  
XX*                                                              */    
XX* REMOVE THE NEXT DD STATEMENT IF YOU DO NOT                   */    
XX* INTEND TO USE TAPE VOLUMES FOR DAILY BACKUP VOLUMES, SPILL   */    
XX* BACKUP VOLUMES, OR MIGRATION LEVEL 2 VOLUMES.                */    
XX*                                                              */    
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.BCDS,DISP=SHR                    
XXOFFCAT   DD DSN=&UID..OCDS,DISP=SHR                                  
IEFC653I SUBSTITUTION JCL - DSN=DFHSM.OCDS,DISP=SHR                    

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Anthony Thompson
Sent: Wednesday, January 17, 2018 6:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Finding the names of hsm's BCDSs

Similarly, I was going to suggest calling TSO to invoke HSEND WAIT.

But QUERY CDS doesn't reveal the names of the HSM CDS's, just space information 
about them. Neither does Q SETSYS, but it does show the names of the CDS backup 
datasets. Quite often the backup dataset names are the same as the CDS', 
suffixed with BACKUP or BKUP or something.

Ant.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Graham Harris
Sent: Thursday, 18 January 2018 6:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Finding the names of hsm's BCDSs

Whilst you're waiting for IBM to deliver a proper API, you could trap the 
console output from a F DFHSM,Q CDS.
DFHSM may well not be called DFHSM of course, so that will add a little extra 
work, perhaps using an ISGQUERY on ARCENQG




On 17 January 2018 at 13:29, Manfred Lotz <ml_n...@posteo.de> wrote:

> On Wed, 17 Jan 2018 15:04:11 +0200
> ITschak Mugzach <imugz...@gmail.com> wrote:
>
> > Can you tell about the languages you wish to use and if this code 
> > runs on a server side or client (TSO, Batch).
> >
>
> Assembler. The program runs in TSO.
>
> --
> Manfred
>
>
> > ITschak
> >
> > On Wed, Jan 17, 2018 at 10:04 AM, Manfred Lotz <ml_n...@posteo.de>
> > wrote:
> >
> > > Hi there,
> > > I like to find out the DFSMShsm BCDS names programmatically.
> > >
> > > As I know the DD names, i.e. BAKCAT, and optionally BAKCAT2,
> > > BAKCAT3 and BAKCAT4 I thought of using AR mode in order to get the 
> > > TIOT of HSM.
> > >
> > > However, in order to get to the TIOT reliably I need SWAREQ which 
> > > doesn't support AR mode.
> > >
> > > Is there a way to get access to another address space's TIOT?  Any 
> > > ideas much appreciated.
> > >
> > > --
> > > Thanks a lot,
> > > Manfred Lotz
> > >
> > > ------------------------------------------------------------------
> > > ---- 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

----------------------------------------------------------------------
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