PDS with COBOL & Ezytrieve PGMS



Support for OS/VS COBOL, VS COBOL II, COBOL for OS/390 & VM and Enterprise COBOL for z/OS

PDS with COBOL & Ezytrieve PGMS

Postby debo » Mon May 03, 2010 5:11 pm

Hi,

We have a PDS with COBOL & Ezytrieve PGMS...That PDS Was full (Maximum no of members reached )..So i copied the PDS by giving option COPY.Then deleted the old one & again created with same name with more Directory Blocks...Then again copied the backed up PDS to Original..
Say

TEST.TEAM.COBOL - Original PDS

I copied like this
COPY TEST.TEAM.COBOL ---> TEST.TEAM.COBOL.BKUP

But when i see after that,first 4-5 bytes are coming diffrently in all the members...Can u help me?

I ll give some sample here

PNK (C8EZVT08 R)
*****************************
*T NASCO CLAIMS FOR VERMONT
*****************************
FLEA
-NO 01 12 A
NO 13 02 B
NO-ID 15 06 A
R-NO 21 03 A
EFF-DT 24 10 A
TERM-DT 34 10 A
TY-CD 44 03 A
EFF-DT 47 10 A
TERM-DT 57 10 A
NAME 67 15 A
1ST-NM 82 10 A


The First 4-5 bytes are truncated
debo
 
Posts: 19
Joined: Sat Apr 17, 2010 5:26 pm
Has thanked: 0 time
Been thanked: 0 time

Re: PDS with COBOL & Ezytrieve PGMS

 

Re: Help me -Very Urgent

Postby Robert Sample » Mon May 03, 2010 5:28 pm

Just a guess - your COPY may have treated every member as having COBOL line numbers. I always use batch jobs (IEBCOPY) to do this type of thing to prevent TSO assuming things about the data set. I also verify the copy before deleting and redefining the original.

