|
View previous topic :: View next topic
|
| Author |
Message |
NJDevils28
New User
Joined: 11 Nov 2019
Posts: 10
Location: USA
|
|
|
|
All,
I have a bit of a dilemma.
I am new to Panvalet and the SME has left the company. We are in the midst of seeking a new SME and until then, I'm all we have.
To say I'm new would be a stretch. I know just enough to get me in trouble. Having said that, here is my issue.
I have 25K members in Panvalet that need to be copied to a PDS on the mainframe, then sent down to a MS Server.
The members are all COBOL, COPYBOOKS and the like.
The issue is that the first 8 characters of the linked members are the same and the 9th is the distinct.
What I mean is the COBOL program is named PGMNAME1 and the Copybook is named PGMNAME1C and the Include is named PGMNAME1I and the DB2 Includes are name PGMNAME1D and so forth.
When I submit the copy JCL, it only takes a single member and shoots out a message, That the "PGMNAME1" has already been copied.
Looking at the Documentation it clearly states that ONLY the first 8 characters will be used to copy to a PDS.
Is there a way around this and allow me to copy all the members?
Regards,
-Ron |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1205
Location: Dublin, Ireland
|
|
|
|
I faced this issue some years back. My approach was taken on a project-by-project basis where, for each project, I identified a character position from the first 8 that could be dropped and then generated control cards to copy from the 9-character Panvalet name to an 8-character PDS(e) name.
Garry. |
|
| Back to top |
|
|
NJDevils28
New User
Joined: 11 Nov 2019
Posts: 10
Location: USA
|
|
|
|
| Garry Carroll wrote: |
I faced this issue some years back. My approach was taken on a project-by-project basis where, for each project, I identified a character position from the first 8 that could be dropped and then generated control cards to copy from the 9-character Panvalet name to an 8-character PDS(e) name.
Garry. |
That sounds like a valid approach. I like it. I am no panvalet expert. Not even a newbie.
You would not be able to provide a sample JCL with the control cards, would you? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
why not build TWO pds'es
a <source> with the programs
where the names are left asis
a <include> with the copybooks
where the destination names are truncated at the last char
( the name mangling can be done using the sort product installed ) |
|
| Back to top |
|
|
NJDevils28
New User
Joined: 11 Nov 2019
Posts: 10
Location: USA
|
|
|
|
| enrico-sorichetti wrote: |
why not build TWO pds'es
a <source> with the programs
where the names are left asis
a <include> with the copybooks
where the destination names are truncated at the last char
( the name mangling can be done using the sort product installed ) |
All the members are in the same PANVALET library and when I execute the JCL it copies the first one, then error's out on the next one. I'm sure there is a way to do this with Control Cards as PANVALET uses them, I just don't know PANVALET. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1205
Location: Dublin, Ireland
|
|
|
|
I'm afraid I don't have the jobs I used for this ( I think it was back in 2006-7). IFIRC, I unloaded the members using the shop's change management software and used the memberlist to generate control cards using DFSORT.
| enrico-sorichetti wrote: |
why not build TWO pds'es
a <source> with the programs
where the names are left asis
a <include> with the copybooks
where the destination names are truncated at the last char
( the name mangling can be done using the sort product installed ) |
I don't think this would work as the first 8 characters of the copybook names are the same. You would end up with 'C', 'I' and 'D' copybooks with the same name which will also give you 'already copied' results.
Having a separate PDS for each copybook type might work if you modify the Cobol code to specify IN which library the copybook is to be found rather than default SYSLIB. However, this does involve source changes which could be achieved using the SORT product. There would be source changes anyway since the copybook names will have changed to 8 characters. Would this approach work for any languages other then Cobol?
Garry |
|
| Back to top |
|
|
NJDevils28
New User
Joined: 11 Nov 2019
Posts: 10
Location: USA
|
|
|
|
Thank you for all the help Gary! I'll try and Google my way through this.
-Ron
| Garry Carroll wrote: |
I'm afraid I don't have the jobs I used for this ( I think it was back in 2006-7). IFIRC, I unloaded the members using the shop's change management software and used the memberlist to generate control cards using DFSORT.
| enrico-sorichetti wrote: |
why not build TWO pds'es
a <source> with the programs
where the names are left asis
a <include> with the copybooks
where the destination names are truncated at the last char
( the name mangling can be done using the sort product installed ) |
I don't think this would work as the first 8 characters of the copybook names are the same. You would end up with 'C', 'I' and 'D' copybooks with the same name which will also give you 'already copied' results.
Having a separate PDS for each copybook type might work if you modify the Cobol code to specify IN which library the copybook is to be found rather than default SYSLIB. However, this does involve source changes which could be achieved using the SORT product. There would be source changes anyway since the copybook names will have changed to 8 characters. Would this approach work for any languages other then Cobol?
Garry |
|
|
| Back to top |
|
|
|
|
