|
View previous topic :: View next topic
|
| Author |
Message |
Emile Straker
New User
Joined: 27 Mar 2013
Posts: 5
Location: United Kingdom
|
|
|
|
We are replacing some of our CD jobs with the GDKUTIL program to send files from z/OS Mainframe to Cloud Object Storage.
Everything is working except where the destination filepath/name exceeds 72 chars, the name gets truncated at col 72, as in the following example:
| Code: |
=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
000008 //STEP010 EXEC PGM=GDKUTIL
000009 //SYSOUT DD SYSOUT=*
000010 //SYSPRINT DD SYSOUT=*
000011 //SYSUDUMP DD SYSOUT=D
000012 //SYSIN DD *
000013 UPLOAD PROVIDER(TESTIBMCOS) CONVERT
000014 //OBJNAME DD *
000015 /retail-test-batch-files/test1/account-index/inbound/test_accountindex_dg.dat
000016 //LOCAL DD DSN=BNK.AC99.DG99999.ACCT.STATUS(0),DISP=SHR
****** ******************************** Bottom of Data ******************************** |
I've tried splitting the name over two lines at col 72, also using a hyphen in col 72
I've also tried using a PDS member with LRECL 80, but all to no avail.
Does anyone know how to continue a long filepath/name over two or more lines?
Documentation on the internet is sparse to say the least!
Any help is greatly appreciated. |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1430
Location: Bamberg, Germany
|
|
|
|
Try using a USS dataset instead for your tests. Alternatively see what also may be worth to have a look at:
| Code: |
You can submit a data set to JES2 or JES3 with a record length of greater
than 80 bytes by submitting JCL like the following. In this example JCL,
IBMUSER.LONGDATA.JCL contains the data with a record length of greater
than 80 bytes. |
|
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1430
Location: Bamberg, Germany
|
|
|
|
Update:
New GDKUTIL DD name called OBJNAMEX
• Read each line of the DD to build the full object name, with leading and trailing whitespace from each line discarded, and the remaining characters are put together to create the long object name. |
|
| Back to top |
|
|
Emile Straker
New User
Joined: 27 Mar 2013
Posts: 5
Location: United Kingdom
|
|
|
|
Joerg, thanks for the two different options you supplied.
Using USS isn't an option at the moment as we don't have our code management tool configured for USS files at present.
However the OBJNAMEX is exactly what I need, so will test this tomorrow when I'm back in work.
BTW, where did you find this info?
Our mainframe is managed by a third party, so sometimes info about updates to software/utilities doesn't make it down to us grunts on the ground! |
|
| Back to top |
|
|
|
|
