Re: HOW DO I LEAVE IBM-MAIN

[John Dawes]

 Thanks to  all and to all a good night.
On Monday, 9 December 2019, 09:55:49 pm UTC, Edward Finnell 
<000248cce9f3-dmarc-requ...@listserv.ua.edu> wrote:  
 
 >>You can change your listserv options or subscription status at
>>the Archives web interface listserv.ua.edu/archives/ibm-main.html
In a message dated 12/9/2019 2:31:23 PM Central Standard Time, 
paul.bees...@atos.net writes:
To SIGNOFF from IBM-MAIN, send email to lists...@listserv.ua.edu with the 
following in the body: SIGNOFF 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

HOW DO I LEAVE IBM-MAIN

[John Dawes]

G'Day,
     Could somebody tell me how I could leave the IBM Main board?  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

GOODBYE

[John Dawes]

G'Day,
     I am about to retire and become a lazy sod for the rest of my life.  I 
would like to take this opportunity to thank everybody who answered my 
questions and for the invaluable help that was given to me.Looking back over 
the years I am surprised that I survived the cuts and stress of the job.  Every 
year when the budget was being drawn up I hardly slept because I was scared 
that I would be a casualty.  In my Mainframe career I survived 3 brutal cuts 
(jobs transferred to India, Philippines etc. etc) and I was lucky to get 
employment in this firm.  
A massive thanks to all of you for your support especially during the early 
hours of the morning.
Bye and good luck to all.  A Happy Christmas to those who celebrate it and a 
prosperous 2020 !


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Gerhard Postpischil ז״ל

[John Dawes]

 Condolences to you and the Postpischil family.  Gerhard will be remembered by 
his intelligent posts and advice.
On Monday, 11 November 2019, 07:31:20 pm UTC, Seymour J Metz 
 wrote:  
 
 It is with deep regret that I announce the death of my friend and colleague 
Gerhard Postpischil, whom some of you may know from here, CBTTAPE.ORG or 
Hercules. Someone told his son Eric "You sound like your father." - I can think 
of no greater compliment. Gerhard was a stickler for accuracy and always strove 
to write 
tight code. He was also a good friend to me and my children, and we will miss 
him.



--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

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

Re: DFHSM/DCOLLECT QUESTION [EXTERNAL]

[John Dawes]

 Paul,
Thanks for your suggestion.  I ran the LISTCAT but there is no RLS IN USE 
displayed.

On Monday, 4 November 2019, 06:36:16 pm UTC, Feller, Paul 
 wrote:  
 
 In the LISTCAT output look for "RLS IN USE", it should show YES or NO.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of esmie moo
Sent: Monday, November 04, 2019 9:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: DFHSM/DCOLLECT QUESTION [EXTERNAL]

Gentle Readers,
     We receive a IEC161I 009-0663 (COND CODE 0008) everytime we execute a 
batch job which uses DCOLLECT:   The error occurs while reading the MCDS.
I checked the IBM documentation and I got more confused.  I found this tidbit 
of info:

This is a known condition when running IDCAMS DCOLLECT against DFSMShsm CDS

which are not in RLS mode. ARCUTIL first tries to open the CDS in RLS mode, so 
the IEC161I RC009 is issued when this fails. HSM then opens the CDS in NON RLS 
mode. This is described in DFSMShsm Implementation and Customization Guide, 
Chapter " User Application Interfaces", under Choosing a Data Collection 
Method. Customers whose HSM CDS are not in RLS mode may ignore this condition.
   I am not sure how verify if the CDS is "... are not in RLS mode."
I looked at the LISTCAT and it shows that the SHROPTIONS parm is set at 
SHROPTNS(3,3) 

Could somebody help me understand this?
Thanks.




--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

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

Re: TLMS QUESTION - SCRATCH A TAPE

[John Dawes]

 Russell,
Thanks for the confirmation.
On Saturday, 5 October 2019, 06:12:49 pm UTC, Russell Witt 
<025adb32e6d7-dmarc-requ...@listserv.ua.edu> wrote:  
 
 John,

Yes, that is the correct control statements to scratch the tape (assumption 
being that it is not an EDM tape).

Russell Witt
Broadcom

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Friday, October 4, 2019 6:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TLMS QUESTION - SCRATCH A TAPE

G'Day,
I want to scratch a tape which has a retention period of 1095 days.  This is 
what it looks when I query the tape:
RTN-SCHED(1)  BY RMF 5DC1095

I saw this example in the TLMS doc.  Would it scratch the tape?

