On Tue, 7 May 2019 15:54:19 +0000, Mark Jacobs <[email protected]>
wrote:
>They're called program objects in a PDS/e
^^^^^
PDSE
Pedants unite! ;-)
>
>Mark Jacobs
>
>
>Sent from ProtonMail, Swiss-based encrypted email.
>
>GPG Public Key -
>https://api.protonmail.ch/pks/lookup?op=get&[email protected]
>
>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>On Tuesday, May 7, 2019 11:50 AM, Blake, Daniel J [CTR]
><[email protected]> wrote:
>
>> Shmuel,
>>
>> I'm not sure what you mean by your statement > There are no load modules in
>> a PDSE. <
>>
>> Data Set Information
>> Command ===>
>>
>> Data Set Name . . . : TCPIP.SEZALOAD
>>
>> General Data Current Allocation
>> Management class . . : None Allocated tracks . : 2,963
>> Storage class . . . : None Allocated extents . : 1
>> Volume serial . . . : xxxxxx Maximum dir. blocks : NOLIMIT
>> Device type . . . . : 3390
>> Data class . . . . . : None
>> Organization . . . : PO Current Utilization
>> Record format . . . : U Used pages . . . . : 29,397
>> Record length . . . : 0 % Utilized . . . . : 82
>> Block size . . . . : 32760 Number of members . : 306
>> 1st extent tracks . : 2963
>> Secondary tracks . : 270
>> Data set name type : LIBRARY Dates
>> Data set version . : 1 Creation date . . . : 2018/01/31
>> Referenced date . . : 2019/05/07
>> Expiration date . . : None
>>
>> ;-D an
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [email protected] On Behalf Of
>> Seymour J Metz
>>
>> Sent: Tuesday, May 07, 2019 11:40 AM
>> To: [email protected]
>> Subject: [EXTERNAL MESSAGE] Re: COPYING PDS AND PDSE
>>
>> COPYMOD is for load module reblocking. There are no load modules in a PDSE.
>> Off the top of my head I don't even recall whether it is valid for program
>> objects. The COPY statement should work fine for PDSE.
>>
>>
>> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> Shmuel (Seymour J.) Metz
>> http://mason.gmu.edu/~smetz3
>>
>> From: IBM Mainframe Discussion List [email protected] on behalf of
>> esmie moo [email protected]
>> Sent: Tuesday, May 7, 2019 9:15 AM
>> To: [email protected]
>> Subject: Re: COPYING PDS AND PDSE
>>
>> I want to copy the PDSE to another. I was told that COPYMOD was the
>> preferable parm when copying LOADLIBS. Is it okay just to use COPY?
>> On Tuesday, May 7, 2019, 8:09:09 a.m. EDT, Elardus Engelbrecht
>> [email protected] wrote:
>>
>> esmie moo wrote:
>>
>> > Are there special parms that I need to use in the copy PDS & PDSE'S?
>>
>> It depends. Do you want to copy all or specific members?
>>
>> > For example if I want to copy a PDSE to another PDSE (some maybe LOADLIBS)
>> > would the following be okay?
>>
>> PS: I have doctored your JCL sample for better readability! ;-)
>>
>> //COPYJCL1 EXEC PGM=IEBCOPY
>> //SYSPRINT DD SYSOUT=*
>> //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(50,50))
>> //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(50,50))
>> //INDD DD DISP=OLD,DSN=MYDSN.CLIP.SHR
>> //OUTDD DD DISP=OLD,DSN=MYDSN.CLIP.SHR.NEW
>> //SYSIN DD *
>> COPY INDD=INDD,OUTDD=OUTDD
>> /*
>> //
>>
>> > Is the COPY command sufficient?
>>
>> It should be, a$$uming you want to copy ALL members without any reblocking
>> with COPYMOD and that both datasets RECFM, LRECL, BLKSIZE, etc. are the same.
>>
>> Perhaps you can drop SYSUT3 and SYSUT4 and add this one:
>>
>> //SYSOUT DD SYSOUT=*
>>
>> Are you getting any error message(s)?
>>
>> Groete / Greetings
>> Elardus Engelbrecht
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email
>> to [email protected] with the message: INFO IBM-MAIN
>>
>> ---------------------------------------------------------------------------------------------------------------------------------------
>>
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email
>> to [email protected] with the message: INFO IBM-MAIN
>>
>> ---------------------------------------------------------------------------------------------------------------------------------------
>>
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email
>> to [email protected] with the message: INFO IBM-MAIN
>>
>> ---------------------------------------------------------------------------------------------------------------------------------------
>>
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