And we installed PDS from the CBT tape (http://www.cbttape.org) which allows you to add directory blocks to a PDS without having to copy or redefine it.
Robert Sample
Global moderator
 
Posts: 3431
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 239 times

Re: Help me -Very Urgent

Postby CICS Guy » Mon May 03, 2010 9:00 pm

Could one of the two new PDSs been defined with variable records?
CICS Guy
 
Posts: 255
Joined: Wed Jun 20, 2007 4:08 am
Has thanked: 0 time
Been thanked: 0 time

Re: Help me -Very Urgent

Postby debo » Tue May 04, 2010 9:22 am

No..The Destination PDS is getting created with the same Attributes of Source PDS...

I tried again..When you use option 3.3 to copy the same COBOL PDS to another PDS,its working fine....But when we use COPY , Its creating members (ALL) with unexpected Truncation/Junk. Is there any way to get the original code from the collapsed PDS ?

Please help me..Its very important PDS with all Programs....We are not able Hrecover the PDs also.
debo
 
Posts: 19
Joined: Sat Apr 17, 2010 5:26 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Help me -Very Urgent

Postby dick scherrer » Tue May 04, 2010 9:45 am

Hello,

If this is an important file, there should be a "real" backup (not one that would be part hsm migration). Reload from the backup.

If for some reason, the file is not routinely backed up, suggest you talk with the storage management people to see if this might be restored from the disaster backups.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 92 times

Re: Help me -Very Urgent

Postby debo » Tue May 04, 2010 9:56 am

Hi Dick,

We asked Storage Management..They dont have Backup for this PDs since this PDS belongs to Test Region ..So is there any way to format the collpased PDS ?

Actually Why COPY is wotking like this ? Whats the diff b/w COPY & 3.3 option ?

Could You please explain in detail about COPY ?
debo
 
Posts: 19
Joined: Sat Apr 17, 2010 5:26 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Help me -Very Urgent

Postby dick scherrer » Tue May 04, 2010 10:06 am

Hello,

They dont have Backup for this PDs since this PDS belongs to Test Region ..
Suggest there should be disaster backups for test environments as well as production. . . It does not sound like good business to be willing to lose the environment where new development and production enhancement/repair is done. . .

You might ask if there are any full-volume dumps that have been taken and retrievem the pdsmfrom this.

Actually Why COPY is wotking like this ? Whats the diff b/w COPY & 3.3 option ?
I'm not connected to a mainframe now but i do not know which "copy" was used. When i want to copy a pds, i use 3.3.

Suggest you create a throw-away pds and go to the COPY you used. Then use PF1 and see what info is presented. There may be something about how the target dataset is created.

Not knowing what you have, i can't suggest how to "un-collapse" the file.

You might also look at the "info" about the problem dataset and one that is not damaged. This may show something.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 92 times

Re: PDS with COBOL & Ezytrieve PGMS

Postby debo » Tue May 04, 2010 10:16 am

We use endevor to stage the Pgms....So we are not taking regular backups....There is no much Impact because of this...All the resources have staged their modules to Endevor....But i feel Guilty..My Project Manager didnt tell anything..But if i can retrieve the PDS i will be Happy....

I have used COPY like this... in 3,4 option, if u give COPY as prefix to a PDS it will ask like this:
IKJ56700A ENTER 'TO' DATA SET NAME -


Here,whatever dataset u give,it will copy the source PDS.
debo
 
Posts: 19
Joined: Sat Apr 17, 2010 5:26 pm
Has thanked: 0 time
Been thanked: 0 time

Re: PDS with COBOL & Ezytrieve PGMS

Postby debo » Tue May 04, 2010 10:32 am

For Example a member have coding like this in the old one :
 ***************************** Top of Data ******************************
 PARM LINK (C8EZBH30 R)                                                 
 ************************************************************************
 * MODIFICATION LOG (MOST RECENT ON TOP):                               *
 ************************************************************************
 ************************************************************************
 FILE FILEA                                                             
   FIRST-343            1   343    A                                     
   PCC                  1     6    A                                     
   GRP-NO-ID            7     6    A                                     
   SUBGR-NO            13     3    A                                     
   PKG-NO              16     2    B                                     
   PKGSTRT             18    10    A                                     
   PKGEND              28    10    A                                     
   PKG-STAS-CD         38     2    A                                     
   SUBR-NO             40    12    A                                     

In the collapsed PDS,its coming like this :

***************************** Top of Data ************************
PNK (C8EZBH30 R)                                                         0019403I
00ÜÜÜÜÜ*
0004649F
00ÜÜÜÜÜ*
00ÜÜÜÜÜ*
 
******************************************************************
*ICATION LOG (MOST RECENT ON TOP):                               *
******************************************************************
******************************************************************
*MODULE PROCESSES A DB2 UNLOAD.                                  *
******************************************************************
FLEA                                                             
 -343            1   343    A                                     
                 1     6    A                                     
 O-ID            7     6    A                                     
 -NO            13     3    A                                     
 O              16     2    B                                     
 RT             18    10    A                                     
 D              28    10    A                                     
 TAS-CD         38     2    A
debo
 
Posts: 19
Joined: Sat Apr 17, 2010 5:26 pm
Has thanked: 0 time
Been thanked: 0 time

Re: PDS with COBOL & Ezytrieve PGMS

Postby dick scherrer » Tue May 04, 2010 11:44 pm

Hello,

It sounds like the allocation attributes for the output pds was not the same as the input. . .

If all of the code is in Endevor, you should be able to rebuild from the source stored in Endevor.

Suggest you majorly overhaul the way datasets are worked with. . .
1. Take regular backups.
2. When trying something, do not use the "real" dataset(s) for the attempt.
3. When copying a pds, it is often safest to make a copy (other than the regular backup) and then rename the "real" dataset to some other name - this will preserve the dataset attributes and content. Copy from the renamed dataset to a newly allocated "real" dataset and test this new dataset.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 92 times

Next

Return to IBM Cobol

 


  • Related topics
    Replies
    Views
    Last post