/*                        //TLMSINQR EXEC CATINQR    //CAIIPT DD *              
//UPV T59631,SCRATCH=YES  /*                        //                        

--

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

TLMS QUESTION - SCRATCH A TAPE

[John Dawes]

G'Day,
I want to scratch a tape which has a retention period of 1095 days.  This is 
what it looks when I query the tape: 
RTN-SCHED(1)  BY RMF 5DC1095

I saw this example in the TLMS doc.  Would it scratch the tape?

/*                         //TLMSINQR EXEC CATINQR    //CAIIPT DD *             
 //UPV T59631,SCRATCH=YES   /*                         //                       
  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: CA-DISK (DMS) QUESTION

[John Dawes]

 Bob,
Thanks for the info. and the example.  I will try it out.
On Tuesday, 20 August 2019, 05:40:39 pm UTC, Robert Longabaugh 
<01f25da983e8-dmarc-requ...@listserv.ua.edu> wrote:  
 
 Hi John,

The easiest way to "re-duplex" would be to run MERGE, using the duplex
volume as input.

You would specify the original volume key. The merge process will see that
the primary volume is disabled, so it will use the duplex volume as input
to the merge.  It will create a new duplex as well.

Using PERCENT=0 excludes all volumes.  INCLUDE=199664 overrides any other
parms, such as "PERCENT=0", so MERGE will select the volume that you wish
to re-duplex.

//MERG      EXEC MERGE
//MERGE.COPYFILE DD DUMMY
//MERGE.SYSIN DD *
 MERGE PERCENT=0,INCLUDE=199664



Bob Longabaugh
Broadcom
Storage Management

On Tue, Aug 20, 2019 at 8:02 AM John Dawes <
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
> Would anybody have an example to create an ARCHPRIM tape.  The original
> ARCHPRIM was written over (user error).  As a quick fix I ran IXUPDATE
> with RESET KEY=199664,DISABLE.  This replaces the original ARCHPRIM.
> Thanks.
>
> --
> 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

CA-DISK (DMS) QUESTION

[John Dawes]

G'Day,
Would anybody have an example to create an ARCHPRIM tape.  The original 
ARCHPRIM was written over (user error).  As a quick fix I ran IXUPDATE with 
RESET KEY=199664,DISABLE.  This replaces the original ARCHPRIM.   
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Rex,
I used your jcl and it worked.  I was successful with and without the NORUN 
parm.  
A massive thanks. 
On Thursday, 16 May 2019, 7:35:43 pm UTC, Pommier, Rex 
 wrote:  
 
 John,

I'm running 2.2 as well.  I was able to run it successfully copying 2 datasets 
to a tape.  And just for kicks and giggles, I removed the TYPRUN parm and it 
dumped the 2 datasets to a single tape. 

Here's my JCL/parms:

//STEP005 EXEC  PGM=ADRDSSU,REGION=0M,PARM='TYPRUN=NORUN'  
//SYSPRINT DD  SYSOUT=*                                    
//DASD1    DD  UNIT=3390,VOL=SER=S10057,DISP=SHR          
//OUTVOL1  DD  UNIT=VTS,DISP=(,CATLG),                    
//    DSN=RRP.PHYS.DUMP                                    
//SYSIN  DD  *                                            
  DUMP DATASET(                            -            
          INCLUDE(                          -            
      RRP.ROCKET.SJHNCLIB                    -            
      RRP.ROCKET.SJHNLOAD                    -            
                  ))                        -            
        CANCELERROR                          -            
        OPT(4) ALLDATA(*) ALLEXCP            -            
        INDDNAME(DASD1)                      -            
        OUTDDNAME(                          -            
                  OUTVOL1                    -            
                )                          -            
        TOL(ENQF)                            -            
        WAIT(1,1)                                          
/*                                                        

And my output:

ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP '        
                      
ADR109I (R/I)-RI01 (01), 2019.136 14:32:16 INITIAL SCAN OF USER CONTROL 
STATEMENTS COMPLETED          
ADR146I (R/I)-RI03 (15), OBSOLETE KEYWORD INDDNAME SPECIFIED. PHYSINDDNAME WILL 
BE USED                
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK            
                      
ADR006I (001)-STEND(01), 2019.136 14:32:16 EXECUTION BEGINS                     
                       
ADR329I (001)-DTDS (01), DATA SET DUMP OF VOLUME S10057 BEGINS ON TAPE A04491 
SEQUENCE 0001            
ADR329I (001)-DTDS (02), DATA SET DUMP OF VOLUME S10057 ENDS ON TAPE A04491 
SEQUENCE 0001              
ADR378I (001)-DTDS (01), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED 
FROM VOLUME S10057        
                          RRP.ROCKET.SJHNCLIB                                   
                       
                          RRP.ROCKET.SJHNLOAD                                   
                       
ADR006I (001)-STEND(02), 2019.136 14:32:17 EXECUTION ENDS                       
                       
ADR013I (001)-CLTSK(01), 2019.136 14:32:17 TASK COMPLETED WITH RETURN CODE  
                       
ADR012I (SCH)-DSSU (01), 2019.136 14:32:17 DFSMSDSS PROCESSING COMPLETE. 
HIGHEST RETURN CODE IS   

So, yes, DFDSS is OK dumping more than one physical dataset to a tape.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 Rex,I tried both INDDNAME & PHYSINDD as well.  I can confirm that both dsns 
are on the same volume.Maybe you can try a test to see if you can do a 
successful Physical backup of 2 dsns.I am curious if it works for you.  I am 
running V2R02.0 
    On Thursday, 16 May 2019, 4:47:56 pm UTC, Pommier, Rex 
 wrote:  
 
 John,

Do you need to change your INDDNAME to PHYSINDD?  The 2.2 manual indicates that 
INDDNAME is used for full or track copying and PHYSINDD is used for datasets.  
Are both the datasets you're going after on the same volume?

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER 

    On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:  
 
 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of 
> several dsn which are on a specific volume.  For some reason it doesn't work. 
> I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER Below is the job output and the JCL.  Can you spot my error?  Does 
> DFDSS support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE 
> INNORUN MOD

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 For some reason the output seems to get misaligned.  Here it is again.
ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE IN NORUN 
MOD DUMP INDDNAME(DASD1) OUTDDNAME(TAPE1)        -                              
         DATASET(INCLUDE(HESP.IMS.PROD.MATRIX     -                             
                                   HESP.NETVIEW.PRF))          -                
              TOL(ENQF)                          -                              
              OPT(4) ALLDATA(*) ALLEXCP                                         
        ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP 
'        ADR109I (R/I)-RI01 (01), 2019.136 11:19:22 INITIAL SCAN OF USER 
CONTROL STATEMENADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER           
                ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND 
                ADR017E (001)-CLTSK(01), 2019.136 11:19:22 TASK NOT SCHEDULED 
DUE TO ERROR. TASKADR012I (SCH)-DSSU (01), 2019.136 11:19:22 DFSMSDSS 
PROCESSING COMPLETE. HIGHEST                         SYNTAX                     
                            

On Thursday, 16 May 2019, 6:10:06 pm UTC, Jousma, David 
<01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:  
 
 One other tidbit.  The SYSIN data, and all of the lines must be contained 
between columns 2-72.  Not column 1.  It would be really helpful if you could 
post the job with the correct formatting.  Whatever is messing it up appears to 
be removing spaces between some of your keywords.

_
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

 John,The - or , are both acceptable.  I use the - all the time and never had a 
problem.
    On Thursday, 16 May 2019, 2:59:16 pm UTC, John McKown 
 wrote:  
 
 It's hard for me to read the reformatted text. But you need a comma between 
the two DSNs in the INCLUDE list. I don't see any comma.

On Thu, May 16, 2019 at 9:51 AM John Dawes < 
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
> I am encountering a problem performing a Physical dataset backup of  
>several dsn which are on a specific volume.  For some reason it doesn't  
>work. I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      '
> IS IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does 
>DFDSS  support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE  
>INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>                DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -
>                                      HESP.NETVIEW.PRF))          -
>                      TOL(ENQF)            -        OPT(4)ALLDATA(*)  
>ALLEXCP  ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO 
>COMMAND  'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR.
> TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
> HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>    OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
This is clearly another case of too many mad scientists, and not enough 
hunchbacks.


Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  

-

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 David,I rechecked the job.  The DUMP command is in column 2, the 
DATASET(INCLUDE starts at col  7.
On Thursday, 16 May 2019, 6:13:10 pm UTC, Jousma, David 
<01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:  
 
 This would be correct syntax.  Comma's are optional, dash is not.  By your 
other post where you said it worked with one dataset, it almost looks like your 
HESP. Dataset name starts in column 1? 

//SYSIN    DD  *
  DUMP INDDNAME(DASD1) OUTDDNAME(TAPE1)        -
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
                HESP.NETVIEW.PRF))            -  
                TOL(ENQF)                          -
                OPT(4) ALLDATA(*) ALLEXCP
/*

_
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

 John,The - or , are both acceptable.  I use the - all the time and never had a 
problem.
    On Thursday, 16 May 2019, 2:59:16 pm UTC, John McKown 
 wrote:  
 
 It's hard for me to read the reformatted text. But you need a comma between 
the two DSNs in the INCLUDE list. I don't see any comma.

On Thu, May 16, 2019 at 9:51 AM John Dawes < 
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
> I am encountering a problem performing a Physical dataset backup of  
>several dsn which are on a specific volume.  For some reason it doesn't  
>work. I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      '
> IS IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does 
>DFDSS  support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE  
>INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>                DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -
>                                      HESP.NETVIEW.PRF))          -
>                      TOL(ENQF)            -        OPT(4)ALLDATA(*)  
>ALLEXCP  ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO 
>COMMAND  'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR.
> TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
> HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>    OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
This is clearly another case of too many mad scientists, and not enough 
hunchbacks.


Maranatha! <><
John McKown

--
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
**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.  It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting 

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Rex,
I am glad that it works for you and not me.  Could you post the output of the 
job?  Maybe I will see something that I may be missing?
Thanks.
On Thursday, 16 May 2019, 7:45:36 pm UTC, Pommier, Rex 
 wrote:  
 
 I just changed my SYSIN to look as close to identical to yours as I can see, 
given the formatting problems you're having, and it still worked.  Regarding 
the "column 1" question David had, I just tried it, and all DFDSS did was 
ignore the first character of the dataset name and tell me it couldn't find 
"RP.ROCKET.SJHNLOAD" and continue on its merry way.

  DUMP  INDDNAME(DASD1) OUTDDNAME(OUTVOL1) -      
    DATASET(INCLUDE(RRP.ROCKET.SJHNCLIB        -  
    RRP.ROCKET.SJHNLOAD))      -                  
        TOL(ENQF)                            -    
        OPT(4) ALLDATA(*) ALLEXCP                  

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jousma, David
Sent: Thursday, May 16, 2019 1:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

This would be correct syntax.  Comma's are optional, dash is not.  By your 
other post where you said it worked with one dataset, it almost looks like your 
HESP. Dataset name starts in column 1? 

//SYSIN    DD  *
  DUMP INDDNAME(DASD1) OUTDDNAME(TAPE1)        -
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
                HESP.NETVIEW.PRF))            -  
                TOL(ENQF)                          -
                OPT(4) ALLDATA(*) ALLEXCP
/*

_
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

 John,The - or , are both acceptable.  I use the - all the time and never had a 
problem.
    On Thursday, 16 May 2019, 2:59:16 pm UTC, John McKown 
 wrote:  
 
 It's hard for me to read the reformatted text. But you need a comma between 
the two DSNs in the INCLUDE list. I don't see any comma.

On Thu, May 16, 2019 at 9:51 AM John Dawes < 
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
> I am encountering a problem performing a Physical dataset backup of 
>several dsn which are on a specific volume.  For some reason it doesn't 
>work. I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      '
> IS IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does 
>DFDSS  support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE 
>INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>                DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -
>                                      HESP.NETVIEW.PRF))          -
>                      TOL(ENQF)            -        OPT(4)ALLDATA(*) 
>ALLEXCP  ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO 
>COMMAND  'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR.
> TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
> HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>    OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
This is clearly another case of too many mad scientists, and not enough 
hunchbacks.


Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  

---

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Alan,Could you confirm the following:a) after DSN=datasetname1. is it a period 
or a comma?b) in the statement Inddd=indd1outdd=outdd1 should there be a space 
between the indd1 and outdd?b) after the outdd1.. is there something else I 
should tack on?
On Thursday, 16 May 2019, 4:54:38 pm UTC, Allan Staller 
 wrote:  
 
 Try this:
//INDD1 dd 
//INDD2 dd .
//OUTDD1 dd 
//OUTDD2 dd .
//SYSIN DD *
 Parallel
 DUMP DSN=datasetname1. Inddd=indd1outdd=outdd1
 DUMP DSN=datasetname2. Inddd=indd21outdd=outdd2

HTH,


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 Rex,
No, there is none. As I had mentioned before, if I execute the job to select 1 
dsn it works, however if I try with 2 or more dsns the job fails.  I suspect 
that DFDSS doesn't support a phyiscial dataset backup for more than 1 dsn.
    On Thursday, 16 May 2019, 3:26:44 pm UTC, Pommier, Rex 
 wrote:

 Do you have some kind of hidden hex character in your input stream?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER

    On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:

 
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.1.0%2Fcom.ibm.zos.v2r1.adru000%2Fr2298.htm=02%7C01%7Callan.staller%40HCL.COM%7C477dbed3b5f94d1640d508d6da1ddeb7%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636936219191148634=nUnrrCmo0KNzeZJ0J1jxn6InE%2Bb1Z44CMH7Ci6QrnxQ%3D=0

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of
> several dsn which are on a specific volume.  For some reason it doesn't work. 
> I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER Below is the job output and the JCL.  Can you spot my error?  Does 
> DFDSS support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE
> INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -                    
>               DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -             
>                                  HESP.NETVIEW.PRF))          -                
>             TOL(ENQF)            -        OPT(4)ALLDATA(*) ALLEXCP ADR101I 
> (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE
> TOERROR. TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
>HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Alan,I'll try it out.  The only drawback is that I will be using more than 1 
tape to backup the dsns.In your example I will be using 2 tapes.
On Thursday, 16 May 2019, 4:54:38 pm UTC, Allan Staller 
 wrote:  
 
 Try this:
//INDD1 dd 
//INDD2 dd .
//OUTDD1 dd 
//OUTDD2 dd .
//SYSIN DD *
 Parallel
 DUMP DSN=datasetname1. Inddd=indd1outdd=outdd1
 DUMP DSN=datasetname2. Inddd=indd21outdd=outdd2

HTH,


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 11:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 Rex,
No, there is none. As I had mentioned before, if I execute the job to select 1 
dsn it works, however if I try with 2 or more dsns the job fails.  I suspect 
that DFDSS doesn't support a phyiscial dataset backup for more than 1 dsn.
    On Thursday, 16 May 2019, 3:26:44 pm UTC, Pommier, Rex 
 wrote:

 Do you have some kind of hidden hex character in your input stream?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER

    On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:

 
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.1.0%2Fcom.ibm.zos.v2r1.adru000%2Fr2298.htm=02%7C01%7Callan.staller%40HCL.COM%7C477dbed3b5f94d1640d508d6da1ddeb7%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636936219191148634=nUnrrCmo0KNzeZJ0J1jxn6InE%2Bb1Z44CMH7Ci6QrnxQ%3D=0

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of
> several dsn which are on a specific volume.  For some reason it doesn't work. 
> I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER Below is the job output and the JCL.  Can you spot my error?  Does 
> DFDSS support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE
> INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -                    
>               DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -             
>                                  HESP.NETVIEW.PRF))          -                
>             TOL(ENQF)            -        OPT(4)ALLDATA(*) ALLEXCP ADR101I 
> (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE
> TOERROR. TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
>HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawfu

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Rex,I tried both INDDNAME & PHYSINDD as well.  I can confirm that both dsns 
are on the same volume.Maybe you can try a test to see if you can do a 
successful Physical backup of 2 dsns.I am curious if it works for you.  I am 
running V2R02.0 
On Thursday, 16 May 2019, 4:47:56 pm UTC, Pommier, Rex 
 wrote:  
 
 John,

Do you need to change your INDDNAME to PHYSINDD?  The 2.2 manual indicates that 
INDDNAME is used for full or track copying and PHYSINDD is used for datasets.  
Are both the datasets you're going after on the same volume?

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER 

    On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:  
 
 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of 
> several dsn which are on a specific volume.  For some reason it doesn't work. 
> I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER Below is the job output and the JCL.  Can you spot my error?  Does 
> DFDSS support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE 
> INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -                    
>               DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -             
>                                  HESP.NETVIEW.PRF))          -                
>             TOL(ENQF)            -        OPT(4)ALLDATA(*) ALLEXCP ADR101I 
> (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE 
> TOERROR. TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -    
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -                    
>HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -        
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


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

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Rex,
No, there is none. As I had mentioned before, if I execute the job to select 1 
dsn it works, however if I try with 2 or more dsns the job fails.  I suspect 
that DFDSS doesn't support a phyiscial dataset backup for more than 1 dsn.  
On Thursday, 16 May 2019, 3:26:44 pm UTC, Pommier, Rex 
 wrote:  
 
 Do you have some kind of hidden hex character in your input stream?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER 

    On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:  
 
 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of 
> several dsn which are on a specific volume.  For some reason it doesn't work. 
> I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER Below is the job output and the JCL.  Can you spot my error?  Does 
> DFDSS support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE 
> INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -                    
>               DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -             
>                                  HESP.NETVIEW.PRF))          -                
>             TOL(ENQF)            -        OPT(4)ALLDATA(*) ALLEXCP ADR101I 
> (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE 
> TOERROR. TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -    
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -                    
>HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -        
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


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

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Rex,I tried that as well but I got the same ADR129E error message.I tried the 
backup for one dsn and it works.  Which makes me believe that a multiple 
physical dsn backup is  not supported by DFDSS.
On Thursday, 16 May 2019, 3:29:32 pm UTC, Pommier, Rex 
 wrote:  
 
 John,

I see that you're doing a TYPRUN=NORUN.  What happens if you strip all the 
excess/optional lines from your SYSIN.  Can you eliminate the error by 
eliminating most of the control cards and just re-add them until you hit the 
error again?

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

 Dave,I checked.  The DUMP statement is part of the INDDNAME.  It looks that it 
is missing the - because my post came out misaligned.Here it is again:
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    - 

  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -   
 

  HESP.NETVIEW.PRF))  -    

  TOL(ENQF)  -
 OPT(4) ALLDATA(*) ALLEXCP                                                 

    On Thursday, 16 May 2019, 2:58:36 pm UTC, Jousma, David 
<01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:  
 
 Could it be that you are missing a dash after the word DUMP?  Or a space 
between these two keywords: INDDNAME(DASD1)OUTDDNAME(TAPE1)        

_
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

 Please excuse my post for being misaligned.  I do not know how to correct it.  
Any ideas?
    On Thursday, 16 May 2019, 2:51:22 pm UTC, John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:  
 
 G'Day,
I am encountering a problem performing a Physical dataset backup of several dsn 
which are on a specific volume.  For some reason it doesn't work. I receive the 
error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER Below is 
the job output and the JCL.  Can you spot my error?  Does DFDSS support a 
phyisical backup of multiple dsns?
ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -                              
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -                         
                     HESP.NETVIEW.PRF))  -                             
TOL(ENQF)             -     OPT(4)ALLDATA(*) ALLEXCP ADR101I (R/I)-RI01 
(01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'    

ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER CONTROLSTATEMENT

ADR129E (001)-RI01 (01), KEYWORD ' ' IS IMPROPER  

ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND 

ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. TASK

/*   

//NORUN   EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'    

//*STEP1   EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'

//DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR 

//TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,  

//DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99) 

//SYSPRINT DD  SYSOUT=*   

//SYSMAP   DD SYSOUT=*    

//SYSIN    DD  *
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -     
DATASET(INCLUDE(HESP.IMS.PROD.MATRIX    -                    
HESP.NETVIEW.PRF))    -   TOL(ENQF)  -        
OPT(4) ALLDATA(*) ALLEXCP
/*                    



--
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 **CAUTION EXTERNAL 
EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.  It is intended only for the

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 I tried your suggestion but it didn't work:
ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER 

On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab 
 wrote:  
 
 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm

INCLUDE(data.set.one, -
                data.set.two)

Commas are REQUIRED.

On Thu, May 16, 2019 at 9:51 AM John Dawes
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:
>
> G'Day,
> I am encountering a problem performing a Physical dataset backup of several 
> dsn which are on a specific volume.  For some reason it doesn't work. I 
> receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does DFDSS 
> support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
> MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -                            
>       DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -                     
>                          HESP.NETVIEW.PRF))          -                        
>     TOL(ENQF)            -        OPT(4)ALLDATA(*) ALLEXCP
> ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. 
> TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -    
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -                    
>HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -        
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 David,The reason why I am doing a Physical backup of the dsns instead of a 
Logical backup it is because these dsns have a problem - no NVR.  They reside 
on a SMS volume but for some reason some of the dsn|(s) are non-SMS.DFDSS does 
not support a Logical backup of these problem dsns
On Thursday, 16 May 2019, 3:04:15 pm UTC, David Spiegel 
 wrote:  
 
 Hi John,
Physical Backups are usually a bad idea when doing backup by dataset.
If these are non-VSAM and non-SMS-managed, you can still do it for 
specific volumes by coding LIDD instead of INDD.
The INDD/INDY is used to determine Logical vs. Physical. If coded, it's 
Physical, otherwise, it's Logiocal.

Regards,
David

On 2019-05-16 10:51, John Dawes wrote:
> G'Day,
> I am encountering a problem performing a Physical dataset backup of several 
> dsn which are on a specific volume.  For some reason it doesn't work. I 
> receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS 
> IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does DFDSS 
> support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
> MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -                            
>       DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -                     
>                          HESP.NETVIEW.PRF))  -                        
>      TOL(ENQF)             -     OPT(4)ALLDATA(*) ALLEXCP
> ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER 
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD ' ' IS IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. 
> TASK
>
> /*
>
> //NORUN   EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1   EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP   DD SYSOUT=*
>
> //SYSIN    DD  *
>   DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -     
>DATASET(INCLUDE(HESP.IMS.PROD.MATRIX    -                    
>HESP.NETVIEW.PRF))    -   TOL(ENQF)  -        
>OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> 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

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 John,The - or , are both acceptable.  I use the - all the time and never had a 
problem.
On Thursday, 16 May 2019, 2:59:16 pm UTC, John McKown 
 wrote:  
 
 It's hard for me to read the reformatted text. But you need a comma between
the two DSNs in the INCLUDE list. I don't see any comma.

On Thu, May 16, 2019 at 9:51 AM John Dawes <
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
> I am encountering a problem performing a Physical dataset backup of
> several dsn which are on a specific volume.  For some reason it doesn't
> work. I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      '
> IS IMPROPER
> Below is the job output and the JCL.  Can you spot my error?  Does DFDSS
> support a phyisical backup of multiple dsns?
> ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE
> INNORUN MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>                DATASET(INCLUDE(HESP.IMS.PROD.MATRIX              -
>                                      HESP.NETVIEW.PRF))          -
>                      TOL(ENQF)            -        OPT(4)ALLDATA(*)
> ALLEXCP
> ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND
> 'DUMP'
>
> ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER
> CONTROLSTATEMENT
>
> ADR129E (001)-RI01 (01), KEYWORD '    ' IS
> IMPROPER
>
> ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT
> COMMAND
>
> ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR.
> TASK
>
> /*
>
> //NORUN  EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'
>
> //*STEP1  EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
>
> //DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR
>
> //TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,
>
> //            DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99)
>
> //SYSPRINT DD  SYSOUT=*
>
> //SYSMAP  DD SYSOUT=*
>
> //SYSIN    DD  *
>  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)        -
>  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX        -
> HESP.NETVIEW.PRF))            -  TOL(ENQF)                          -
>    OPT(4) ALLDATA(*) ALLEXCP
> /*
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
This is clearly another case of too many mad scientists, and not enough
hunchbacks.


Maranatha! <><
John McKown

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

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Dave,I checked.  The DUMP statement is part of the INDDNAME.  It looks that it 
is missing the - because my post came out misaligned.Here it is again:
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    - 

  DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -   
 

  HESP.NETVIEW.PRF))  -    

  TOL(ENQF)  -  
 OPT(4) ALLDATA(*) ALLEXCP                                                 

On Thursday, 16 May 2019, 2:58:36 pm UTC, Jousma, David 
<01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:  
 
 Could it be that you are missing a dash after the word DUMP?  Or a space 
between these two keywords: INDDNAME(DASD1)OUTDDNAME(TAPE1)        

_
Dave Jousma
AVP | Manager, Systems Engineering  

Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, MI 
49546
616.653.8429  |  fax: 616.653.2717


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, May 16, 2019 10:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

 Please excuse my post for being misaligned.  I do not know how to correct it.  
Any ideas?
    On Thursday, 16 May 2019, 2:51:22 pm UTC, John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:  
 
 G'Day,
I am encountering a problem performing a Physical dataset backup of several dsn 
which are on a specific volume.  For some reason it doesn't work. I receive the 
error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER Below is 
the job output and the JCL.  Can you spot my error?  Does DFDSS support a 
phyisical backup of multiple dsns?
ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -                              
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -                         
                     HESP.NETVIEW.PRF))  -                             
TOL(ENQF)             -     OPT(4)ALLDATA(*) ALLEXCP ADR101I (R/I)-RI01 
(01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'    

ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER CONTROLSTATEMENT

ADR129E (001)-RI01 (01), KEYWORD ' ' IS IMPROPER  

ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND 

ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. TASK

/*   

//NORUN   EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'    

//*STEP1   EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'

//DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR 

//TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,  

//DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99) 

//SYSPRINT DD  SYSOUT=*   

//SYSMAP   DD SYSOUT=*    

//SYSIN    DD  *
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -     
DATASET(INCLUDE(HESP.IMS.PROD.MATRIX    -                    
HESP.NETVIEW.PRF))    -   TOL(ENQF)  -        
OPT(4) ALLDATA(*) ALLEXCP
/*                    



--
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 **CAUTION EXTERNAL 
EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.  It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: I

DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

G'Day,
I am encountering a problem performing a Physical dataset backup of several dsn 
which are on a specific volume.  For some reason it doesn't work. I receive the 
error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER
Below is the job output and the JCL.  Can you spot my error?  Does DFDSS 
support a phyisical backup of multiple dsns?
ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -                              
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -                         
                     HESP.NETVIEW.PRF))  -                             
TOL(ENQF)             -     OPT(4)ALLDATA(*) ALLEXCP                        
                        
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'    

ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER CONTROLSTATEMENT

ADR129E (001)-RI01 (01), KEYWORD ' ' IS IMPROPER  

ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND 

ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. TASK

/*   

//NORUN   EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'    

//*STEP1   EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'

//DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR 

//TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,  

//DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99) 

//SYSPRINT DD  SYSOUT=*   

//SYSMAP   DD SYSOUT=*    

//SYSIN    DD  * 
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -     
DATASET(INCLUDE(HESP.IMS.PROD.MATRIX    -                    
HESP.NETVIEW.PRF))    -   TOL(ENQF)  -        
OPT(4) ALLDATA(*) ALLEXCP                                  
/*                    



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

[John Dawes]

 Please excuse my post for being misaligned.  I do not know how to correct it.  
Any ideas?
On Thursday, 16 May 2019, 2:51:22 pm UTC, John Dawes 
<00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:  
 
 G'Day,
I am encountering a problem performing a Physical dataset backup of several dsn 
which are on a specific volume.  For some reason it doesn't work. I receive the 
error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER
Below is the job output and the JCL.  Can you spot my error?  Does DFDSS 
support a phyisical backup of multiple dsns?
ADR031I (SCH)-PRIME(01), TYPRUN=NORUN REQUESTED. TASKS WILL EXECUTE INNORUN 
MODE DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -                              
    DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      -                         
                     HESP.NETVIEW.PRF))  -                             
TOL(ENQF)             -     OPT(4)ALLDATA(*) ALLEXCP                        
                        
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP'    

ADR109I (R/I)-RI01 (01), 2019.136 10:21:19 INITIAL SCAN OF USER CONTROLSTATEMENT

ADR129E (001)-RI01 (01), KEYWORD ' ' IS IMPROPER  

ADR131E (001)-RI03 (01), ABOVE TEXT BYPASSED UNTIL NEXT COMMAND 

ADR017E (001)-CLTSK(01), 2019.136 10:21:19 TASK NOT SCHEDULED DUE TOERROR. TASK

/*   

//NORUN   EXECPGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN'    

//*STEP1   EXECPGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'

//DASD1    DD  UNIT=SYSDA,VOL=SER=PROD03,DISP=SHR 

//TAPE1    DD  DSN=MVS.PHYSICAL.BKUP.PROD03,  

//DISP=(,CATLG,DELETE),UNIT=3490,VOL=(,,,99) 

//SYSPRINT DD  SYSOUT=*   

//SYSMAP   DD SYSOUT=*    

//SYSIN    DD  * 
 DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -     
DATASET(INCLUDE(HESP.IMS.PROD.MATRIX    -                    
HESP.NETVIEW.PRF))    -   TOL(ENQF)  -        
OPT(4) ALLDATA(*) ALLEXCP                                  
/*                    



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

Re: SMS ALLOCATION OF VSAM DSN [EXTERNAL]

[John Dawes]

 Paul,
Thanks for reviewing the define cluster.  I checked, there is about 7,000 
cylinders on the volume.  Many thanks.
On Tuesday, 27 November 2018, 11:22:16 am GMT-5, Feller, Paul 
 wrote:  
 
 John, your definition should work just fine.  It has been a while that I 
looked at HSM control files so I did a little testing.  Depending on how much 
space you have on your HSM002 volume you could go as high as 5,800 cyls.  With 
that size you would get a HI-A-RBA of 4262952960.  Depending on how you do the 
calculation you would get around 3.97 gig.

Just as a side note the MCDS can be an extended format dataset.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Tuesday, November 27, 2018 8:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMS ALLOCATION OF VSAM DSN [EXTERNAL]

 Paul,
Thanks for the info.  I am trying to define the HSM MCDS at a maximum number of 
cylinders.  Below is the DEFINE CLUSTER:

DEFINECLUSTER -                                     
   (NAME(PROD..HSM.MCDS) VOLUME(HSM002) -  
   CYLINDER(4300 0)  -    
   RECORDSIZE(435 2040) FREESPACE(0 0)-    
   SPEED BUFFERSPACE(530432) -  
   INDEXED KEYS(44 0) SHAREOPTIONS(3 3)-   
   UNIQUE NOWRITECHECK)  -  
   DATA (NAME(PROD..HSM.MCDS.DATA) CISZ(12288) ) -
   INDEX (NAME(PROD..HSM.MCDS.INDEX) CISZ(2048)) I think I am safe.  What says 
you?

    On Monday, 26 November 2018, 7:15:32 pm GMT-5, Feller, Paul 
 wrote:  
 
 John, basically you are limited to 4 gig (HI-A-RBA) for the size of a 
non-extended VSAM dataset.  So depending on your VSAM define option you will 
get somewhere in the neighborhood of 6,000 cyls.  In my quick test I got around 
5,800 cyls.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Monday, November 26, 2018 12:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMS ALLOCATION OF VSAM DSN [EXTERNAL]

G'Day,
Could somebody please tell me what is the maximum number of cylinders that 
could be allocated for a SMS managed VSAM dsn (not VSAM EXTENDED 
ADDRESSABILITY). I have been able to allocate a dsn with 6,000 cylinders.  
However, due to a lack of disk space I couldn't continue with a higher 
allocation.
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

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

Re: SMS ALLOCATION OF VSAM DSN [EXTERNAL]

[John Dawes]

 Paul,
Thanks for the info.  I am trying to define the HSM MCDS at a maximum number of 
cylinders.  Below is the DEFINE CLUSTER:

DEFINECLUSTER -                                     

   (NAME(PROD..HSM.MCDS) VOLUME(HSM002) -  

   CYLINDER(4300 0)  -    

   RECORDSIZE(435 2040) FREESPACE(0 0)-    

   SPEED BUFFERSPACE(530432) -  

   INDEXED KEYS(44 0) SHAREOPTIONS(3 3)-   

   UNIQUE NOWRITECHECK)  -  

   DATA (NAME(PROD..HSM.MCDS.DATA) CISZ(12288) ) -

   INDEX (NAME(PROD..HSM.MCDS.INDEX) CISZ(2048))  
I think I am safe.  What says you?

On Monday, 26 November 2018, 7:15:32 pm GMT-5, Feller, Paul 
 wrote:  
 
 John, basically you are limited to 4 gig (HI-A-RBA) for the size of a 
non-extended VSAM dataset.  So depending on your VSAM define option you will 
get somewhere in the neighborhood of 6,000 cyls.  In my quick test I got around 
5,800 cyls.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Monday, November 26, 2018 12:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMS ALLOCATION OF VSAM DSN [EXTERNAL]

G'Day,
Could somebody please tell me what is the maximum number of cylinders that 
could be allocated for a SMS managed VSAM dsn (not VSAM EXTENDED 
ADDRESSABILITY). I have been able to allocate a dsn with 6,000 cylinders.  
However, due to a lack of disk space I couldn't continue with a higher 
allocation.
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
Please note:  This message originated outside your organization. Please use 
caution when opening links or attachments.

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

SMS ALLOCATION OF VSAM DSN

[John Dawes]

G'Day,
Could somebody please tell me what is the maximum number of cylinders that 
could be allocated for a SMS managed VSAM dsn (not VSAM EXTENDED 
ADDRESSABILITY).  
I have been able to allocate a dsn with 6,000 cylinders.  However, due to a 
lack of disk space I couldn't continue with a higher allocation.
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SDSF INPUT ON/OFF

[John Dawes]

To add my 2 cents you can do the following
Activate SDSFThe main panel is displayed select the OPTIONS tabChoose option 3 
: Change include SYSIN to ON Go back to ST display.
We are running RELEASE z/OS 02.02.00

   On Tuesday, 28 August 2018, 9:29:44 pm GMT-4, Jesse 1 Robinson 
 wrote:  
 
 With a lot of off-list help, I finally got this working. Appears that I 
skipped way too many SHARE What's New in SDSF sessions over the past few years. 
Here's a summary of how to get it working in z/OS 2.1+.

-- Displaying inline SYSIN will work only on the ST(atus) display, not 
O(output) or H(old) display.  
-- If it's not working for you, issue command SET SCREEN  
-- Select 1.  Basic settings and tabular panels  
-- Select      Display the action bar        1  1. Yes  
-- On the action bar, click Options  
-- Select 2. Browse and Print...  
-- Select 2  Change include SYSIN to ON (if this OFF, then it's already ON)  
-- Go back to ST display  

At this point you can issue command INPUT ON. When you select a job on the ST 
screen with '?', you will see all JES2 data sets including inline SYSIN. 

Special thanks to Sri Kolusu and Tom Dien. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, August 28, 2018 3:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: SDSF INPUT ON/OFF

On Tue, 28 Aug 2018 21:01:37 +, Jesse 1 Robinson wrote:

>A colleague noticed that SDSF INPUT ON is not showing a SYSIN DD * data set. 
>It's supposed to, right? OTOH SJ for the job shows everything including inline 
>input. This is z/OS 2.3.
> 
"?" display, not "O" or "H", right?

My observation has been that it shows SYSINs but does not identify them by 
STEPNAME/DDNAME until they've been opened.  I suppose there's a reason, but 
hardly a good one.

-- gil


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

Re: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS MANAGED DISK

[John Dawes]

 You mention "bypass options".  Does this pertain to recalling the file to a 
non-SMS disk or SMS disk?  I would like to try out your suggestion.  
On Friday, 6 July 2018, 2:53:13 pm GMT-4, Gibney, Dave  
wrote:  
 
 There are bypass options, given sufficient authority. Of course, with 
sufficient authority, the ACS routines could be tweaked for the specific case 
during recall. :)

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Allan Staller
> Sent: Friday, July 06, 2018 11:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS
> MANAGED DISK
> 
> I don't think ADRDSSU will override the SMS specifications.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Gibney, Dave
> Sent: Friday, July 6, 2018 1:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS
> MANAGED DISK
> 
> 1. Pull it back. 2. Move it with ADDRDSSU
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Mike Schwab
> > Sent: Friday, July 06, 2018 11:24 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS
> > MANAGED DISK
> >
> > If that dataset needs a large allocation, quiesce a/that volume,
> > migrate the select volume to move unallocated datasets on it, defrag
> > to create larger extents, then recall it.  If no active volume has
> > enough space, it would go there.
> > On Fri, Jul 6, 2018 at 10:07 AM John Dawes <00ff0e22811f-dmarc-
> > requ...@listserv.ua.edu> wrote:
> > >
> > >  Allan,
> > > Thanks for your suggestion.  I looked at that option however being
> > > in the
> > Production cycle window I cannot do so because jobs could abend if I
> > do a DISNEW.
> > >    On Friday, 6 July 2018, 11:00:02 am GMT-4, Allan Staller
> >  wrote:
> > >
> > >  AFAIK, Guaranteed Space only (IMO) acceptable way to accomplish
> > > what
> > you've described.
> > >
> > > You could place all of the other volumes in the pool in QUIESCE or
> > > DISNEW
> > for the duration (IMO, not acceptable).
> > > You could make the ACS routine and SMS update to place the desired
> > > volume in its own SG, restore your data, and reverse the process.
> > > (Waaay tooo much work!)
> > >
> > > HTH,
> > >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Dawes
> > > Sent: Friday, July 6, 2018 9:48 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS
> > MANAGED
> > > DISK
> > >
> > > G'Day,
> > > Because of storage considerations I would like to recall some ML2
> > > SMS
> > managed dsns to a specific SMS managed disk.  I tried a few things e.g.
> > :HSEND RECALL 'CICSV2.XPD2.A7060.ZFE1' VOLUME(ZFE315) -  UNIT(3390)
> > However the dsn was not recalled to the desired disk.  I thought of
> > using the GUARANTEED SPACE storage class option as a work around.  I
> > checked the doc (DFSMShsm Storage Administration Guide) but I could
> > not find an example.  Is this possible to do?  If so, would anyone
> > have an example to share?
> > > Thanks.
> > >
> > > 
> > > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO
> > > IBM-MAIN
> > > ::DISCLAIMER::
> > > 
> > > --
> > > 
> > > --
> > > 
> > > --
> > > 
> > > The contents of this e-mail and any attachment(s) are confidential
> > > and
> > intended for the named recipient(s) only. E-mail transmission is not
> > guaranteed to be secure or error-free as information could be
> > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> > may contain viruses in transmission. The e mail and its contents (with
> > or without referred errors) shall 

Re: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS MANAGED DISK

[John Dawes]

 Allan,
Thanks for your suggestion.  I looked at that option however being in the 
Production cycle window I cannot do so because jobs could abend if I do a 
DISNEW.
On Friday, 6 July 2018, 11:00:02 am GMT-4, Allan Staller 
 wrote:  
 
 AFAIK, Guaranteed Space only (IMO) acceptable way to accomplish what you've 
described.

You could place all of the other volumes in the pool in QUIESCE or DISNEW for 
the duration (IMO, not acceptable).
You could make the ACS routine and SMS update to place the desired volume in 
its own SG, restore your data, and reverse the process. (Waaay tooo much work!)

HTH,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Friday, July 6, 2018 9:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: DFHSM QUESTION - RECALLING SMS DSNS TO A SPECIFIC SMS MANAGED DISK

G'Day,
Because of storage considerations I would like to recall some ML2 SMS managed 
dsns to a specific SMS managed disk.  I tried a few things e.g. :HSEND RECALL 
'CICSV2.XPD2.A7060.ZFE1' VOLUME(ZFE315) -  UNIT(3390)                           
                 However the dsn was not recalled to the desired disk.  I 
thought of using the GUARANTEED SPACE storage class option as a work around.  I 
checked the doc (DFSMShsm Storage Administration Guide) but I could not find an 
example.  Is this possible to do?  If so, would anyone have an example to share?
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--

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

Re: MERGECAT QUESTION

[John Dawes]

Jesse,

I noticed that in your example you do not have the DD1 statements which 
indicate on which disks the dsns exist.

Is it no longer required?  I remember that in the past I had to code in the jcl 
several DD1 statements when I was doing a REPRO MERGECAT.

Could you or somebody confirm?  I ran test using your example and it worked.  
Just want to be sure.

Sorry to sound like a doubting Thomas.  Catalog maintenance makes me nervous.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removing Catalog Entries for Datasets That Do Not Exist [Public Information]

[John Dawes]

Bill,I checked some of our migrated dsns.  They have the catalog entry as 
MIGRAT1 or MIGRAT2.  The status of MIGRAT (folks at FDR please correct me if I 
am wrong) indicates that the dsn was archived by FDR.

  From: "Usher, Darrold" <014f796d148d-dmarc-requ...@listserv.ua.edu>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Friday, 18 August 2017, 11:58
 Subject: Re: Removing Catalog Entries for Datasets That Do Not Exist [Public 
Information]
   
Did your try DEL 'dsname' NSCR?

Classification: Public Information


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rodatz, William J
Sent: Friday, August 18, 2017 10:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Removing Catalog Entries for Datasets That Do Not Exist

Hello Everyone,

Recently I discovered some datasets with "MIGRAT" as the volser.  These 
datasets had been migrated with DFHSM many years ago.  My organization is no 
longer running the product.  I am attempting to remove the dangling catalog 
entries which appears to be challenging.  The pubs say to use IEHPROGM with the 
SCRATCH function if (1) the dataset is non-SMS managed and (2) you know the 
dataset's volser prior to migration.  I don't what the original volser was and 
I don't know why it matters.  The catalog entry has only the dataset name and 
"MIGRAT" for the volser.

When I execute IEHPROGM, I get messages denoting that DFHSM is not active.  I 
am unable to move past this point.

Does anyone have an idea how the catalog entries can be removed?  Any input 
would be greatly appreciated.

Thank you.

Bill

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

Re: ISPF LINE COMMAND

[John Dawes]

John,I tried it out and it did what I asked for.  A massive thanks.

  From: John McKown <john.archie.mck...@gmail.com>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Thursday, 10 August 2017, 10:05
 Subject: Re: ISPF LINE COMMAND
   
On Thu, Aug 10, 2017 at 8:55 AM, John Dawes <
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

>  G'Day,
> Is there a line command equivalent to ROSCOE line command using CR?  Let
> me explain.
> 01 HSEND FIXCDS D TESTJOB.D286.T2041375.TTQM0003              DELETE
> -
> 02    PATCH(X'06' BITS(0.1.)) ODS(SYSTEST.FIXCDS)
> 03 HSEND FIXCDS D TESTJOB.D286.T2101225.TTQM0003              DELETE
> -
> 04 HSEND FIXCDS D TESTJOB.D286.T2120595.TTQM0003              DELETE
> -
> 05 HSEND FIXCDS D TESTJOB.D286.T2141244.TTQM0003              DELETE
> -
> 06 HSEND FIXCDS D TESTJOB.D286.T2203302.TTNRON70              DELETE
> -
> 07 HSEND FIXCDS D TESTJOB.D286.T2221294.TTQM0003              DELETE
> -
> 08 HSEND FIXCDS D TESTJOB.D288.T1345356.TMDMDE21              DELETE
> -
> 09 HSEND FIXCDS D TESTJOB.D295.T1345250.TMDMDE21              DELETE
> -
> 10 HSEND FIXCDS D TESTJOB.D298.T1045337.TPDMDE21              DELETE
> -
> 11 HSEND FIXCDS D TESTJOB.D299.T1345302.TMDMDE21              DELETE
> -
> 12 HSEND FIXCDS D TESTJOB.D300.T1045286.TPDMDE21              DELETE
> -
> In the above member I would like to copy line 02    PATCH(X'06'
> BITS(0.1.)) ODS(SYSTEST.FIXCDS) after each HSEND command.
> In ROSCOE (miss it dearly)  all I had to do is type CR in 02 and an A
> in 03 up to 12.  Does ISPF have something similar?
> Thanks in advance
>

​Yes,

Put a "C" (Copy)on line 2. On lines 3 through 11 put an "AK" (After Keep)
and a single "A" (After) on line 12.​


-- 
If you look around the poker table & don't see an obvious sucker, it's you.

Maranatha! <><
John McKown

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

ISPF LINE COMMAND

[John Dawes]

  G'Day,
Is there a line command equivalent to ROSCOE line command using CR?  Let me 
explain.
01 HSEND FIXCDS D TESTJOB.D286.T2041375.TTQM0003   DELETE -
02    PATCH(X'06' BITS(0.1.)) ODS(SYSTEST.FIXCDS)  
03 HSEND FIXCDS D TESTJOB.D286.T2101225.TTQM0003   DELETE -
04 HSEND FIXCDS D TESTJOB.D286.T2120595.TTQM0003   DELETE -
05 HSEND FIXCDS D TESTJOB.D286.T2141244.TTQM0003   DELETE -
06 HSEND FIXCDS D TESTJOB.D286.T2203302.TTNRON70   DELETE -
07 HSEND FIXCDS D TESTJOB.D286.T2221294.TTQM0003   DELETE -
08 HSEND FIXCDS D TESTJOB.D288.T1345356.TMDMDE21   DELETE -
09 HSEND FIXCDS D TESTJOB.D295.T1345250.TMDMDE21   DELETE -
10 HSEND FIXCDS D TESTJOB.D298.T1045337.TPDMDE21   DELETE -
11 HSEND FIXCDS D TESTJOB.D299.T1345302.TMDMDE21   DELETE -
12 HSEND FIXCDS D TESTJOB.D300.T1045286.TPDMDE21   DELETE -
In the above member I would like to copy line 02    PATCH(X'06' 
BITS(0.1.)) ODS(SYSTEST.FIXCDS) after each HSEND command.
In ROSCOE (miss it dearly)  all I had to do is type CR in 02 and an A in 
03 up to 12.  Does ISPF have something similar?
Thanks in advance 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Elardus,

Good suggestion but Big Blue has beaten me to the crying.  They have been 
crying all the way to the bank for decades !!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Radoslaw,

 Thanks for the example.  I will check out the syntax etc.  I will try it 
out.  Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Radoslaw,

 Thanks for the suggestion.  I will give it a try.  Regarding the option of 
using the IMPORT command to restore the dsn.  I am not sure how I can go about 
it.  Could you provide me an example.  I have used the IMPORT command to reorg 
CATALOGS and VSAM dsns but never to restore them.  Perhaps I could have 
misunderstood your suggestion?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Elardus,
    I took a fourth look.  No, the dsn is on one line.

  From: Elardus Engelbrecht 
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Friday, 14 July 2017, 9:43
 Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
   
Lizette Koehler wrote:

>I have not known DFDSS to truncate a dataset name.
>Can you post the control cards you used to restore the file and the ADR 
>messages that showed how it restored the file?

And also the full message(s) on all lines.

ADR418I it shows .A0 instead A001  <--- Is the '01' not perhaps on a second 
line???


>The DB2 Names are very long to begin with, so if you changed the dataset name 
>on restore, it might have just kicked it over the 44 char limit

I have seen that before. You rename something, new name is larger than 44 chars 
-> results are lots of trouble and grey hairs.

This is one of the many reasons why TYPRUN='NORUN' is useful.

Groete / Greetings
Elardus Engelbrecht

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

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Lizette,

Below is the output.  Look for message ADR418I.  You will notice that it is 
MPRAR.DSNDBC.CISDBYSS.MDO2IX.I0001.A0

Sorry for the misalignment of the output.

- RESTORE DATASET(INCLUDE(HDFQ.DSNDBC.CISDBYSS.MDO2IX.I0001.A001)) -   
  RENAMEU(**,MPRAR.**) -  
  INDDNAME(TAPE1) OUTDDNAME(DISK1) -
  CATALOG   
 ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE '
 ADR109I (R/I)-RI01 (01), 2017.194 13:38:53 INITIAL SCAN OF USER CONTROL STATEME
 ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK   
0ADR006I (001)-STEND(01), 2017.194 13:38:53 EXECUTION BEGINS
0ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN FULL 
VOLUME FORMAT AND WAS CREATED BY Z/OS DFSMSDSS VERSION
  2 RELEASE 1 MODIFICATION LEVEL 0 ON 2017.189 06:11:41 
0ADR395I (001)-SB105(01), DATA SET HDFQ.DSNDBD.CISDBYSS.MDO2IX.I0001.A001 
ALLOCATED WITH NEWNAME
  MPRAR.DSNDBD.CISDBYSS.MDO2IX.I0001.A001, ON VOLUME(S: 
TSS001
0ADR418I (001)-SB105(01), THE FOLLOWING COMPONENTS FOR CLUSTER 
MPRAR.DSNDBC.CISDBYSS.MDO2IX.I0001.A0 ON TSS001 MAY HAVE TO BE
  CATALOGED IN CATALOG SYS1.ICFCAT.INSTALL  
0  COMPONENT MPRAR.DSNDBD.CISDBYSS.MDO2IX.I0001.A001  
0ADR378I (001)-TDDS (02), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED 
FROM VOLUME TSB064
0  HDFQ.DSNDBC.CISDBYSS.MDO2IX.I0001.A001  
HDFQ.DSNDBD.CISDBYSS.MDO2IX.I0001.A001

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Another brilliant IBM moment.  When I restored the dataset with a rename (DB2 
linear dsn) guess what?The new name CLUSTER was truncated.  Besides the message 
ADR418I it shows .A0 instead A001 .I wasted 30 minutes trying to recatalog the 
cluster.  Finally I ran a print of the VVDS entry of the volume and lo and 
behold I found the cluster name.Thank you IBM for your useless product (DFDSS) 
.  Amen.

  From: John Dawes <00ff0e22811f-dmarc-requ...@listserv.ua.edu>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Friday, 14 July 2017, 7:18
 Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
   
Lizette,
The system default for DFDSS dump is set at 256K.  Isn't that fantastic?  Now 
there is no way we can ever copy a tape to dasd  because the lasrgest blksize 
supported for a DASD dataset is 32760 bytes.  IBM increased the blksize for 
tape but not DASD.  Brilliant !!! 

Thanks to all who responded.

      From: Lizette Koehler <stars...@mindspring.com>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Thursday, 13 July 2017, 13:42
 Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
  
@JohnD

I think the problem is the LBI.  The DUMP tape was create with a HUGE Blksize.  
You cannot copy that to DASD.  Maybe you can change the way the DUMP tape is 
created to use a BLKSIZE like 32760.  Then you can probably use COPYDUMP to 
copy it to DISK.

>From what I can tell, you could only copy tape to tape.

Maybe restore the files to a disk, then backup the disk manually with DFDSS


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Dawes
> Sent: Thursday, July 13, 2017 9:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> Rex,
> I tried your suggestion.  I tried copying the tape to another tape
> using DCB=BLKSIZE=27998.  However I got the same result :ADR331E (001)-CPYD
> (01), OUTPUT BLKSIZE 27998 FOR DATA SET ON DDNAME COPY1 IS SMALER THAN INPUT
> BLKSIZE 262144.
>      From: "Pommier, Rex" <rpomm...@sfgmembers.com>
>  To: IBM-MAIN@LISTSERV.UA.EDU
>  Sent: Thursday, 13 July 2017, 12:15
>  Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> John,
> 
> Based on error ADR331E, it appears that the only way you could do this would
> be if you had created the original tape backup using a block size of 32K - or
> 27998.  That message explicitly states that you cannot copy a dump dataset to
> something with a smaller block size.
> 
> Rex
> 
> -----Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Dawes
> Sent: Thursday, July 13, 2017 10:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> I am trying to copy a volume backup (which was created by DFDSS)  to disk,
> using DFDSS. However I am encountering problems doing so.I tried
> using DCB=BLKSIZE=32760 to no avail.  I tried running the job without the DCB
> and it returned the same result (ADR324E).  According to the doc(SC23-6868-
> 01) this is feasible:
> 
> "With the COPYDUMP command, you can make from 1 to 255 copies ofDFSMSdss-
> produced dump data. The data to be copied, a sequential data set, canbe on a
> tape or a DASD volume, and copies can be written to a tape or a DASDvolume."
> Here is my job :
> //STEP1  EXEC PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES' //SYSPRINT
> DD SYSOUT=*                                            //BACKUP  DD
> DISP=OLD,                                          //            DSN=HDFQ.DF
> DSS.TSB063.COPY1.WEEK(0)                //COPY1    DD
> DISP=(,CATLG,DELETE),                              //            DSN=SYS1.DF
> DSS.COPYTAPE,                            //            UNIT=3390,VOL=SER=SPAR
> E1,,                          //            SPACE=(CYL,(3200,20),RLSE),DCB=B
> LKSIZE=32760    //SYSIN    DD
> *                                                    COPYDUMP -
>                                                            INDD(BACKUP) -
>                                                    OUTDD(COPY1)
>                                      /* here is the output messages:
> COPYDUMP-
> 
>    INDD(BACKUP) -
> 
> 
>    OUTDD(COPY1)
> 
> 
> ADR101I(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPYDUMP
> '
> 
> ADR109I(R/I)-RI01 (01), 2017.194 10:55:25 INITIAL SCAN OF USER CONTROL
> STATEMEN
> 
> ADR016I(001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS
> TASK
> 
> ADR006I(001)-STEND(01), 2017.194 10:55:25 EXECUTION
> BEGINS
> 
> ADR331E(001)-CPYD (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS
> SMALLERTHAN INPUT BLKSIZE 262144
> 
> ADR3

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Lizette,
The system default for DFDSS dump is set at 256K.  Isn't that fantastic?  Now 
there is no way we can ever copy a tape to dasd  because the lasrgest blksize 
supported for a DASD dataset is 32760 bytes.  IBM increased the blksize for 
tape but not DASD.  Brilliant !!! 

Thanks to all who responded.

  From: Lizette Koehler <stars...@mindspring.com>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Thursday, 13 July 2017, 13:42
 Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
   
@JohnD

I think the problem is the LBI.  The DUMP tape was create with a HUGE Blksize.  
You cannot copy that to DASD.  Maybe you can change the way the DUMP tape is 
created to use a BLKSIZE like 32760.  Then you can probably use COPYDUMP to 
copy it to DISK.

>From what I can tell, you could only copy tape to tape.

Maybe restore the files to a disk, then backup the disk manually with DFDSS


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Dawes
> Sent: Thursday, July 13, 2017 9:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> Rex,
> I tried your suggestion.  I tried copying the tape to another tape
> using DCB=BLKSIZE=27998.  However I got the same result :ADR331E (001)-CPYD
> (01), OUTPUT BLKSIZE 27998 FOR DATA SET ON DDNAME COPY1 IS SMALER THAN INPUT
> BLKSIZE 262144.
>      From: "Pommier, Rex" <rpomm...@sfgmembers.com>
>  To: IBM-MAIN@LISTSERV.UA.EDU
>  Sent: Thursday, 13 July 2017, 12:15
>  Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> John,
> 
> Based on error ADR331E, it appears that the only way you could do this would
> be if you had created the original tape backup using a block size of 32K - or
> 27998.  That message explicitly states that you cannot copy a dump dataset to
> something with a smaller block size.
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Dawes
> Sent: Thursday, July 13, 2017 10:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
> 
> I am trying to copy a volume backup (which was created by DFDSS)  to disk,
> using DFDSS. However I am encountering problems doing so.I tried
> using DCB=BLKSIZE=32760 to no avail.  I tried running the job without the DCB
> and it returned the same result (ADR324E).  According to the doc(SC23-6868-
> 01) this is feasible:
> 
> "With the COPYDUMP command, you can make from 1 to 255 copies ofDFSMSdss-
> produced dump data. The data to be copied, a sequential data set, canbe on a
> tape or a DASD volume, and copies can be written to a tape or a DASDvolume."
> Here is my job :
> //STEP1  EXEC PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES' //SYSPRINT
> DD SYSOUT=*                                            //BACKUP  DD
> DISP=OLD,                                          //            DSN=HDFQ.DF
> DSS.TSB063.COPY1.WEEK(0)                //COPY1    DD
> DISP=(,CATLG,DELETE),                              //            DSN=SYS1.DF
> DSS.COPYTAPE,                            //            UNIT=3390,VOL=SER=SPAR
> E1,,                          //            SPACE=(CYL,(3200,20),RLSE),DCB=B
> LKSIZE=32760    //SYSIN    DD
> *                                                    COPYDUMP -
>                                                            INDD(BACKUP) -
>                                                    OUTDD(COPY1)
>                                      /* here is the output messages:
> COPYDUMP-
> 
>    INDD(BACKUP) -
> 
> 
>    OUTDD(COPY1)
> 
> 
> ADR101I(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPYDUMP
> '
> 
> ADR109I(R/I)-RI01 (01), 2017.194 10:55:25 INITIAL SCAN OF USER CONTROL
> STATEMEN
> 
> ADR016I(001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS
> TASK
> 
> ADR006I(001)-STEND(01), 2017.194 10:55:25 EXECUTION
> BEGINS
> 
> ADR331E(001)-CPYD (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS
> SMALLERTHAN INPUT BLKSIZE 262144
> 
> ADR324E(001)-CPYD (01), THE VOLUME/DATA SET SPECIFIED BY DDNAME COPY1 HAS
> BECOME UNUSABLE
> 
> ADR006I(001)-STEND(02), 2017.194 10:55:59 EXECUTION
> ENDS
> 
> ADR013I(001)-CLTSK(01), 2017.194 10:55:59 TASK COMPLETED WITH RETURN CODE
> 0016
> 
> ADR012I(SCH)-DSSU (01), 2017.194 10:55:59 DFSMSDSS PROCESSING COMPLETE.
> HIGHEST
> 
>                          TASK    001
> 
> 
> Can someone advise me how to fix the problem?
> Thanks.
> 

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

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Rex,

Thanks for the help.  I checked.  The system default for DFDSS is set at 256K.  
The reason why I cannot restore the datasets is because the volumes are SMS 
managed LPAR(A) and the backup is done from another LPAR(B).  The SMS 
configurations are not the same on LPAR A & B.  However the disks are visible 
from both the LPARs.  Why is the backup not taken on LPAR(A) pray tell?  This 
is because of CPU constraints.
   
A work around I devised is that I restored the dataset to a new name on LPAR(B) 
 then I did a copy of the dataset to the original name from LPAR(A).  

Oh! What a tangled web we weave ..

I hope that I was able to explain myself clearly.

G'day.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

Rex,
I tried your suggestion.  I tried copying the tape to another tape using 
DCB=BLKSIZE=27998.  However I got the same result :ADR331E (001)-CPYD (01), 
OUTPUT BLKSIZE 27998 FOR DATA SET ON DDNAME COPY1 IS SMALER THAN INPUT BLKSIZE 
262144.
  From: "Pommier, Rex" <rpomm...@sfgmembers.com>
 To: IBM-MAIN@LISTSERV.UA.EDU 
 Sent: Thursday, 13 July 2017, 12:15
 Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E
   
John,

Based on error ADR331E, it appears that the only way you could do this would be 
if you had created the original tape backup using a block size of 32K - or 
27998.  That message explicitly states that you cannot copy a dump dataset to 
something with a smaller block size.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Thursday, July 13, 2017 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

I am trying to copy a volume backup (which was created by DFDSS)  to disk, 
using DFDSS. However I am encountering problems doing so.I tried using 
DCB=BLKSIZE=32760 to no avail.  I tried running the job without the DCB and it 
returned the same result (ADR324E).  According to the doc(SC23-6868-01) this is 
feasible:

"With the COPYDUMP command, you can make from 1 to 255 copies 
ofDFSMSdss-produced dump data. The data to be copied, a sequential data set, 
canbe on a tape or a DASD volume, and copies can be written to a tape or a 
DASDvolume."
Here is my job :
//STEP1   EXEC PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES' //SYSPRINT DD 
SYSOUT=*                                            //BACKUP   DD DISP=OLD,     
                                      //            
DSN=HDFQ.DFDSS.TSB063.COPY1.WEEK(0)                 //COPY1    DD 
DISP=(,CATLG,DELETE),                               //            
DSN=SYS1.DFDSS.COPYTAPE,                            //            
UNIT=3390,VOL=SER=SPARE1,,                           //            
SPACE=(CYL,(3200,20),RLSE),DCB=BLKSIZE=32760     //SYSIN    DD *                
                                    COPYDUMP -                                  
                         INDD(BACKUP) -                                         
           OUTDD(COPY1)                                                  /*     
                                                           
here is the output messages:
COPYDUMP-

    INDD(BACKUP) - 

    OUTDD(COPY1)   

ADR101I(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPYDUMP '    

ADR109I(R/I)-RI01 (01), 2017.194 10:55:25 INITIAL SCAN OF USER CONTROL STATEMEN

ADR016I(001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK    

ADR006I(001)-STEND(01), 2017.194 10:55:25 EXECUTION BEGINS 

ADR331E(001)-CPYD (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS 
SMALLERTHAN INPUT BLKSIZE 262144

ADR324E(001)-CPYD (01), THE VOLUME/DATA SET SPECIFIED BY DDNAME COPY1 HAS 
BECOME UNUSABLE

ADR006I(001)-STEND(02), 2017.194 10:55:59 EXECUTION ENDS   

ADR013I(001)-CLTSK(01), 2017.194 10:55:59 TASK COMPLETED WITH RETURN CODE 0016 

ADR012I(SCH)-DSSU (01), 2017.194 10:55:59 DFSMSDSS PROCESSING COMPLETE. HIGHEST

 TASK    001    
                                                  

Can someone advise me how to fix the problem?
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


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

COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E

[John Dawes]

I am trying to copy a volume backup (which was created by DFDSS)  to disk, 
using DFDSS. However I am encountering problems doing so.I tried using 
DCB=BLKSIZE=32760 to no avail.  I tried running the job without the DCB and it 
returned the same result (ADR324E).  According to the doc(SC23-6868-01) this is 
feasible:

"With the COPYDUMP command, you can make from 1 to 255 copies 
ofDFSMSdss-produced dump data. The data to be copied, a sequential data set, 
canbe on a tape or a DASD volume, and copies can be written to a tape or a 
DASDvolume."
Here is my job :
//STEP1   EXEC PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES' //SYSPRINT DD 
SYSOUT=*                                            //BACKUP   DD DISP=OLD,     
                                      //            
DSN=HDFQ.DFDSS.TSB063.COPY1.WEEK(0)                 //COPY1    DD 
DISP=(,CATLG,DELETE),                               //            
DSN=SYS1.DFDSS.COPYTAPE,                            //            
UNIT=3390,VOL=SER=SPARE1,,                           //            
SPACE=(CYL,(3200,20),RLSE),DCB=BLKSIZE=32760     //SYSIN    DD *                
                                    COPYDUMP -                                  
                         INDD(BACKUP) -                                         
           OUTDD(COPY1)                                                  /*     
                                                           
here is the output messages:
COPYDUMP-

    INDD(BACKUP) - 

    OUTDD(COPY1)   

ADR101I(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPYDUMP '    

ADR109I(R/I)-RI01 (01), 2017.194 10:55:25 INITIAL SCAN OF USER CONTROL STATEMEN

ADR016I(001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK    

ADR006I(001)-STEND(01), 2017.194 10:55:25 EXECUTION BEGINS 

ADR331E(001)-CPYD (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS 
SMALLERTHAN INPUT BLKSIZE 262144

ADR324E(001)-CPYD (01), THE VOLUME/DATA SET SPECIFIED BY DDNAME COPY1 HAS 
BECOME UNUSABLE

ADR006I(001)-STEND(02), 2017.194 10:55:59 EXECUTION ENDS   

ADR013I(001)-CLTSK(01), 2017.194 10:55:59 TASK COMPLETED WITH RETURN CODE 0016 

ADR012I(SCH)-DSSU (01), 2017.194 10:55:59 DFSMSDSS PROCESSING COMPLETE. HIGHEST

 TASK    001    
                                                  

Can someone advise me how to fix the problem?
Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: help with DFDSS and LBI (large block interface)

[John Dawes]

I am able to do a tape to tape copy without any issues.  However tape to disk 
doesn't work because the default of tape blksize is 262144 and the maximum 
blksize that is supported for DASD is 32760.  I guess nothing can be done. 

On Fri, 16/6/17, Carmen Vitullo <cvitu...@hughes.net> wrote:

 Subject: Re: help with DFDSS and LBI (large block interface)
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Friday, 16 June, 2017, 3:12 PM
 
 a better example 
 tape to tape 
 
 
 
 //STEP1 EXEC
 PGM=ADRDSSU 
 //TAPEI DD
 DSN=OTCTR.OMVS19.DUMP, 
 //
 UNIT=3390,VOL=SER=(OTCTR3,OTCTR4),DISP=SHR 
 //TAPEO DD DSN=OTC.OMVS19.DUMP, 
 // UNIT=3390,VOL=SER=(OTC047,OTC053), 
 // DISP=(,CATLG),SPACE=(CYL,(1100,100)) 
 //SYSPRINT DD SYSOUT=* 
 //SYSIN
 DD * 
 COPYDUMP INDDNAME(TAPEI)
 OUTDDNAME(TAPEO) 
 IF LASTCC GT 0 - 
 THEN DO 
 WTO
 ''
 
 WTO '* DSSU TAPE COPY HAS
 ABENDED ! *' 
 WTO
 ''
 
 END 
 ELSE DO 
 WTO
 ''
 
 WTO '*** DSSU TAPE COPY HAS COMPLETED
 SUCCESSFULLY ! ' 
 WTO
 ''
 
 END 
 - Original Message
 -
 
 From: "Carmen
 Vitullo" <cvitu...@hughes.net>
 
 To: IBM-MAIN@LISTSERV.UA.EDU
 
 Sent: Friday, June 16, 2017 2:11:17 PM 
 Subject: Re: help with DFDSS and LBI (large
 block interface) 
 
 I've
 done this alot creating a second copy of a dump tape and
 never forced a blocksize - 
 
 //STEP1 EXEC PGM=ADRDSSU 
 //SYSPRINT DD SYSOUT=T 
 //INVOL1 DD VOL=SER=RMDS01,UNIT=3380,DISP=SHR
 
 //TAPE1 DD
 DISP=(,CATLG),DSN=x,UNIT=T3480,DCB=X 
 //SYSIN DD * 
 
 /SYSIN DD * 
 COPYDUMP
 INDDNAME(INVOL1) OUTDDNAME(TAPE1) 
 IF LASTCC
 GT 0 - 
 THEN DO 
 WTO
 '*++*'
 
 WTO '* COPYDUMP OF TECHD7
 ABENDED ! *' 
 WTO
 '*++*'
 
 END 
 ELSE DO 
 WTO
 '*++*'
 
 WTO '*** COPYDUMP OF TECHD7 COMPLETED
 SUCCESSFULLY ! ' 
 WTO
 '*++*'
 
 END - Original Message - 
 
 From: "Lizette
 Koehler" <stars...@mindspring.com>
 
 To: IBM-MAIN@LISTSERV.UA.EDU
 
 Sent: Friday, June 16, 2017 2:03:26 PM 
 Subject: help with DFDSS and LBI (large block
 interface) 
 
 This is from
 John Dawes who is having issues posting to IBMMAIN. I only
 have the following details 
 
 G'Day, 
 
 Here is the jcl: 
 //STEP1 EXEC
 PGM=ADRDSSU,REGION=0M,TIME=1440,PARM='UTILMSG=YES'
 
 //SYSPRINT DD SYSOUT=* 
 //BACKUP DD
 DISP=OLD,DSN=SYS2.STORDSK.BKUP.G0001V00 
 //COPY1 DD DISP=(,CATLG,DELETE), 
 // DSN=SYS2.DFDSS.BKUP2, 
 //
 UNIT=3490,VOL=(,,,99),DCB=BLKSIZE=32760 
 //SYSIN DD * 
 COPYDUMP - 
 INDD(BACKUP) - 
 OUTDD(COPY1)
 
 /* 
 I am trying to copy the
 tape (which has the default blksize of 262144). I 
 tried to force a blksize of 32760 so that it
 would be copied on to DASD in a 
 later step.
 
 Here is the error message of copying the
 tape to another tape: 
 ADR331E (001)-CPYD
 (01), OUTPUT BLKSIZE 32760 FOR DATA SET ON DDNAME COPY1 IS
 
 SMALLER THAN INPUT BLKSIZE 262144 ADR324E
 (001)-CPYD (01), THE VOLUME/DATA 
 SET
 SPECIFIED BY DDNAME COPY1 HAS BECOME UNUSABLE 
 
 The tape dsn does not have a
 DATACLAS. 
 
 I tried a copy
 of the tape to dasd which didn't work which prompted my
 first 
 post. To bypass the problem I tried
 to copy the tape to another tape with a 
 blksize of 32760 and encountered the above
 error. 
 
 
 --
 
 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

Re: SDSF in Batch

[John Dawes]

Sri,

I tried out your example and it worked like a charm.  Great stuff.  Thanks for 
sharing this with us.


On Tue, 30/5/17, Sri h Kolusu  wrote:

 Subject: Re: SDSF in Batch
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, 30 May, 2017, 3:11 PM
 
 Steely Mark,
 
 Assuming you always have more than 1 job to
 extract in the DA queue, you 
 can use SDSF
 block commands  (//X - //) and extract the entire log. 
 You 
 can use utility of choice ( I used
 SORT) to extract out the contents you 
 like.
 Some thing like this
 
 //**
 //* DELETE IF OUTPUT DATASET EXISTS       
                     *
 //**
 //STEP0100 EXEC PGM=IEFBR14 
 //DD01     DD  DSN=,
 
 //            
 DISP=(MOD,DELETE),UNIT=SYSDA, 
 //       
      SPACE=(TRK,(1,0),RLSE) 
 //* 
 //**
 //* EXTRACT THE ENTIRE JOB OUTPUTS IN DA FOR
 PREFIX 'CICS'     *
 //* USING SDSF
 BLOCK COMMANDS (//X - //)                      
 *
 //**
 //STEP0200 EXEC
 PGM=SDSF,PARM='++30,256' 
 //ISFOUT 
  DD SYSOUT=* 
 //SYSUDUMP DD SYSOUT=* 
 //SYSPRINT DD SYSOUT=* 
 //SYSTSPRT DD SYSOUT=* 
 //SYSOUT   DD SYSOUT=* 
 //DATAOUT  DD DSN=,
 
 //           
 DISP=(NEW,CATLG,DELETE), 
 //         
   SPACE=(CYL,(25,25),RLSE), 
 //       
     RECFM=FB,LRECL=133,BLKSIZE=0 
 //ISFIN    DD * 
 PRE CICS*
 
 DA 
 PRINT FILE DATAOUT 
 FIND 'CICS' 
 ++//X 
 FIND 'CICS' LAST 
 ++//
 
 PRINT CLOSE 
 END 
 /*
 //**
 //* EXTRACT THE JESMSGLG FOR EACH JOB LOOKING
 FOR THE TIME     *
 //**
 //STEP0300 EXEC PGM=SORT 
 //SYSOUT   DD SYSOUT=* 
 //SORTIN   DD
 DISP=SHR,DSN= 
 //SORTOUT  DD SYSOUT=* 
 //SYSIN    DD * 
   OPTION
 COPY 
   INCLUDE COND=(2,2,ZD,EQ,NUM,AND,
 
                
 4,1,CH,EQ,C'.',AND, 
          
       5,2,ZD,EQ,NUM,AND, 
          
       7,1,CH,EQ,C'.',AND, 
    
             8,2,ZD,EQ,NUM) 
 /*
 
 P.S : The block command will
 fail if you just have 1 active job in the DA 
 queue.
 
 Thanks,
 Kolusu
 
 
 
 From:   "Steely.Mark" 
 To:     IBM-MAIN@LISTSERV.UA.EDU
 Date:   05/30/2017 10:17 AM
 Subject:        SDSF in Batch
 Sent by:        IBM Mainframe Discussion
 List 
 
 
 
 I know this has been discussed before but I
 can't find anything that I am 
 looking
 for.
 
 The only thing I found
 close was SDSFEXT from file 313 on the CBTAPE.
 
 I would like the batch SDSF
 job to perform PREFIX CICS*.  Then DA.  Then 
 from that list print the JESMSGLG from each one
 listed.
 
 I have been able to
 do this successfully  for 1 job.
 
 Any help would be appreciated.
 
 Thanks
 
 
 --
 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

Re: DFDSS PROBLEM - DUMP USING STORGRP PARM

[John Dawes]

I am losing it.  Sorry.  The night shifts (because I am supporting daytime 
users) are killing me !!

Thanks to all.

On Tue, 30/5/17, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: DFDSS PROBLEM - DUMP USING STORGRP PARM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, 30 May, 2017, 7:24 AM
 
 John Dawes wrote:
 
 >> Last question.  From
 looking at the example below would backup be of a physical
 or logical format?.  
 
 Logical. Actually, you already gave
 yourself the answer in your first post. This is what you
 quoted:
 
 "If you specify the DATASET keyword
 with the LOGINDDNAME, LOGINDYNAM,or STORGRP keywords,
 DFSMSdss performs a logical data set dump by using
 information in the VTOCs to select data sets..."
 
 Just trying to put it all together...
 ;-)
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

Re: DFDSS PROBLEM - DUMP USING STORGRP PARM

[John Dawes]

Lizette,

 Thanks for the suggestion to use NORUN.

On Mon, 29/5/17, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: DFDSS PROBLEM - DUMP USING STORGRP PARM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Monday, 29 May, 2017, 7:24 PM
 
 Note:  The TYPRUN=NORUN  is the
 PARM input to DFDSS.
  
 
 I always Thought IBM could have done better
 with this name.
 
 //S1  EXEC
 PGM=ADRDSSU,PARM='TYPRUN=NORUN'
 
 
 
 Lizette
 
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Monday, May 29, 2017 1:36 PM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: DFDSS PROBLEM - DUMP USING
 STORGRP PARM
 > 
 >
 Elardus,
 > 
 > Thanks
 for the example.  I will give it a try and let you know how
 I fared.
 > Thanks again.
 > 
 >
 
 > On Mon, 29/5/17, Elardus Engelbrecht
 <elardus.engelbre...@sita.co.za>
 wrote:
 > 
 >  Subject:
 Re: DFDSS PROBLEM - DUMP USING STORGRP PARM
 >  To: IBM-MAIN@LISTSERV.UA.EDU
 >  Received: Monday, 29 May, 2017, 12:56
 PM
 > 
 >  John Dawes
 wrote:
 > 
 >  >Here
 is my job:
 >  >//SYSIN    DD *
 >  >  DUMP
 > 
 DATASET(INCLUDE(**)        -
 > 
 >
 >        EXCLUDE(SYS1.VVDS.**
 -
 >  >
 > 
 >  SYS1.VTOCIX.**) -
 >
 
 >  One ')' is missing. Add a
 ')' between
 >  ')' and
 '-'.
 > 
 > 
 >
 >  STORGRP(MVS003)      -
 >  >      OUTDD(TAPE)
 >  OPT(4) ALLDATA(*) ALLEXCP -
 >  >      SPHERE
 >            -
 > 
 >      TOL(ENQF)
 > 
 >  Test it with TYPRUN=HOLD and report
 >  back.
 > 
 >  HTH!
 > 
 >  Groete / Greetings
 >  Elardus Engelbrecht
 >
 
 > 
 --
 >  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

Re: DFDSS PROBLEM - DUMP USING STORGRP PARM

[John Dawes]

Elardus,

 Your suggestion worked.  Thanks for catching my error.  Last question.  
From looking at the example below would backup be of a physical or logical 
format?.  

 DUMP  DATASET(INCLUDE(**)-
  EXCLUDE(SYS1.VVDS.** -  
  SYS1.VTOCIX.**)) -  
STORGRP(MVS003)  -   
OUTDD(TAPE) OPT(4) ALLDATA(*) ALLEXCP -   
SPHERE-   
TOL(ENQF) 


On Mon, 29/5/17, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: DFDSS PROBLEM - DUMP USING STORGRP PARM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Monday, 29 May, 2017, 12:56 PM
 
 John Dawes wrote:
 
 >Here is my job:
 >//SYSIN    DD *
 >  DUMP 
 DATASET(INCLUDE(**)        -
 >         
       EXCLUDE(SYS1.VVDS.** -
 >         
              
 SYS1.VTOCIX.**) -
 
 One ')' is missing. Add a ')' between
 ')' and '-'.
 
 >     
 STORGRP(MVS003)      -
 >      OUTDD(TAPE)
 OPT(4) ALLDATA(*) ALLEXCP -
 >      SPHERE 
           -
 >      TOL(ENQF)
 
 Test it with TYPRUN=HOLD and report
 back.
 
 HTH!
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

Re: DFDSS PROBLEM - DUMP USING STORGRP PARM

[John Dawes]

Elardus,

Thanks for the example.  I will give it a try and let you know how I fared.  
Thanks again.


On Mon, 29/5/17, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: DFDSS PROBLEM - DUMP USING STORGRP PARM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Monday, 29 May, 2017, 12:56 PM
 
 John Dawes wrote:
 
 >Here is my job:
 >//SYSIN    DD *
 >  DUMP 
 DATASET(INCLUDE(**)        -
 >         
       EXCLUDE(SYS1.VVDS.** -
 >         
              
 SYS1.VTOCIX.**) -
 
 One ')' is missing. Add a ')' between
 ')' and '-'.
 
 >     
 STORGRP(MVS003)      -
 >      OUTDD(TAPE)
 OPT(4) ALLDATA(*) ALLEXCP -
 >      SPHERE 
           -
 >      TOL(ENQF)
 
 Test it with TYPRUN=HOLD and report
 back.
 
 HTH!
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

DFDSS PROBLEM - DUMP USING STORGRP PARM

[John Dawes]

G'Day,

I am trying to backup several dsns using the STORGRP parm while performing 
a dump of dsns for a particular SG.  My problem is that I cannot seem to get it 
to run.  I checked the doc (SC23-6868-01) for an example but I couldn't find 
one.  However it does show that STORGRP is supported:

  "If you specify the DATASET keyword with the LOGINDDNAME, LOGINDYNAM,or 
STORGRP keywords, DFSMSdss performs a logical data set dump by 
using information in the VTOCs to select data sets..."

Here is my job:
//STEP1   EXEC PGM=ADRDSSU,REGION=4096K,PARM='TYPRUN=NORUN' 
//SYSPRINT DD SYSOUT=*   
//SYSUDUMP DD SYSOUT=*   
//SYSMAP   DD SYSOUT=*   
//TAPE DD DSN=SYSD3.DUMP.TEST,DISP=(,CATLG,DELETE), 
//UNIT=3490,VOL=(,,,35)  
//SYSINDD *  
  DUMP  DATASET(INCLUDE(**)- 
EXCLUDE(SYS1.VVDS.** -   
SYS1.VTOCIX.**) -
  STORGRP(MVS003)  -
  OUTDD(TAPE) OPT(4) ALLDATA(*) ALLEXCP -
  SPHERE-
  TOL(ENQF)  
/*   
//

The job fails with a "ADR129E (001)-RI01 (01), KEYWORD 'STORGRP ' IS IMPROPER"  
  Can anybody point out my error?
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: REORGANIZING HSM CDS

[John Dawes]

To answer your question about the Listcats I do them to compare (before and 
after reorg).
I do have a separate job to backup the dsns (using logical DFDSS) in case 
something goes wrong.
You recommend to DELETE and recreate it.  Is there a reason why I should do so 
because the EXPORT/IMPORT will take care of that function. 

On Wed, 29/3/17, R.S. <r.skoru...@bremultibank.com.pl> wrote:

 Subject: Re: REORGANIZING HSM CDS
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 29 March, 2017, 11:22 AM
 
 In short words, there is
 no black magic here, it is regular VSAM KSDS 
 cluster, so any method to reorganize it is
 OK.
 I don't like your job because of
 irrational CONDs and disputable 
 LISTCATs
 (why ?)
 
 In general:
 1. Check your clusters using LISTCAT and/or
 EXAMINE if you want, but 
 definitely review
 the output before next step or just skip this step.
 2. Do a backup, of course "manual
 backup", do not use HSM. It can be 
 REPRO, EXPORT, or dss DUMP/COPY RENAMEU or
 whatever.
 2.1 Make sure, your backup is
 valid. You are allowed to do another 
 backup, using other method. You are not allowed
 to proceed if you are 
 unsure about
 backup...
 3. Delete CDS (and recreate it)
 and copy data from the backup to new 
 empty
 dataset.
 4. Have  a beer...
 
 BTW: it is good idea to review
 CDS parameters, especially space allocation.
 BTW2: For the step 2 I would consider REPRO
 OFILE(OUT) with //OUT DD 
 DISP=(,CATLG),LIKE=INPUT.FILE
 
 HTH
 
 -- 
 Radoslaw Skorupka
 Lodz, Poland
 
 
 
 
 
 
 
 W dniu 2017-03-29 o 16:43, John Dawes pisze:
 > G'Day,
 >
 > I am setting up a reorg job to reorganise
 the MCDS/BCDS/OCDS because they have reached the threshold
 of 95%.
 > I checked the doc IBM z/OS
 DFSMShsm Primer for an example.  I noticed that in the
 IMPORT step it is using parm IEMPTY:
 >
 IMPORT IDS(?UID.EXPORT.MCDS) ODS(?UID.MCDS) IEMPTY  because
 the cluster is being redefined.  Would it be a problem if I
 was not deleting the cluster and performed the IMPORT using
 the IEMPTY parm?
 > I have run a test with
 the IEMPTY parm and without and they both work.  My
 question is do I need to use the IEMPTY parm?
 > I read in the doc z/OS V1R9.0 DFSMShsm
 Storage Administration Guide that the IMPORT function
 redefines a VSAM data set by using a copy of the catalog
 information saved in the EXPORT copy of the data set
 >
 > Here is my jcl:
 > //STEP1    EXEC
 PGM=IDCAMS,COND=(0,NE)
 > //SYSPRINT DD 
 SYSOUT=*
 >
 //SYSIN   DD   *
 >   LISTC ENT(SYS2.MCDS) ALL
 > /*
 >
 //STEP2   EXEC PGM=IEFBR14,COND=(0,NE)
 > //MCDS    DD
 DSNAME=SYS2.MCDS.BKUP,UNIT=SYSALLDA,
 >
 //        DISP=(,CATLG,DELETE),SPACE=(CYL,(250,200))
 > /*
 >
 //STEP3   EXEC PGM=IDCAMS,COND=(0,NE,STEP4)
 > //SYSPRINT DD  SYSOUT=*
 > //SYSIN   DD   *
 >    EXPORT SYS2.MCDS ODS(SYS2.MCDS.BKUP)
 TEMPORARY
 > /*
 >
 //STEP4   EXEC PGM=IDCAMS,COND=(0,NE)
 > //SYSPRINT DD  SYSOUT=*
 > //SYSIN   DD   *
 >    IMPORT IDS(SYS2.MCDS.BKUP)
 ODS(SYS2.MCDS) IEMPTY
 > /*
 > //STEP5     EXEC
 PGM=IDCAMS,COND=(0,NE)
 > //SYSPRINT DD 
 SYSOUT=*
 >
 //SYSIN   DD   *
 >   LISTC ENT(SYS2.MCDS) ALL
 > /*
 >
 >
 --
 > For IBM-MAIN subscribe / signoff / archive
 access instructions,
 > send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN
 >
 
 
 
 ==
 
 
        
 --
         Treść tej wiadomości może
 zawierać informacje prawnie chronione Banku przeznaczone
 wyłącznie do użytku służbowego adresata. Odbiorcą
 może być jedynie jej adresat z wyłączeniem dostępu
 osób trzecich. Jeżeli nie jesteś adresatem niniejszej
 wiadomości lub pracownikiem upoważnionym do jej
 przekazania adresatowi, informujemy, że jej
 rozpowszechnianie, kopiowanie, rozprowadzanie lub inne
 działanie o podobnym charakterze jest prawnie zabronione i
 może być karalne. Jeżeli otrzymałeś tę wiadomość
 omyłkowo, prosimy niezwłocznie zawiadomić nadawcę
 wysyłając odpowiedź oraz trwale usunąć tę wiadomość
 włączając w to wszelkie jej kopie wydrukowane lub
 zapisane na dysku.
 
      
   This e-mail may contain legally privileged information of
 the Bank and is intended solely for business use of the
 addressee. This e-mail may only be received by the addressee
 and may not be disclosed to any third parties. If you are
 not the intended addressee of this e-mail or the employee
 authorized to forward it to the addressee, be advised that
 any dissemination, copying, distribution or any other
 similar activity is legally prohibited and may be
 punishable. If you received this e-mail by mistake please
 advise the sender immediately by using the reply facility in
 your e-mail software and delete permanently this e-mail
 including any copies of it either printed or saved to hard
 dr

REORGANIZING HSM CDS

[John Dawes]

G'Day,

I am setting up a reorg job to reorganise the MCDS/BCDS/OCDS because they have 
reached the threshold of 95%.
I checked the doc IBM z/OS DFSMShsm Primer for an example.  I noticed that in 
the IMPORT step it is using parm IEMPTY:
IMPORT IDS(?UID.EXPORT.MCDS) ODS(?UID.MCDS) IEMPTY  because the cluster is 
being redefined.  Would it be a problem if I was not deleting the cluster and 
performed the IMPORT using the IEMPTY parm?
I have run a test with the IEMPTY parm and without and they both work.  My 
question is do I need to use the IEMPTY parm?
I read in the doc z/OS V1R9.0 DFSMShsm Storage Administration Guide that the 
IMPORT function redefines a VSAM data set by using a copy of the catalog 
information saved in the EXPORT copy of the data set

Here is my jcl:
//STEP1EXEC PGM=IDCAMS,COND=(0,NE) 
//SYSPRINT DD  SYSOUT=*
//SYSIN   DD   *   
 LISTC ENT(SYS2.MCDS) ALL  
/* 
//STEP2   EXEC PGM=IEFBR14,COND=(0,NE) 
//MCDSDD DSNAME=SYS2.MCDS.BKUP,UNIT=SYSALLDA,  
//DISP=(,CATLG,DELETE),SPACE=(CYL,(250,200))   
/* 
//STEP3   EXEC PGM=IDCAMS,COND=(0,NE,STEP4)
//SYSPRINT DD  SYSOUT=*
//SYSIN   DD   *   
  EXPORT SYS2.MCDS ODS(SYS2.MCDS.BKUP) TEMPORARY   
/* 
//STEP4   EXEC PGM=IDCAMS,COND=(0,NE)  
//SYSPRINT DD  SYSOUT=*
//SYSIN   DD   *   
  IMPORT IDS(SYS2.MCDS.BKUP) ODS(SYS2.MCDS) IEMPTY 
/* 
//STEP5 EXEC PGM=IDCAMS,COND=(0,NE)
//SYSPRINT DD  SYSOUT=*   
//SYSIN   DD   *  
 LISTC ENT(SYS2.MCDS) ALL 
/* 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: $AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS

[John Dawes]

When I hit PF1 it brings me to the TUTORIAL--- $AVRS SELECTION 
DIRECTORY TUTORIAL.  There is a section for the LOCATE COMMAND and it doesn't 
say anything about not supporting the LOCATE command when viewing TYPE  ==> AH 
.  I check in with the vender.

Thanks to all who responded.

On Wed, 1/2/17, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: $AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 1 February, 2017, 7:10 PM
 
 In ISPF I know this
 works.
 
 Enter the invalid
 command.  When you get the error in Top Right Hand Corner,
 hit PF1 (once may be twice) and it should take you to a help
 panel. 
 
 Not sure how good
 the $AVERS Help panels are.
 
 Lizette
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Wednesday, February 01, 2017 4:24
 PM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: $AVRS QUESTION - LOCATING
 SPECIFIC ARCHIVE JOBS
 > 
 > I did the PF1 but it was no help.  I will
 open a ticket with ROCKET software
 > (I
 think they are the vendor) Thanks.
 >
 
 > On Wed, 1/2/17, Leonardo Vaz <leonardo@cn.ca>
 wrote:
 > 
 >  Subject:
 Re: $AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS
 >  To: IBM-MAIN@LISTSERV.UA.EDU
 >  Received: Wednesday, 1 February, 2017,
 4:14 PM
 > 
 >  Good
 Point Lizette, PF1
 >  also states it
 should work under archive; John, I would open  a case with
 the
 > vendor.
 > 
 >  Leo
 > 
 -Original
 >  Message-
 >  From: IBM Mainframe Discussion
 >  List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 >  On Behalf Of Lizette Koehler
 >  Sent:
 >  Wednesday,
 February 01, 2017 4:07 PM
 >  To: IBM-MAIN@LISTSERV.UA.EDU
 >  Subject: Re: $AVRS QUESTION - LOCATING
 SPECIFIC  ARCHIVE JOBS
 > 
 >  Did you
 >  contact
 the vendor for assistance?
 > 
 >  Do the manuals indicating anything?
 > 
 >  Did you try PF1
 (HELP) while
 >  in the Panel? 
 Sometimes vendors supply decent help  panels.
 > 
 >  Lizette
 > 
 >  >
 -Original
 >  Message-
 >  > From: IBM Mainframe
 >  Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 > 
 >  > On Behalf Of
 John Dawes
 >  > Sent: Wednesday,
 February 01, 2017 8:30  AM  > To: IBM-MAIN@LISTSERV.UA.EDU
 > > Subject: $AVRS QUESTION - LOCATING 
 SPECIFIC ARCHIVE JOBS  >  > G'Day,  > 
 >
 > When I am in the JN or job display
 option  panel in $AVRS ($AVRS JOB  >
 > SELECTION) I  am able to locate the job
 output for a specific job by  >
 >
 issuing the command L TMSBKUP in the  command line. 
 However when I am  > in
 > the $AVRS
 ARCHIVE HISTORY SELECTION or AH option panel the  command
 does not
 > work.
 > 
 > Is the command L
 >  X supported
 or is there another command I need to  issue?
 >  > Below is a screen display of the
 >  ARCHIVE HISTORY selection:
 >  >
 >  > - WED
 01 FEB 2017.032  $AVRS ARCHIVE
 > 
 HISTORY SELECTION - ROW 3782 OF 46000  > COMMAND
 ===>
 >                     
             SCROLL
 >  ===>
 CUR
 >  > SELECT AN ENTRY:
 >  B=DSPLY,P=PRT
 > 
 >    SEL# ACT  JOBNAME
 >    JOB #
 TYP RESPUN     START DATE
 > 
 TIME        LINES
 >  > _ 
 3782
 >  TMSBKUP  0028364
 JOB   NO   FRI 19
 >  AUG 2016.232 05:00     
    146
 >  > _  3783   
   TMSBKUP  0028740
 > 
 JOB   NO   FRI 19 AUG 2016.232
 05:15
 >         147
 >  > _  3784
 >   
 TMSBKUP  0028869 JOB   NO   FRI 19
 >  AUG 2016.232 05:30     
    147
 >  > _  3785   
   TMSBKUP  0029016
 > 
 JOB   NO   FRI 19 AUG 2016.232
 05:45
 >         147
 >  > _  3786
 >   
 TMSBKUP  0029084 JOB   NO   FRI 19
 >  AUG 2016.232 06:00     
    147
 >  >
 >  > Thanks.
 > 
 
 --
 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

Re: $AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS

[John Dawes]

I did the PF1 but it was no help.  I will open a ticket with ROCKET software (I 
think they are the vendor)  
Thanks.

On Wed, 1/2/17, Leonardo Vaz <leonardo@cn.ca> wrote:

 Subject: Re: $AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 1 February, 2017, 4:14 PM
 
 Good Point Lizette, PF1
 also states it should work under archive; John, I would open
 a case with the vendor.
 
 Leo
 -Original
 Message-
 From: IBM Mainframe Discussion
 List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of Lizette Koehler
 Sent:
 Wednesday, February 01, 2017 4:07 PM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: $AVRS QUESTION - LOCATING SPECIFIC
 ARCHIVE JOBS
 
 Did you
 contact the vendor for assistance?
 
 Do the manuals indicating anything?
 
 Did you try PF1 (HELP) while
 in the Panel?  Sometimes vendors supply decent help
 panels.
 
 Lizette
 
 > -Original
 Message-
 > From: IBM Mainframe
 Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 
 > On Behalf Of John Dawes
 > Sent: Wednesday, February 01, 2017 8:30
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: $AVRS QUESTION - LOCATING
 SPECIFIC ARCHIVE JOBS
 > 
 > G'Day,
 > 
 > When I am in the JN or job display option
 panel in $AVRS ($AVRS JOB 
 > SELECTION) I
 am able to locate the job output for a specific job by 
 > issuing the command L TMSBKUP in the
 command line.  However when I am 
 > in
 the $AVRS ARCHIVE HISTORY SELECTION or AH option panel the
 command does not work.
 > Is the command L
 X supported or is there another command I need to
 issue?
 > Below is a screen display of the
 ARCHIVE HISTORY selection:
 > 
 > - WED 01 FEB 2017.032  $AVRS ARCHIVE
 HISTORY SELECTION - ROW 3782 OF 46000
 > COMMAND ===>                 
                                 SCROLL
 ===> CUR
 > SELECT AN ENTRY:
 B=DSPLY,P=PRT
 >    SEL# ACT  JOBNAME 
   JOB # TYP RESPUN     START DATE     
 TIME        LINES
 > _  3782     
 TMSBKUP  0028364 JOB   NO   FRI 19
 AUG 2016.232 05:00         146
 > _  3783      TMSBKUP  0028740
 JOB   NO   FRI 19 AUG 2016.232 05:15 
        147
 > _  3784   
   TMSBKUP  0028869 JOB   NO   FRI 19
 AUG 2016.232 05:30         147
 > _  3785      TMSBKUP  0029016
 JOB   NO   FRI 19 AUG 2016.232 05:45 
        147
 > _  3786   
   TMSBKUP  0029084 JOB   NO   FRI 19
 AUG 2016.232 06:00         147
 > 
 > Thanks.
 
 --
 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

$AVRS QUESTION - LOCATING SPECIFIC ARCHIVE JOBS

[John Dawes]

G'Day,

When I am in the JN or job display option panel in $AVRS ($AVRS JOB SELECTION) 
I am able to locate the job output for a specific job by issuing the command 
L TMSBKUP in the command line.  However when I am in the $AVRS ARCHIVE HISTORY 
SELECTION or AH option panel the command does not work.  
Is the command L X supported or is there another command I need to issue?  
Below is a screen display of the ARCHIVE HISTORY selection:

- WED 01 FEB 2017.032  $AVRS ARCHIVE HISTORY SELECTION - ROW 3782 OF 46000
COMMAND ===>  SCROLL ===> CUR 
SELECT AN ENTRY: B=DSPLY,P=PRT
   SEL# ACT  JOBNAMEJOB # TYP RESPUN START DATE  TIMELINES
_  3782  TMSBKUP  0028364 JOB   NO   FRI 19 AUG 2016.232 05:00 146
_  3783  TMSBKUP  0028740 JOB   NO   FRI 19 AUG 2016.232 05:15 147
_  3784  TMSBKUP  0028869 JOB   NO   FRI 19 AUG 2016.232 05:30 147
_  3785  TMSBKUP  0029016 JOB   NO   FRI 19 AUG 2016.232 05:45 147
_  3786  TMSBKUP  0029084 JOB   NO   FRI 19 AUG 2016.232 06:00 147

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

Thanks Elardus.  I will check around with our MVS gurus to see if I can remove 
the command.

On Thu, 8/12/16, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 8 December, 2016, 11:23 AM
 
 John Dawes wrote:
 
 >Thanks Elardus.  
 
 You're most welcome! ;-)
 
 First thing first - perhaps you should remove that command
 from the batch job you discovered.
 
 
 >What does "Host view  is consistent with subsystem
 view of control unit and device  function status.' I am
 unable to understand IBM speak.
 
 Neither me...
 
 
 >Could you elaborate or give an example as to what it
 means?
 
 I wish I could elaborate on that, but as a previous storage
 admin + MVS admin, I remember that during the configuration
 of the devices and later VARY ONLINE, somehow the definition
 of the control units and their devices are placed somewhere
 in a table after the system and control units have a 'chat'
 about defined devices / control units. 
 
 Other things considered: how the device is shared, what
 paths and what control units are connected to what LPAR /
 SysPlex, how the caching is defined/working.
 
 What I know, is when you IPL, the operating system use the
 IODEVICE macros for example and scan the IO config or using
 your setup in HCD. Only devices which are initialized and
 varied online are available for use. The system is 'talking'
 with each control unit and then establish tables for each
 devices and control units. Of course your CE should get
 those devices ready for use.
 
 But see Bill Woodger's excellent comments about system
 control blocks.
 
 So if a device is 'boxed' or in a similar status, the
 operating system, the hardware on the computer and control
 unit are not 100% agreeing with the real status of a device.
 Hence those DS commands as an aid amongst other things for
 you.
 
 One example I know is, if you vary a device offline on one
 LPAR, but the device is in use in the same LPAR or other
 LPAR in same or other SysPlex. Then you get some
 inconsistency. This is messy enough that I locked up the
 VARY command in RACF.
 
 Above is based on my frail and faint memory as storage
 admin. 
 
 Perhaps others can chime in with better examples or pointers
 to good documentation.
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

Thanks Elardus.  What does "Host view  is consistent with subsystem view of 
control unit and device  function status.' I am unable to understand IBM speak.
Could you elaborate or give an example as to what it means?

Thanks.

On Thu, 8/12/16, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 8 December, 2016, 9:23 AM
 
 John Dawes wrote:
 
 >There is no information posted in the job however this
 is what I found in the SYSLOG:
 
 >DS QD,4470,VALIDATE
  UNIT VOLSER SCUTYPE DEVTYPE   
    CYL  SSID SCU-SERIAL DEV-SERIAL EFC 
 >04070 DTB064 2107900 2107900     
 3339  4040 XX75-67054 XX75-67054 *OK 
 >      1 DEVICE(S) MET THE SELECTION
 CRITERIA             
          
 >      0 DEVICE(S) FAILED EXTENDED
 FUNCTION CHECKING           
     
 
 Thanks, I just looked at that EFS which caught my
 attention.
 
 Hmmm, according to the fine doc, that '*OK' says 'Host view
 is consistent with subsystem view of control unit and device
 function status.'
 
 I see you have indeed a valid concern after I reread the
 fine docs. Perhaps you should ask IBM for assistance if you
 can't get answers from this list?
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

Elardus,

There is no information posted in the job however this is what I found in the 
SYSLOG:

DS QD,4470,VALIDATE

 UNIT VOLSER SCUTYPE DEVTYPE   CYL  SSID SCU-SERIAL DEV-SERIAL EFC 
04070 DTB064 2107900 2107900  3339  4040 XX75-67054 XX75-67054 *OK 
  1 DEVICE(S) MET THE SELECTION CRITERIA   
  0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING



On Wed, 7/12/16, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:

 Subject: Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 7 December, 2016, 12:27 PM
 
 John Dawes wrote:
 
 >Could someone clear up what the command DS
 QD,413Z,VALIDATE actually do?  The doc says the
 following:
 
 >VALIDATE : Uses status information acquired directly
 from a device to correct inconsistent extended function
 status information maintained in host processor storage.
 VALIDATE has no effect if the unit address has no physical
 device attached
 
 >I am not sure what "to correct inconsistent extended
 function.." does.  Is it safe to use? Could you please
 help me understand IBM's explanation because it is not
 clear.
 
 Since it is a 'DISPLAY' command, it is indeed safe to issue
 the command. What are you seeing in the console/syslog?
 
 It depends of course what is shown, then it should be
 obvious what next you should be doing.
 
 Just post the result if you can. If you can and device is
 shared, repeat the display from another LPAR, just to be
 sure.
 
 About IBM's explanation, I'm sorry, but I can't help without
 specific results of your display command.
 
 Oh, IBM's docs can sometimes be really that hard to read...
 ;-)
 
 Groete / Greetings
 Elardus Engelbrecht
 
 --
 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

Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

Bill,

Thanks for the explanation.  Just for the record the addresses are online which 
raised my concern when I read the doc which states "VALIDATE has no effect if 
the unit address has no  physical device attached" .  As you said that it could 
update something which confirms my suspicions.


On Wed, 7/12/16, Bill Woodger  wrote:

 Subject: Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 7 December, 2016, 1:45 PM
 
 "In addition, there is one action
 parameter, VALIDATE" says the documentation. That, coupled
 with "VALIDATE has no effect if the unit address has no
 physical device attached" is a pretty strong indication that
 there is an actual effect from VALIDATE.
 
 "Use the dump selection parameters, to define the contents
 of the display. Beyond the basic status information, you can
 specify which of the following MVS™ system control blocks,
 and/or what information acquired directly from the following
 device information buffers, to display in hexadecimal
 format.
 
     The system control blocks are UCB, DCE, SSSCB,
 DPCT and RDFEATS.
 
     If you specify the parameter NOIO, the display
 will show only the storage resident information in the MVS
 control blocks; the command will not issue any I/O to the
 selected devices.
     The device information buffers are RDC, RCD,
 and SNSS."
 
 If I were to guess, I'd say that UCB, DCE, SSSCB, DPCT and
 RDFEATS are all candidates to be "updated" (validated) from
 RDC, RCD (don't you just love when you see TLCs in the same
 paragraph which are anagrams of each other?) and SNSS.
 Unless NOIO is specified.
 
 However, I assume the purpose of the question is not to rely
 on guesses. From reading the brief documentation, I'd for
 sure say VALIDATE may update something.
 
 --
 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

Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

Lizette,

There are no error messages or issues.  I posed the question because I came 
across the command (which is run in batch job, using an inhouse program) and I 
wasn't sure what the VALIDATE did when the command was issued.


On Wed, 7/12/16, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 7 December, 2016, 1:50 PM
 
 So, what is it you are
 working on?
 
  What error
 messages?
  What IO issue?
 
 Any HCD or IO Gen issues?
  Device not coming
 online or responding?
 
 Perhaps if there were more detail on why you
 wish to use validate on the DS DQ command, more guidance
 from the list could be given.
 
 Remember:  The more details the better the
 advice.   ;-D
 
 
 Lizette
 
 
 > -Original Message-
 > From: IBM Mainframe Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Wednesday, December 07, 2016 8:59
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: EXPLANATION ABOUT VALIDATE WHEN
 DOING A DS QD
 > 
 >
 G'Day,
 > 
 > Could
 someone clear up what the command DS QD,413Z,VALIDATE
 actually do?  The
 > doc says the
 following:
 > 
 >
 VALIDATE : Uses status information acquired directly from a
 device to correct
 > inconsistent extended
 function status information maintained in host processor
 > storage. VALIDATE has no effect if the
 unit address has no physical device
 >
 attached
 > 
 > I am not
 sure what "to correct inconsistent extended
 function.." does.  Is it
 > safe to
 use? Could you please help me understand IBM's
 explanation because it
 > is not clear.
 > 
 > Thanks.
 > 
 
 --
 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

EXPLANATION ABOUT VALIDATE WHEN DOING A DS QD

[John Dawes]

G'Day,

Could someone clear up what the command DS QD,413Z,VALIDATE actually do?  The 
doc says the following:

VALIDATE : Uses status information acquired directly from a device to correct 
inconsistent extended function status information maintained in host processor 
storage. VALIDATE has no effect if the unit address has no physical device 
attached

I am not sure what "to correct inconsistent extended function.." does.  Is it 
safe to use? Could you please help me understand IBM's explanation because it 
is not clear.

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF RECORD TYPE : HELP

[John Dawes]

Daniel,

I would like to try out your suggestion.  Would you have an example of the 
FDRABR step?  Also, would it support SMF as an input file?


On Thu, 3/11/16, Blake, Daniel J [CTR] 
<00f1be92566d-dmarc-requ...@listserv.ua.edu> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 9:20 AM
 
 OK, add an SDSF step
 before your FDR dump step, then one after your FDR dump
 step.  Rerun the job.
 
 //COMMAND1  EXEC PGM=ISFAFD
 //ISFOUT              DD  SYSOUT=*
 //ISFIN   DD  *
  
 /D ALLOC,,devaddr,1
 /*
 //*
 //FDRABR step here
 //FDR 
 //*    
 //COMMAND2  EXEC PGM=ISFAFD
 //ISFOUT              DD  SYSOUT=*
 //ISFIN   DD  *
  
 /D ALLOC,,devaddr,1
 /*
 
 
 
 ;-D an 
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: Thursday,
 November 03, 2016 8:23 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: SMF RECORD TYPE : HELP
 
 Yes, I tried that.  However,
 when I issued the command it was too late (3 minutes after
 the job abend).  This is why I thought by  reading SMF
 records would have some info on the volume.
 
 
 
 On Thu, 3/11/16, Blake, Daniel J [CTR] 
<00f1be92566d-dmarc-requ...@listserv.ua.edu>
 wrote:
 
  Subject: Re: SMF
 RECORD TYPE : HELP
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Thursday, 3 November, 2016, 7:56
 AM
  
  Have you tried the
 alloc
  command from the console or SDSF?
  
  D U,,ALLOC,devaddr,1
  
  Thank You
 
 
  
  ;-D an
 
 
  
   
 
 -Original Message-
  From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On Behalf Of John Dawes
  Sent: Thursday,
  November 03, 2016 7:53 AM
  To:
 IBM-MAIN@LISTSERV.UA.EDU
  Subject: SMF RECORD TYPE : HELP
  
  G'Day,
 
 
  Could someone suggest how I could obtain 
 information about a certain DASD volume?  I am trying to 
 trouble shoot a problem of a job failure when attempting
 to  copy a volume using the following parms.
  
  COPY INDYNAM(SYS012)
 OUTDYNAM(BCD012)
  CANCELERROR      - 
   
     PURGE ALLEXCP
 ALLDATA(*) OPT(4) ADMIN FCNOCOPY
  -    
  
  I get the following
  message:
  
 
 ADR306E
  (043)-SBRTN(01), UNABLE TO COPY THE
 VOLUME BECAUSE OUTPUT  VOLUME BCD012  IS IN USE. TASK IS
 TERMINATED
  
  I am trying to
 find out what
  resource was using the volume
 at that time.  I thought that  SMF would be a solution
 however I don't see a SMF record  type for DASD.
  
  Any
 
 suggestions would be very welcome.
  
  Thanks.
  
 
 --
  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

Re: SMF RECORD TYPE : HELP

[John Dawes]

That was the first thing I tried.  However it was too late because I issued 3 
minutes later after the job abended.  The device showed that no resource had 
aan enque on it..

On Thu, 3/11/16, Ronald Hawkins <ronjhawk...@sbcglobal.net> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 7:51 PM
 
 John,
 Have you tried D U ... ALLOC COMMAND?
 Ron
 
 Sent from
 Yahoo Mail on Android 
  
  
 On Thu, Nov 3, 2016 at 4:52, John 
Dawes<00ff0e22811f-dmarc-requ...@listserv.ua.edu>
 wrote:   G'Day,
 
 Could someone suggest how I could obtain
 information about a certain DASD volume?  I am trying to
 trouble shoot a problem of a job failure when attempting to
 copy a volume using the following parms.
 
 COPY INDYNAM(SYS012) OUTDYNAM(BCD012)
 CANCELERROR      - 
     PURGE ALLEXCP
 ALLDATA(*) OPT(4) ADMIN FCNOCOPY -    
 
 I get the following message:
 
 ADR306E (043)-SBRTN(01),
 UNABLE TO COPY THE VOLUME BECAUSE OUTPUT VOLUME BCD012  IS
 IN USE. TASK IS TERMINATED
 
 I am trying to find out what resource was using
 the volume at that time.  I thought that SMF would be a
 solution however I don't see a SMF record type for
 DASD.
 
 Any suggestions would
 be very welcome.
 
 Thanks.
 
 --
 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

Re: SMF RECORD TYPE : HELP

[John Dawes]

We ar e running RELEASE z/OS 02.01.00.  The target volume (DASD) is for 
Flashcopy only.  We have had this type of problem intermittently for other 
volumes as well.

On Thu, 3/11/16, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 9:06 AM
 
 What version of z/OS are
 you running?
 
 
 So, I might try the following
 
 If you have an automation
 tool, this works easier
 
 Start the displays when the JOB enters the
 system
 
 1)  D
 GRS,DEV=         This can be imbedded in
 the JCL with the // command JCL Card or issued as an MVS
 Command
 
 2)  D
 U,,ALLOC,,1      This can be imbedded in the JCL with
 the // command JCL Card or issued as an MVS Command
 
 3)  Add
 PARM='UTILMSG=YES'
 
 4)  Review the volume to see what is on it. 
 Any catalogs, DB2 Tables, zFS or HFS files that might be
 enqueued?
 
 5)  Is BCD012 a
 tape or disk?  Is it purely a flashcopy volume? Or do you
 allow it to be used by other activities?
 
 6)  Is this first time this job has had an
 issue or is this a reoccurring event?
 
 7)  As others have stated, RMF Panels could
 help
 
 
 Lizette
 
 
 
 
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Thursday, November 03, 2016 4:53
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: SMF RECORD TYPE : HELP
 > 
 > G'Day,
 > 
 > Could someone
 suggest how I could obtain information about a certain
 DASD
 > volume?  I am trying to trouble
 shoot a problem of a job failure when
 >
 attempting to copy a volume using the following parms.
 > 
 > COPY INDYNAM(SYS012)
 OUTDYNAM(BCD012) CANCELERROR      -
 >      PURGE ALLEXCP ALLDATA(*) OPT(4)
 ADMIN FCNOCOPY -
 > 
 >
 I get the following message:
 > 
 > ADR306E (043)-SBRTN(01), UNABLE TO COPY
 THE VOLUME BECAUSE OUTPUT VOLUME
 >
 BCD012  IS IN USE. TASK IS TERMINATED
 >
 
 > I am trying to find out what resource
 was using the volume at that time.  I
 >
 thought that SMF would be a solution however I don't see
 a SMF record type for
 > DASD.
 > 
 > Any suggestions
 would be very welcome.
 > 
 > Thanks.
 
 --
 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

Re: SMF RECORD TYPE : HELP

[John Dawes]

Lizette,

I checked with our Capacity Performance group and they informed me that the 
data is retained for a day.  Thanks for the info.

On Thu, 3/11/16, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 9:15 AM
 
 If they set up the RMF
 ISPF application in your environment - Most shops use a
 REXX/CLIST to access it.
 
 In
 my shop we created RMFIII as the REXX/CLIST.  However, you
 shop might be different.  You need to have datasets that
 use SERBxxx allocated to your TSO Session.  See if your
 sysprog can help.
 
 This link
 shows the RMF libraries that are allocated (dynamically or
 hard coded in the TSO Logon Proc) to your TSO Session to use
 the RMF Panels
 
 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.erbb200/exec.htm
 
 Unless the libraries are
 allocated, you cannot use the RMF Panels.
 
 The second issue is how large
 are the RMF monitor VSAM Files?  If they are too small,
 then the option will not be able to retain sufficient data
 to do past analysis.
 
 If you
 have SAS/MXG or SAS/MICS, then you can run the dasd reports
 for RMF.
 
 Lizette
 
 
 
 
 
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Thursday, November 03, 2016 5:36
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: SMF RECORD TYPE : HELP
 > 
 > Thanks for the
 suggestion.  I am not familiar on how to use.  I sure
 would
 > like to try.
 >
 
 > Is it interactive via ISPF?
 > 
 >
 
 > On Thu, 3/11/16, Campbell Jay <james.l.campb...@irs.gov>
 wrote:
 > 
 >  Subject:
 Re: SMF RECORD TYPE : HELP
 >  To: IBM-MAIN@LISTSERV.UA.EDU
 >  Received: Thursday, 3 November, 2016,
 8:32 AM
 > 
 >  How
 about  RMF
 >  panels   3 - 2
 - 5 ?
 >  Put in
 > 
 jobname - then set time for when job was running
 > 
 >  Jay Campbell
 >  MSSD – IZSSB – IOSSS
 > 
 >  -Original
 Message-----
 >  From: IBM Mainframe
 Discussion List [mailto:IBM-MAIN@listserv.ua.edu] 
 On
 > Behalf Of John Dawes
 >  Sent: Thursday,
 > 
 November 03, 2016 8:23 AM
 >  To: IBM-MAIN@listserv.ua.edu
 >  Subject: Re: SMF RECORD TYPE : HELP
 > 
 >  Yes, I tried
 that.  However,
 >  when I issued the
 command it was too late (3 minutes after  the job
 > abend).  This is why I thought by 
 reading SMF  records would have some info
 > on the volume.
 > 
 > 
 > 
 
 >  On Thu, 3/11/16, Blake, Daniel J [CTR]
 <00f1be92566d-dmarc-
 > requ...@listserv.ua.edu>
 >  wrote:
 > 
 >   Subject: Re: SMF
 >  RECORD TYPE : HELP
 >   To: IBM-MAIN@LISTSERV.UA.EDU
 >   Received: Thursday, 3
 November, 2016, 7:56  AM
 > 
 >   Have you tried the
 >  alloc
 >   command from the console or
 SDSF?
 > 
 >   D U,,ALLOC,devaddr,1
 > 
 >   Thank
 You
 > 
 > 
 > 
 >   ;-D
 an
 > 
 > 
 > 
 > 
 > 
 >  -Original
 Message-
 >   From: IBM
 >  Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On Behalf Of
 > John Dawes
 >   Sent: Thursday,
 >   November 03, 2016 7:53 AM
 >   To:
 >  IBM-MAIN@LISTSERV.UA.EDU
 >   Subject: SMF RECORD TYPE :
 HELP
 > 
 >   G'Day,
 > 
 > 
 >   Could someone suggest how I
 could obtain  information about a certain DASD
 > volume?  I am trying to  trouble shoot a
 problem of a job failure when
 >
 attempting  to  copy a volume using the following
 parms.
 > 
 >   COPY INDYNAM(SYS012)
 >  OUTDYNAM(BCD012)
 >   CANCELERROR      -
 > 
 >      PURGE
 ALLEXCP
 >  ALLDATA(*) OPT(4) ADMIN
 FCNOCOPY
 >   -
 > 
 >   I get
 the following
 >   message:
 > 
 > 
 >  ADR306E
 >   (043)-SBRTN(01), UNABLE TO
 COPY THE
 >  VOLUME BECAUSE OUTPUT 
 VOLUME BCD012  IS IN USE. TASK IS  TERMINATED
 > 
 >   I am
 trying to
 >  find out what
 >   resource was using the
 volume
 >  at that time.  I thought
 that  SMF would be a solution  however I don't see
 a
 > SMF record  type for DASD.
 > 
 >   Any
 > 
 >  suggestions would
 be very welcome.
 > 
 >   Thanks.
 >
 
 
 --
 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

Re: SMF RECORD TYPE : HELP

[John Dawes]

 I was able to access the panel however the job is no longer in the spool 
because it has been sent to $AVRS.


On Thu, 3/11/16, Campbell Jay <james.l.campb...@irs.gov> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 8:32 AM
 
 How about  RMF 
 panels   3 - 2 - 5 ?
 Put in
 jobname - then set time for when job was running
 
 Jay Campbell
 MSSD – IZSSB – IOSSS
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu]
 On Behalf Of John Dawes
 Sent: Thursday,
 November 03, 2016 8:23 AM
 To: IBM-MAIN@listserv.ua.edu
 Subject: Re: SMF RECORD TYPE : HELP
 
 Yes, I tried that.  However,
 when I issued the command it was too late (3 minutes after
 the job abend).  This is why I thought by  reading SMF
 records would have some info on the volume.
 
 
 
 On Thu, 3/11/16, Blake, Daniel J [CTR] 
<00f1be92566d-dmarc-requ...@listserv.ua.edu>
 wrote:
 
  Subject: Re: SMF
 RECORD TYPE : HELP
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Thursday, 3 November, 2016, 7:56
 AM
  
  Have you tried the
 alloc
  command from the console or SDSF?
  
  D U,,ALLOC,devaddr,1
  
  Thank You
 
 
  
  ;-D an
 
 
  
   
 
 -Original Message-
  From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On Behalf Of John Dawes
  Sent: Thursday,
  November 03, 2016 7:53 AM
  To:
 IBM-MAIN@LISTSERV.UA.EDU
  Subject: SMF RECORD TYPE : HELP
  
  G'Day,
 
 
  Could someone suggest how I could obtain 
 information about a certain DASD volume?  I am trying to 
 trouble shoot a problem of a job failure when attempting
 to  copy a volume using the following parms.
  
  COPY INDYNAM(SYS012)
 OUTDYNAM(BCD012)
  CANCELERROR      - 
   
     PURGE ALLEXCP
 ALLDATA(*) OPT(4) ADMIN FCNOCOPY
  -    
  
  I get the following
  message:
  
 
 ADR306E
  (043)-SBRTN(01), UNABLE TO COPY THE
 VOLUME BECAUSE OUTPUT  VOLUME BCD012  IS IN USE. TASK IS
 TERMINATED
  
  I am trying to
 find out what
  resource was using the volume
 at that time.  I thought that  SMF would be a solution
 however I don't see a SMF record  type for DASD.
  
  Any
 
 suggestions would be very welcome.
  
  Thanks.
  
 
 --
  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

Re: SMF RECORD TYPE : HELP

[John Dawes]

Thanks for the suggestion.  I am not familiar on how to use.  I sure would like 
to try.

Is it interactive via ISPF?


On Thu, 3/11/16, Campbell Jay <james.l.campb...@irs.gov> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 8:32 AM
 
 How about  RMF 
 panels   3 - 2 - 5 ?
 Put in
 jobname - then set time for when job was running
 
 Jay Campbell
 MSSD – IZSSB – IOSSS
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu]
 On Behalf Of John Dawes
 Sent: Thursday,
 November 03, 2016 8:23 AM
 To: IBM-MAIN@listserv.ua.edu
 Subject: Re: SMF RECORD TYPE : HELP
 
 Yes, I tried that.  However,
 when I issued the command it was too late (3 minutes after
 the job abend).  This is why I thought by  reading SMF
 records would have some info on the volume.
 
 
 
 On Thu, 3/11/16, Blake, Daniel J [CTR] 
<00f1be92566d-dmarc-requ...@listserv.ua.edu>
 wrote:
 
  Subject: Re: SMF
 RECORD TYPE : HELP
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Thursday, 3 November, 2016, 7:56
 AM
  
  Have you tried the
 alloc
  command from the console or SDSF?
  
  D U,,ALLOC,devaddr,1
  
  Thank You
 
 
  
  ;-D an
 
 
  
   
 
 -Original Message-
  From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On Behalf Of John Dawes
  Sent: Thursday,
  November 03, 2016 7:53 AM
  To:
 IBM-MAIN@LISTSERV.UA.EDU
  Subject: SMF RECORD TYPE : HELP
  
  G'Day,
 
 
  Could someone suggest how I could obtain 
 information about a certain DASD volume?  I am trying to 
 trouble shoot a problem of a job failure when attempting
 to  copy a volume using the following parms.
  
  COPY INDYNAM(SYS012)
 OUTDYNAM(BCD012)
  CANCELERROR      - 
   
     PURGE ALLEXCP
 ALLDATA(*) OPT(4) ADMIN FCNOCOPY
  -    
  
  I get the following
  message:
  
 
 ADR306E
  (043)-SBRTN(01), UNABLE TO COPY THE
 VOLUME BECAUSE OUTPUT  VOLUME BCD012  IS IN USE. TASK IS
 TERMINATED
  
  I am trying to
 find out what
  resource was using the volume
 at that time.  I thought that  SMF would be a solution
 however I don't see a SMF record  type for DASD.
  
  Any
 
 suggestions would be very welcome.
  
  Thanks.
  
 
 --
  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

Re: SMF RECORD TYPE : HELP

[John Dawes]

Yes, I tried that.  However, when I issued the command it was too late (3 
minutes after the job abend).  This is why I thought by  reading SMF records 
would have some info on the volume.
 

On Thu, 3/11/16, Blake, Daniel J [CTR] 
<00f1be92566d-dmarc-requ...@listserv.ua.edu> wrote:

 Subject: Re: SMF RECORD TYPE : HELP
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 3 November, 2016, 7:56 AM
 
 Have you tried the alloc
 command from the console or SDSF?
 
 D U,,ALLOC,devaddr,1
 
 Thank You
 
 
 ;-D an
 
 
  
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: Thursday,
 November 03, 2016 7:53 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: SMF RECORD TYPE : HELP
 
 G'Day,
 
 Could someone suggest how I could obtain
 information about a certain DASD volume?  I am trying to
 trouble shoot a problem of a job failure when attempting to
 copy a volume using the following parms.
 
 COPY INDYNAM(SYS012) OUTDYNAM(BCD012)
 CANCELERROR      - 
  
    PURGE ALLEXCP ALLDATA(*) OPT(4) ADMIN FCNOCOPY
 -    
 
 I get the following
 message:
 
 ADR306E
 (043)-SBRTN(01), UNABLE TO COPY THE VOLUME BECAUSE OUTPUT
 VOLUME BCD012  IS IN USE. TASK IS TERMINATED
 
 I am trying to find out what
 resource was using the volume at that time.  I thought that
 SMF would be a solution however I don't see a SMF record
 type for DASD.
 
 Any
 suggestions would be very welcome.
 
 Thanks.
 
 --
 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

SMF RECORD TYPE : HELP

[John Dawes]

G'Day,

Could someone suggest how I could obtain information about a certain DASD 
volume?  I am trying to trouble shoot a problem of a job failure when 
attempting to copy a volume using the following parms.

COPY INDYNAM(SYS012) OUTDYNAM(BCD012) CANCELERROR  - 
 PURGE ALLEXCP ALLDATA(*) OPT(4) ADMIN FCNOCOPY -

I get the following message:

ADR306E (043)-SBRTN(01), UNABLE TO COPY THE VOLUME BECAUSE OUTPUT VOLUME BCD012 
 IS IN USE. TASK IS TERMINATED

I am trying to find out what resource was using the volume at that time.  I 
thought that SMF would be a solution however I don't see a SMF record type for 
DASD.

Any suggestions would be very welcome.

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

QUESTION ABOUT REDUCING EXTENTS : USING DFDSS

[John Dawes]

G'Day,

I ran a job to reduce the extents of a PDS however for some reason it tried to 
process other dataset on that volume.  I am not sure why.  Perhaps I missed 
something in the doc?

Below are the jcl and the job output.  Thanks in advance.
/*   
//CONSOLD EXEC PGM=ADRDSSU,REGION=4M,TIME=1440,PARM='UTILMSG=YES'
//DASD1DD UNIT=3390,VOL=SER=DISS06,DISP=SHR  
//SYSPRINT DD  SYSOUT=*  
//SYSMAP   DD SYSOUT=*   
//SYSINDD  * 
  CONS DATASET(INCLUDE(SYS3.CNTL.DEV)) - 
 PIDD(DASD1) 
/*   
Output:
CONS DATASET(INCLUDE(SYS3.CNTL.DEV))
   PIDD(DASD1)
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'CONS '
ADR109I (R/I)-RI01 (01), 2016.243 07:50:39 INITIAL SCAN OF USER CONTROL STATEMEN
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I (001)-STEND(01), 2016.243 07:50:39 EXECUTION BEGINS 
ADR806I (001)-DFRGD(01), RELOCATED EXTENTS WILL BE COPIED USING A FAST 
REPLICATION FUNCTION
ADR211I (001)-DFRGD(01), DATA SET SYS3.CNTL.SHR IN USE AND WAS NOT MOVED  
ADR455W (001)-DFRGD(01), THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED
  SYS3.CNTL.SHR   
  RADN.RTRIV1.TABLES.DATA  
  DB2.DDIR.D 
  HEST.DDIR.D 
  HEST.DDIR.I 
  DB2.DDIR.I 
  PREM.DDIR.D 
  PREM.DDIR.I 
  SYS3.VSAM.VRRDS.DATA   
ADR006I (001)-STEND(02), 2016.243 07:50:44 EXECUTION ENDS   
ADR013I (001)-CLTSK(01), 2016.243 07:50:44 TASK COMPLETED WITH RETURN CODE 0004 
ADR012I (SCH)-DSSU (01), 2016.243 07:50:44 DFSMSDSS PROCESSING COMPLETE. 
HIGHEST RETURN CODE IS 0004 FROM:
 TASK001
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: VIRTUAL TAPE PECULIARITY

[John Dawes]

Kees,
 I think you are right.  I checked the tape status in the VTS and it shows 
"deleted".  When the FATAR was run it showed that the tape was empty

  Thanks.

On Tue, 26/4/16, Vernooij, CP (ITOPT1) - KLM <kees.verno...@klm.com> wrote:

 Subject: Re: VIRTUAL TAPE PECULIARITY
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, 26 April, 2016, 2:25 AM
 
 John,
 
 You said the tape went to scratch, but it was P in SMS. Has
 it been returned from scratch to private in SMS?
 If it has been scratch, check out the scratch category it
 was in then (in DEVSUPxx) and check in the VTS GUI if this
 category was a fast ready category and if that category has
 an Expire time specified together with Expire Hold. 
 
 This means, that after your tape management system made the
 tape scratch, the VTS has expired the data from it and when
 you made it Private again in SMS in order to mount it again,
 the data is not available anymore and you will be presented
 an empty tape.
 
 Kees.
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: 25 April, 2016 18:18
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: VIRTUAL TAPE PECULIARITY
 
 Kees,
 
 We are using IBM TS770.  In order to mount the tape I
 think the tape was still in SMS with a status of P.  I
 am not sure if the tape was in fast-ready.  Sorry I
 couldn't be more helpful.  This problem happened last
 Tuesday. 
 
 --
 For IBM-MAIN subscribe / signoff / archive access
 instructions,
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN
 
 For information, services and offers, please visit our web
 site: http://www.klm.com. This e-mail and any attachment may
 contain confidential and privileged material intended for
 the addressee only. If you are not the addressee, you are
 notified that no part of the e-mail or any attachment may be
 disclosed, copied or distributed, and that any other action
 related to this e-mail or attachment is strictly prohibited,
 and may be unlawful. If you have received this e-mail by
 error, please notify the sender immediately by return
 e-mail, and delete this message. 
 
 Koninklijke Luchtvaart Maatschappij NV (KLM), its
 subsidiaries and/or its employees shall not be liable for
 the incorrect or incomplete transmission of this e-mail or
 any attachments, nor responsible for any delay in receipt. 
 Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM
 Royal Dutch Airlines) is registered in Amstelveen, The
 Netherlands, with registered number 33014286
 
             
 
 
 --
 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

Re: VIRTUAL TAPE PECULIARITY

[John Dawes]

Is it safe to say that once a tape goes scratch all the data is deleted?

Also, is the same volume serial number - in this case A15886 - is kept and 
reused?

Please bear with me because I am not very familiar with virtual tape processing.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: VIRTUAL TAPE PECULIARITY

[John Dawes]

Kees,

We are using IBM TS770.  In order to mount the tape I think the tape was still 
in SMS with a status of P.  I am not sure if the tape was in fast-ready.  Sorry 
I couldn't be more helpful.  This problem happened last Tuesday.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

VIRTUAL TAPE PECULIARITY

[John Dawes]

G'Day,

I am trying to read a virtual tape that went into scratch status.  The tape 
has not been reused since it went scratch.  The job abends with a
IEC145I 413-08.  I had the tape analyzed and it shows the following:

UNIT  DEVICE   SERIAL  MFR CARTRIDGE 
667D VIRTUAL  A15886  IBM  800 MB   
FATAR DETAIL REPORT  
LOCK  LNGTH/  MESSAGE/1...5...10...15...20...25...30...35...4
UMBER DISPL  BLOCK TYPE (COLUMN GRID IS VALID ONLY FO
 
* * * * * * * START FILE   1H
1 80  INPUT LABEL VOL1A15886 
  ***VOLUME LABEL***VOLSER=A15886 OWNER= 
2 80  INPUT LABEL HDR1000
  ***HEADER LABEL***   DSNAME=0 SERIAL=00
   CRTDT=00 EXPDT=00 SECURITY
* * * * * * * END OF FILE  1H -- FILE CONTAINED 2 BLOCKS 
* * * * * * * START FILE   1 
TS096 **END OF DATA MARK ENCOUNTERED.  BLOCK ID=0003   

It seems that the tape is empty.  My question is if the tape goes scratch the 
data cannot be recovered even though it has not been overwritten?

I have no problems with physical tapes which have gone scratch and not reused.  

I would appreciate your thoughts.

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: QUESTION ABOUT FLASHCOPY

[John Dawes]

Thanks for the info.  Thanks again.

On Wed, 6/4/16, Gonzalo Cengotita <gonzaloce...@gmail.com> wrote:

 Subject: Re: QUESTION ABOUT FLASHCOPY
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 6 April, 2016, 9:35 AM
 
 In the manual "z/OS
 V1R13.0 DFSMSdss Storage Administration" you can see
 (Explanation of COPY Command Keywords, page
 340)
 
 "FULL specifies
 that an entire DASD volume is to be copied. This is the
 default.
 Unallocated tracks are
 not copied."
 
 I think
 this answer your question
 
 Regards,
 
 
 *Gonzalo Cengotita*
 
 2016-04-06 15:20 GMT+02:00 John Dawes <
 00ff0e22811f-dmarc-requ...@listserv.ua.edu>:
 
 > G'Day
 >
 > I have a question
 about FLASHCOPY specifically COPY FULL command.
 >
 > Below are 2 examples
 that we use.  One has the FULL command and the other
 > does not.  Omitting the parm FULL, would
 it be because it is a default?  I
 >
 looked at SC26-4388-05 but I didn't find what I was
 looking for.
 >
 > COPY
 FULL INDYNAM(ZWA601) OUTDYNAM(FBAD00) ALLE ALLD(*) -
 > FASTREPLICATION(REQUIRED) FCINCREMENTAL
 DUMPCONDITIONING ADMIN PURGE
 >
 > COPY INDYNAM(JES901) OUTDYNAM(QF6670)
 CANCELERROR
 >      PURGE ALLEXCP
 ALLDATA(*) OPT(4) ADMIN FCNOCOPY -
 >   
   DUMPCOND FR(REQ) DEBUG(FRMSG(DETAILED))
 >
 >
 --
 > 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

QUESTION ABOUT FLASHCOPY

[John Dawes]

G'Day 

I have a question about FLASHCOPY specifically COPY FULL command.

Below are 2 examples that we use.  One has the FULL command and the other does 
not.  Omitting the parm FULL, would it be because it is a default?  I looked at 
SC26-4388-05 but I didn't find what I was looking for.

COPY FULL INDYNAM(ZWA601) OUTDYNAM(FBAD00) ALLE ALLD(*) -   
FASTREPLICATION(REQUIRED) FCINCREMENTAL DUMPCONDITIONING ADMIN PURGE

COPY INDYNAM(JES901) OUTDYNAM(QF6670) CANCELERROR 
 PURGE ALLEXCP ALLDATA(*) OPT(4) ADMIN FCNOCOPY - 
 DUMPCOND FR(REQ) DEBUG(FRMSG(DETAILED))  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SAVING OUTPUT WHEN IN ISPF 3.4

[John Dawes]

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SAVING OUTPUT WHEN IN ISPF 3.4

[John Dawes]

G'Day,

Can someone suggest how I can go about printing all of the screen output when 
in ISPF 3.4

For example there are about 3,000 dsns.  Here is what I do

Go into ISPF 3.4
Enter the HLQ of the dsn e.g. SYS2.SMF.MONTH
Next I enter the command PRINTL
HIT PF8
Repeat PRINTL
HIT PF8
etc etc et
Once I have captured all of the screen output I enter the comand LIST KEEP
I hit F1 to get the name of the dsn which is usually USERID.SPFx.LIST.

Is there a way I can bypass having to the PRINTL & PF8 commands so as to 
capture all of the screen output?  Is there a PRINT command that would do it?

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SAVING OUTPUT WHEN IN ISPF 3.4

[John Dawes]

Lizette,

I tried the command LIST KEEP and it worked.  Is this what you were refering to?

On Fri, 29/1/16, John Dawes <jhn_da...@yahoo.com.au> wrote:

 Subject: Re: SAVING OUTPUT WHEN IN ISPF 3.4
 To: "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU>
 Received: Friday, 29 January, 2016, 10:58 AM
 
 Lizette
 
 How can I start a new ISPF List dataset?
 
 
 On Fri, 29/1/16, Lizette Koehler <stars...@mindspring.com>
 wrote:
 
  Subject: Re: SAVING OUTPUT WHEN IN ISPF 3.4
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Friday, 29 January, 2016, 9:43 AM
  
  You can use SAVE dsn   
  and it will create HLQ.dsn.DATASETS
  Or you
  can issue SAVE and then LIST - Then you can save it and
  start a new ISPF List dataset.
  
  Lizette
  
  
  >
  -Original Message-
  > From: IBM
  Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
  On
  > Behalf Of John Dawes
  > Sent: Friday, January 29, 2016 7:31 AM
  > To: IBM-MAIN@LISTSERV.UA.EDU
  > Subject: SAVING OUTPUT WHEN IN ISPF 3.4
  > 
  > G'Day,
  > 
  > Can someone suggest
  how I can go about printing all of the screen output when
  > in ISPF 3.4
  > 
  > For example there are about 3,000 dsns. 
  Here is what I do
  > 
  >
  Go into ISPF 3.4
  > Enter the HLQ of the
  dsn e.g. SYS2.SMF.MONTH Next I enter the command PRINTL
  > HIT PF8 Repeat PRINTL HIT PF8 etc etc et
  Once I have captured all of the
  > screen
  output I enter the comand LIST KEEP I hit F1 to get the
 name
  of the dsn
  > which is usually
  USERID.SPFx.LIST.
  > 
  >
  Is there a way I can bypass having to the PRINTL & PF8
  commands so as to
  > capture all of the
  screen output?  Is there a PRINT command that would do
  it?
  > 
  > Thanks.
  
  --
  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

Re: SAVING OUTPUT WHEN IN ISPF 3.4

[John Dawes]

Sri,

Thanks so much.  It worked.  A massive thank youl

On Fri, 29/1/16, Sri h Kolusu <skol...@us.ibm.com> wrote:

 Subject: Re: SAVING OUTPUT WHEN IN ISPF 3.4
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Friday, 29 January, 2016, 11:10 AM
 
 John,
 
 1. Go into ISPF 3.4
 2.
 SYS2.SMF.MON*
 3. Issue the command SAVE
  and press enter
 4. Press PF1 and notice the name of the dataset
 the list is saved to it 
 should be
 USERID.8charactername.DATASETS
 
 If you want a new list go to back step 1 and
 change the dsn listing mask 
 in step 2 and
 give a new name in step 3
 
 Thanks,
 Kolusu
 
 IBM Mainframe Discussion List
 <IBM-MAIN@LISTSERV.UA.EDU>
 wrote on 
 01/29/2016 09:04:00 AM:
 
 > From: John Dawes <jhn_da...@yahoo.com.au>
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Date: 01/29/2016 09:04 AM
 > Subject: Re: SAVING OUTPUT WHEN IN ISPF
 3.4
 > Sent by: IBM Mainframe Discussion
 List <IBM-MAIN@LISTSERV.UA.EDU>
 > 
 > Lizette,
 > 
 > I tried the command
 LIST KEEP and it worked.  Is this what you were 
 > refering to?
 >
 ----
 > On Fri, 29/1/16, John Dawes <jhn_da...@yahoo.com.au>
 wrote:
 > 
 >  Subject:
 Re: SAVING OUTPUT WHEN IN ISPF 3.4
 > 
 To: "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU>
 >  Received: Friday, 29 January, 2016,
 10:58 AM
 > 
 > 
 Lizette
 > 
 >  How can
 I start a new ISPF List dataset?
 > 
 > 
 
 >  On Fri, 29/1/16, Lizette Koehler <stars...@mindspring.com>
 >  wrote:
 > 
 >   Subject: Re: SAVING OUTPUT
 WHEN IN ISPF 3.4
 >   To: IBM-MAIN@LISTSERV.UA.EDU
 >   Received: Friday, 29 January,
 2016, 9:43 AM
 > 
 >   You can use SAVE
 dsn   
 >   and it
 will create HLQ.dsn.DATASETS
 >   Or you
 >   can issue SAVE and then LIST
 - Then you can save it and
 >   start a new ISPF List
 dataset.
 > 
 >   Lizette
 >
 
 > 
 >   >
 >   -Original Message-
 >   > From: IBM
 >   Mainframe Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 >   On
 >   > Behalf Of John Dawes
 >   > Sent: Friday, January
 29, 2016 7:31 AM
 >   > To:
 IBM-MAIN@LISTSERV.UA.EDU
 >   > Subject: SAVING OUTPUT
 WHEN IN ISPF 3.4
 >   > 
 >   > G'Day,
 >   > 
 >   > Can someone suggest
 >   how I can go about printing
 all of the screen output when
 >   > in ISPF 3.4
 >   > 
 >   > For example there are
 about 3,000 dsns. 
 >   Here is
 what I do
 >   > 
 >   >
 >   Go into ISPF 3.4
 >   > Enter the HLQ of the
 >   dsn e.g. SYS2.SMF.MONTH Next
 I enter the command PRINTL
 >   > HIT PF8 Repeat PRINTL
 HIT PF8 etc etc et
 >   Once I
 have captured all of the
 >   > screen
 >   output I enter the comand
 LIST KEEP I hit F1 to get the
 >  name
 >   of the dsn
 >   > which is usually
 >   USERID.SPFx.LIST.
 >   > 
 >   >
 >   Is there a way I can bypass
 having to the PRINTL & PF8
 >   commands so as to
 >   > capture all of the
 >   screen output?  Is there a
 PRINT command that would do
 >   it?
 >   > 
 >   > Thanks.
 > 
 >   --
 >   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

Re: SAVING OUTPUT WHEN IN ISPF 3.4

[John Dawes]

Lizette

How can I start a new ISPF List dataset?


On Fri, 29/1/16, Lizette Koehler <stars...@mindspring.com> wrote:

 Subject: Re: SAVING OUTPUT WHEN IN ISPF 3.4
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Friday, 29 January, 2016, 9:43 AM
 
 You can use SAVE dsn   
 and it will create HLQ.dsn.DATASETS
 Or you
 can issue SAVE and then LIST - Then you can save it and
 start a new ISPF List dataset.
 
 Lizette
 
 
 >
 -Original Message-
 > From: IBM
 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of John Dawes
 > Sent: Friday, January 29, 2016 7:31 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: SAVING OUTPUT WHEN IN ISPF 3.4
 > 
 > G'Day,
 > 
 > Can someone suggest
 how I can go about printing all of the screen output when
 > in ISPF 3.4
 > 
 > For example there are about 3,000 dsns. 
 Here is what I do
 > 
 >
 Go into ISPF 3.4
 > Enter the HLQ of the
 dsn e.g. SYS2.SMF.MONTH Next I enter the command PRINTL
 > HIT PF8 Repeat PRINTL HIT PF8 etc etc et
 Once I have captured all of the
 > screen
 output I enter the comand LIST KEEP I hit F1 to get the name
 of the dsn
 > which is usually
 USERID.SPFx.LIST.
 > 
 >
 Is there a way I can bypass having to the PRINTL & PF8
 commands so as to
 > capture all of the
 screen output?  Is there a PRINT command that would do
 it?
 > 
 > Thanks.
 
 --
 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

Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

[John Dawes]

I checked.  The SMS rules have been built and the dsns are defined in the 
specific SG.  This is only happening for this particular dsn because of the AFF 
parm:

UNIT=AFF=A3490.

I have never used the AFF parm when writing out to dsns.  I used the AFF parm 
only when reading them in the job.


On Thu, 19/11/15, Bob Dott  wrote:

 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF 
DATA SET
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, 19 November, 2015, 9:12 AM
 
 John, I believe your issue may be
 that the IBM VTS is installed as SMS managed tape. Have you
 added the VTS to SMS, if not you may need to. If you do have
 it defined in SMS, verify the tape datasets are getting
 assigned the correct storage group. If they are falling into
 a storage group for disk, that would drive this error. The
 DFSMS OAM Planning, Installation and Storage Administration
 guide for tape libraries (SC23-6867-01) would be the best
 manual to refer to if you have not set the VTS up in SMS.
 
 --
 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

Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

[John Dawes]

No,not yetstill looking

On Tue, 17/11/15, Vernooij, CP (ITOPT1) - KLM <kees.verno...@klm.com> wrote:

 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF 
DATA SET
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, 17 November, 2015, 5:13 AM
 
 John,
 
 Did you find a solution? 
 Just
 interested.
 
 Kees.
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: 10 November,
 2015 16:19
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: JCL QUESTION :IGD17045I SPACE NOT
 SPECIFIED FOR ALLOCATION OF DATA SET
 
 G'Day 
 
 I
 have a problem with allocating a dsn to tape.  This problem
 started when we transferred from Oracle VSM to IBM VTS. 
 
 
 The error message is as
 follows:
 
 IEF344I MVRXL#JP
 TSO CUMUL OUTPUT01 - ALLOCATION FAILED DUE TO DATA FACILITY
 SYSTEM ERROR
 IGD17045I SPACE NOT SPECIFIED
 FOR ALLOCATION OF DATA SET                   
    
 SYSCICS.CICS.CICSVP.G0005V00   
    
 
 This job has
 been running without any problem when it was allocated under
 VSM however with the switch to VTS the abends have occurred
 due to the AFF parm.
 
 Below
 is the jcl:
 
 //ACUMUL  EXEC
 IKJEFT01,                       
    
 //         
    PARM=('CICSAPP')             
     
 //*                     
                          
 //STEP1  DD
 DISP=(SHR,PASS),DSN=&     
    
 //CICSLIST DD
 DSN=&,DISP=(SHR,DELETE)      
 //SYSTSPRT DD SYSOUT=*               
             
 //SYSPRINT DD SYSOUT=* 
                           
 //SYSTSIN  DD DUMMY                 
              
 //*       
                                    
    
 //A3490    DD 
 UNIT=(3490,,DEFER)                 
 //OUTPUT01 DD DSN=SYSCICS.CICS.CICSVP(+1), 
 //            DISP=(NEW,CATLG,DELETE), 
           
 //           
 DCB=MODDSCB,                        
 //            RECFM=VB,LRECL=32756,   
            
 //         
   UNIT=AFF=A3490,LABEL=EXPDT=99000    
 
 As a temporary workaround I
 have removed the AFF parm (UNIT=3490,LABEL=EXPDT=99000)
 however because of JCL changes that would need to be done
 which the user would like to avoid can something else be
 done?
 
 Please note that NO
 SMS changes have been done since 2013 even though the error
 message points out to a SMS problem.
  
 Thanks. 
 
 
 //*                 
                              
 
 --
 For IBM-MAIN subscribe / signoff / archive
 access instructions,
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN
 
 For information, services and offers, please
 visit our web site: http://www.klm.com. This e-mail and any
 attachment may contain confidential and privileged material
 intended for the addressee only. If you are not the
 addressee, you are notified that no part of the e-mail or
 any attachment may be disclosed, copied or distributed, and
 that any other action related to this e-mail or attachment
 is strictly prohibited, and may be unlawful. If you have
 received this e-mail by error, please notify the sender
 immediately by return e-mail, and delete this message. 
 
 Koninklijke Luchtvaart
 Maatschappij NV (KLM), its subsidiaries and/or its employees
 shall not be liable for the incorrect or incomplete
 transmission of this e-mail or any attachments, nor
 responsible for any delay in receipt. 
 Koninklijke Luchtvaart Maatschappij N.V. (also
 known as KLM Royal Dutch Airlines) is registered in
 Amstelveen, The Netherlands, with registered number
 33014286
 
             
 
 
 --
 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

Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

[John Dawes]

Kees,

This environment also was in a non-SMS environment and the STK silo (SLS8500).  
I will check further into the logic.  The LIBNAME is correct.  I will keep on 
digging.

Thanks.

On Wed, 11/11/15, Vernooij, CP (ITOPT1) - KLM <kees.verno...@klm.com> wrote:

 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF 
DATA SET
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Wednesday, 11 November, 2015, 2:21 AM
 
 John,
 
 At first sight: no, this should do. 
 I had to add the check for
 ='AFF=SMST', but we came from an STK Silo,
 where the volumes are nog SMS managed and in the VSM they
 were SMS managed if I recall correctly.
 
 You can check the logic in the SC routine, to
 see if an SC is assigned before it comes to this WHEN
 clause. Or other SELECT clauses following it. Furthermore,
 is the libname correct, i.e. is the same SC assigned when
 the JCL specifies UNIT=3490?
 
 Kees.
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: 10 November,
 2015 18:03
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT
 SPECIFIED FOR ALLOCATION OF DATA SET
 
 Kees,
 
 I took a
 look at the SC routine and this is what I found:
 
 /* CHECK FOR AFFINITY AND
 STACKED VOLUMES                      
 /**
                                
                                
     WHEN ( ='AFF=SMST' OR
 ='REF=ST' )              
     DO                         
                                
           IF  NE ''
 THEN                              
           SET  =
                             
           ELSE DO               
                               
                   SELECT         
                              
                        WHEN
 ( = 'SHSMF')            
                         SET
  = 'SCSMF'             
                        WHEN
 ( = 'SHVTS')            
                         SET
  = 'SCVTS'       
 
 ..etcetc. etc.
 
 In your example you have a
 FILTLIST built but in this ACS routine there is none.  In
 your view do I need to build the FILTLIST?
 
 
 
 
 On Tue, 10/11/15, Vernooij, CP (ITOPT1) - KLM
 <kees.verno...@klm.com>
 wrote:
 
  Subject: Re: JCL
 QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF
 DATA SET
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Tuesday, 10 November, 2015, 10:27
 AM
  
  Check you ACS
 routines. 
 I have the following filtlist to
 recognize an allocation of tape devices. I remember having
 to add the AFF string for the same purpose when moving from
 Storage Tek (then Sun, then Oracle) to TS7740 libraries:
 
 FILTLIST UNIT_VTS 
    INCLUDE('TS7740',   
                              
 'AFF=SMST', 
                
               '3480',     
                              
 '3490',     
        
                       'TAPE', 
    
                    
           'TAPE2')    
 
 Kees. 
  -Original
 Message-
  From: IBM Mainframe Discussion
 List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
  On Behalf Of John Dawes
  Sent:
 10 November,
  2015 16:19
 
 To: IBM-MAIN@LISTSERV.UA.EDU
  Subject: JCL QUESTION :IGD17045I SPACE NOT
  SPECIFIED FOR ALLOCATION OF DATA SET
  
  G'Day 
 
 
  I
  have a problem with
 allocating a dsn to tape.  This problem
 
 started when we transferred from Oracle VSM to IBM VTS. 
  
  
  The error
 message is as
  follows:
  
  IEF344I MVRXL#JP
  TSO CUMUL
 OUTPUT01 - ALLOCATION FAILED DUE TO DATA FACILITY
  SYSTEM ERROR
  IGD17045I SPACE
 NOT SPECIFIED
  FOR ALLOCATION OF DATA SET 
                  
     
  SYSCICS.CICS.CICSVP.G0005V00   
     
  
  This
 job has
  been running without any problem
 when it was allocated under
  VSM however
 with the switch to VTS the abends have occurred
  due to the AFF parm.
  
  Below
  is the jcl:
  
  //ACUMUL  EXEC
  IKJEFT01,                     
  
     
  //       
  
     PARM=('CICSAPP')     
        
      
  //* 
                    
         
                  
  //STEP1  DD
  DISP=(SHR,PASS),DSN=&     
     
  //CICSLIST DD
  DSN=&,DISP=(SHR,DELETE)   
   
  //SYSTSPRT DD SYSOUT=*           
    
              
 
 //SYSPRINT DD SYSOUT=* 
             
               
  //SYSTSIN  DD
 DUMMY                 
         
      
  //*       
 
                                    
     
  //A3490    DD 
  UNIT=(3490,,DEFER)             
    
  //OUTPUT01 DD
 DSN=SYSCICS.CICS.CICSVP(+1), 
  //       
     DISP=(NEW,CATLG,DELETE), 
       
     
  //           
 
 DCB=MODDSCB,                        
  //            RECFM=VB,LRECL=32756, 
  
             
  // 
        
   
 UNIT=AFF=A3490,LABEL=EXPDT=99000    
  
  As a temporary workaround I
 
 have removed the AFF parm (UNIT=3490,LABEL=EXPDT=99000)
  however because of JCL changes that would need
 to be done
  which the user would like to
 avoid can some

Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

[John Dawes]

Kees,

I took a look at the SC routine and this is what I found:

/* CHECK FOR AFFINITY AND STACKED VOLUMES                      
/**
                                                               
    WHEN ( ='AFF=SMST' OR ='REF=ST' )              
    DO                                                         
          IF  NE '' THEN                              
          SET  =                             
          ELSE DO                                              
                  SELECT                                       
                       WHEN ( = 'SHSMF')            
                        SET  = 'SCSMF'             
                       WHEN ( = 'SHVTS')            
                        SET  = 'SCVTS'       

..etcetc. etc.

In your example you have a FILTLIST built but in this ACS routine there is 
none.  In your view do I need to build the FILTLIST?




On Tue, 10/11/15, Vernooij, CP (ITOPT1) - KLM <kees.verno...@klm.com> wrote:

 Subject: Re: JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF 
DATA SET
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, 10 November, 2015, 10:27 AM
 
 Check you ACS routines. 
I have the following filtlist to recognize an allocation of tape devices. I 
remember having to add the AFF string for the same purpose when moving from 
Storage Tek (then Sun, then Oracle) to TS7740 libraries:

FILTLIST UNIT_VTS INCLUDE('TS7740',   
  'AFF=SMST', 
  '3480', 
  '3490', 
  'TAPE', 
  'TAPE2')

Kees. 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John Dawes
 Sent: 10 November,
 2015 16:19
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: JCL QUESTION :IGD17045I SPACE NOT
 SPECIFIED FOR ALLOCATION OF DATA SET
 
 G'Day 
 
 I
 have a problem with allocating a dsn to tape.  This problem
 started when we transferred from Oracle VSM to IBM VTS. 
 
 
 The error message is as
 follows:
 
 IEF344I MVRXL#JP
 TSO CUMUL OUTPUT01 - ALLOCATION FAILED DUE TO DATA FACILITY
 SYSTEM ERROR
 IGD17045I SPACE NOT SPECIFIED
 FOR ALLOCATION OF DATA SET                   
    
 SYSCICS.CICS.CICSVP.G0005V00   
    
 
 This job has
 been running without any problem when it was allocated under
 VSM however with the switch to VTS the abends have occurred
 due to the AFF parm.
 
 Below
 is the jcl:
 
 //ACUMUL  EXEC
 IKJEFT01,                       
    
 //         
    PARM=('CICSAPP')             
     
 //*                     
                          
 //STEP1  DD
 DISP=(SHR,PASS),DSN=&     
    
 //CICSLIST DD
 DSN=&,DISP=(SHR,DELETE)      
 //SYSTSPRT DD SYSOUT=*               
             
 //SYSPRINT DD SYSOUT=* 
                           
 //SYSTSIN  DD DUMMY                 
              
 //*       
                                    
    
 //A3490    DD 
 UNIT=(3490,,DEFER)                 
 //OUTPUT01 DD DSN=SYSCICS.CICS.CICSVP(+1), 
 //            DISP=(NEW,CATLG,DELETE), 
           
 //           
 DCB=MODDSCB,                        
 //            RECFM=VB,LRECL=32756,   
            
 //         
   UNIT=AFF=A3490,LABEL=EXPDT=99000    
 
 As a temporary workaround I
 have removed the AFF parm (UNIT=3490,LABEL=EXPDT=99000)
 however because of JCL changes that would need to be done
 which the user would like to avoid can something else be
 done?
 
 Please note that NO
 SMS changes have been done since 2013 even though the error
 message points out to a SMS problem.
  
 Thanks. 
 
 
 //*                 
                              
 
 --
 For IBM-MAIN subscribe / signoff / archive
 access instructions,
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN
 
 For information, services and offers, please
 visit our web site: http://www.klm.com. This e-mail and any
 attachment may contain confidential and privileged material
 intended for the addressee only. If you are not the
 addressee, you are notified that no part of the e-mail or
 any attachment may be disclosed, copied or distributed, and
 that any other action related to this e-mail or attachment
 is strictly prohibited, and may be unlawful. If you have
 received this e-mail by error, please notify the sender
 immediately by return e-mail, and delete this message. 
 
 Koninklijke Luchtvaart
 Maatschappij NV (KLM), its subsidiaries and/or its employees
 shall not be liable for the incorrect or incomplete
 transmission of this e-mail or any attachments, nor
 responsible for any delay in receipt. 
 Koninklijke Luchtvaart Maatschappij N.V. (also
 known as KLM Royal Dutch Airlines) is registered in
 Amstelveen, T

JCL QUESTION :IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

[John Dawes]

G'Day 

I have a problem with allocating a dsn to tape.  This problem started when we 
transferred from Oracle VSM to IBM VTS.  

The error message is as follows:

IEF344I MVRXL#JP TSO CUMUL OUTPUT01 - ALLOCATION FAILED DUE TO DATA FACILITY 
SYSTEM ERROR
IGD17045I SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET   
SYSCICS.CICS.CICSVP.G0005V00   

This job has been running without any problem when it was allocated under VSM 
however with the switch to VTS the abends have occurred due to the AFF parm.

Below is the jcl:

//ACUMUL  EXEC IKJEFT01,   
// PARM=('CICSAPP')  
//*   
//STEP1  DD DISP=(SHR,PASS),DSN=& 
//CICSLIST DD DSN=&,DISP=(SHR,DELETE)  
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTSIN  DD DUMMY   
//*   
//A3490DD  UNIT=(3490,,DEFER) 
//OUTPUT01 DD DSN=SYSCICS.CICS.CICSVP(+1), 
//DISP=(NEW,CATLG,DELETE),
//DCB=MODDSCB,
//RECFM=VB,LRECL=32756,   
//UNIT=AFF=A3490,LABEL=EXPDT=99000

As a temporary workaround I have removed the AFF parm 
(UNIT=3490,LABEL=EXPDT=99000) however because of JCL changes that would need to 
be done which the user would like to avoid can something else be done?

Please note that NO SMS changes have been done since 2013 even though the error 
message points out to a SMS problem.
 
Thanks. 


//*   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

ISMF QUESTION

[John Dawes]

G'Day,

I am trying to compile a report on space allocation for certain dsns.  I am 
generating a new list.   However for some reason the SPACE & UNIT columns are 
blanks.  Is there a way of  getting this missing information?   I receive no 
error message.  Can someone suggest what I am failing to do?   
 
 ALLOCALLOC
   DATA SET NAMESPACEUNIT 
(2)---(3)--- -(9)-
SYS2.CIC190.ACCOUNT -  --- 
SYS2.CIC190.ACCOUNT.G1756V00 - --- 
SYS2.CIC190.ACCOUNT.G1757V00 - --- 
SYS2.CIC190.ACCOUNT.G1758V00 - --- 
SYS2.CIC190.ACCOUNT.G1759V00 - --- 
SYS2.CIC190.ACCOUNT.G1760V00 - --- 
SYS2.CIC190.ACCOUNT.G1761V00 - --- 
SYS2.CIC190.ACCOUNT.G1762V00 - --- 
SYS2.CIC190.ACCOUNT.G1763V00 - --- 
SYS2.CIC190.ACCOUNT.G1764V00 - --- 
SYS2.CIC190.ACCOUNT.G1765V00 - --- 
SYS2.CIC190.ACCOUNT.G1766V00 - --- 
SYS2.CIC190.ACCOUNT.G1767V00 - --- 
SYS2.CIC190.ACCOUNT.G1768V00 - --- 
SYS2.CIC190.ACCOUNT.G1769V00 - ---

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: ISMF QUESTION - PROBLEM SOLVED

[John Dawes]

I found my error.  I did not have the Y in the Acquire Data from Volume . . . . 
. . . Y

The SPACE is displayed with a value of K e.g.  55K.  Can it be changed to 
display tracks or  cylinders?

Thanks.

On Mon, 28/9/15, John Dawes <jhn_da...@yahoo.com.au> wrote:

 Subject: ISMF QUESTION
 To: "IBM Main" <ibm-m...@bama.ua.edu>
 Received: Monday, 28 September, 2015, 9:49 AM
 
 G'Day,
 
 I am trying to compile a report on space allocation for
 certain dsns.  I am generating a new
 list.   However for some reason the SPACE
 & UNIT columns are blanks.  Is there a way of 
 getting this missing information?   I receive
 no error message.  Can someone suggest what I am
 failing to do?       
    
                
                
      
                
          
    ALLOC    ALLOC    
        DATA SET NAME   
             SPACE   
 UNIT     
 (2)       
                
 ---(3)--- -(9)-    
 SYS2.CIC190.ACCOUNT           
      -  --- 
    
 SYS2.CIC190.ACCOUNT.G1756V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1757V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1758V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1759V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1760V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1761V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1762V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1763V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1764V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1765V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1766V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1767V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1768V00 - --- 
    
 SYS2.CIC190.ACCOUNT.G1769V00 - ---

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: QUESTION ABOUT SPACE ABEND - THANK YOU

[John Dawes]

Thanks to all who responded to my question.  Sorry for the late thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

QUESTION ABOUT SPACE ABEND

[John Dawes]

G'Day,

I would like to know what the abend code would be if the dsn did not have 
enough space allocated to it?  Below is an example of a space abend when the 
volume is out of space: For an output data set, all space was used on the 
current volume and no more volumes were specified.:

IEC030I B37-04,IFG0554A,DBA041D,DB041D16,SORTOUT,C6B7,ZL0024,04210011,  178   
WESP.PTNOTES1.SHADOW  
+WER999A BA041DP ,STEP010 ,BA041D16-  UNSUCCESSFUL SORT B37 S REASON=0004 I




Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: LOOKING FOR INFO

[John Dawes]

Thanks for the info.  I will check it out.  Offhand would you know if there is 
a way of checking it online i.e. logging into the VTS?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

LOOKING FOR INFO

[John Dawes]

G'DAY,

Is there a way of knowing how many logical controllers that are on a TS3500?  I 
logged in to it (TS30)) and viewed all the panels however I couldn't find the 
info.  I GOOGLED TS3500 and I found this excerpt:
The TS3500 Tape Library can support up to four 3953 tape systems, up to eight 
IBMVirtualization EngineTS7740 subsystems per physical library, and up to 
sixteen IBMSystem Storage Tape Controllers for System z per logical library. 

We have 6 libraries.  So if my math is correct there are 96 tape controllers.  
Am I on the right track?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SDSF QUESTION ; FILTER : OPTION 7

[John Dawes]

Thanks.  It is what I am looking for.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SDSF QUESTION ; FILTER : OPTION 7

[John Dawes]

G'Day,

I am trying to display all replies of each syslog on SYSPLEX envrionment via 
SDSF. When in SDSF I place the cursor unde Filter, next I choose 7 followed by 
*.  The outstanding messages are displayed however the LPAR name is not shown.  
Is there something I have forgotten to do?

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IDEAL SIZE OF VTOC VVDS FOR PAGE VOLUME

[John Dawes]

Great.  Thanks for the help.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

IDEAL SIZE OF VTOC VVDS FOR PAGE VOLUME

[John Dawes]

G'Day,

I have to initialise a 3390-9 volume as a PAGE volume.  What would be the ideal 
size of the VTOC  VVDS?  I was thinking 29 tracks for the VTOC and 15 for the 
VVDS.  Any suggestions? 

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

TESTING SMS ACS ROUTINE OPTIONS VIA ISMF

[John Dawes]

G'Day,

I have to test my changes to the SC routine before I put in production.  I 
would like to test the routine to ensure that certain USER  JOBNAME would 
allocate a PDS and PDS-E (LIBRARY). In the ISMF panel the option for DSORG I 
type PO and it works however I do not know what I should use for PDS-E or 
LIBRARY.
The doc : DFSMS Using the Interactive Storage Management Facility, doesn't tell 
me how.  Is there a way of testing for a PDS-E condition?

Thanks.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: UNABLE TO COPY PDS.

[John Dawes]

Willie answered for me on my behalf because I wasn't receiving Yahoo mail .  
Thanks Willie.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: UNABLE TO COPY PDS.

[John Dawes]

Dave,

Finally Yahoo e-mail is functioningg.  I was not receiving any e-mails from 
IBM-MAIN0  Thanks Willie for helpin out.

You are correct.  The PDS was corrupted i.e. every member I browsed gave an I/O 
error message.  I used IEBGENER to correct the problem which I had gleaned from 
the archive files.  If I understand you correctly there was no need to change 
the DCB of the corrupted dsn.  All I had to do was wrie a new member in the pds.
Can I revert back from RECFM=U to RECFM=VBA etc?  Or all is lost?



On Fri, 7/11/14, Gibney, Dave gib...@wsu.edu wrote:

 Subject: Re: UNABLE TO COPY PDS.
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Friday, 7 November, 2014, 4:57 PM
 
 I interpreted the
 original post as an attempt to recover from the classic
 mistake writing to a PDS using IEBGENER.
 I
 suspect the original PDS, before corruption, was VBA137.
 With BLKSIZE 27920. The correct fix is to write a new member
 using IEBGNER and the correct DCB specified on SYSUT2. Given
 that there may have been other attempts at fixing this, I
 hope the OP has been working with a copy. Corrupting
 corruption is rarely a step in the right direction.
 
  -Original
 Message-
  From: IBM Mainframe
 Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
  On Behalf Of R.S.
 
 Sent: Friday, November 07, 2014 1:45 PM
 
 To: IBM-MAIN@LISTSERV.UA.EDU
  Subject: Re: UNABLE TO COPY PDS.
  
  W dniu 2014-11-07 o
 16:13, John Dawes pisze:
  
 G'Day,
  
 
  Just wondering if it is possible to copy a pds with the
 following attributes:
  
   INPUT DSN:
 
 
   RECFM=U
 
  LRECL=137
   BLKSIZE=32760
  
   OUTPUT
 DSN:
   REDFM=VBA
   LRECL=137
  
 BLKSIZE=27920
  
 
 
  (appendix).
 
 
  First, try to copy the PDS to another
 RECFM=U PDS, or simply use LIKE= JCL
 
 construct. In case of errors copy selected members.
  
  --
  Radoslaw Skorupka
 
 Lodz, Poland
  
  
  
  
  
  
  --
  Treść tej
 wiadomości może zawierać informacje prawnie chronione
 Banku
  przeznaczone wyłącznie do
 użytku służbowego adresata. Odbiorcą może być
  jedynie jej adresat z wyłączeniem
 dostępu osób trzecich. Jeżeli nie jesteś
  adresatem niniejszej wiadomości lub
 pracownikiem upoważnionym do jej
 
 przekazania adresatowi, informujemy, że jej
 rozpowszechnianie, kopiowanie,
 
 rozprowadzanie lub inne działanie o podobnym charakterze
 jest prawnie
  zabronione i może być
 karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo,
  prosimy niezwłocznie zawiadomić nadawcę
 wysyłając odpowiedź oraz trwale
 
 usunąć tę wiadomość włączając w to wszelkie jej
 kopie wydrukowane lub
  zapisane na
 dysku.
  
  This
 e-mail may contain legally privileged information of the
 Bank and is
  intended solely for
 business use of the addressee. This e-mail may only be
  received by the addressee and may not be
 disclosed to any third parties. If
  you
 are not the intended addressee of this e-mail or the
 employee authorized
  to forward it to
 the addressee, be advised that any dissemination,
 copying,
  distribution or any other
 similar activity is legally prohibited and may be
  punishable. If you received this e-mail by
 mistake please advise the sender
 
 immediately by using the reply facility in your e-mail
 software and delete
  permanently this
 e-mail including any copies of it either printed or saved
 to
  hard drive.
  
  mBank S.A. z siedzibą w Warszawie, ul.
 Senatorska 18, 00-950 Warszawa,
 
 www.mBank.pl, e-mail: kont...@mbank.pl
  Sąd Rejonowy dla m. st. Warszawy XII
 Wydział Gospodarczy Krajowego
  Rejestru
 Sądowego, nr rejestru przedsiębiorców KRS 025237,
 NIP: 526-
  021-50-88. Według stanu na
 dzień 01.01.2014 r. kapitał zakładowy mBanku
  S.A. (w całości wpłacony) wynosi
 168.696.052 złote.
  
  
 
 --
  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