Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Dataset lenght chaged for unknown reason.....HELP!!!!!

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
rchandran_19

New User


Joined: 08 Mar 2005
Posts: 34

PostPosted: Tue Nov 06, 2007 2:28 am    Post subject: Dataset lenght chaged for unknown reason.....HELP!!!!!
Reply with quote

Hi all,

I have a PDS where I have all my cobol programs. When I checked this morning, its all formatted differently. I can't even open in Edit mode. even if I say open with Edit....it still opens with Browse mode.

-------------------------------------------------------------------------------------
Name Prompt Alias-of Size TTR AC AM RM
_________ JRP007 *Viewed 00296F17 008608 24 24
_________ JRP007S 00250F16 006B06 24 24
_________ JRP032 00213F10 004908 24 24
------------------------------------------------------------------------------------

I can't even see my user ID on the screen to the right....its showing all this Alias-of, size which I have never seen before.

can anybody tell me what might have caused this change to my PDS and how to rectify it????

Thanks,
RC
[/img]
Back to top
View user's profile Send private message

superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Tue Nov 06, 2007 2:35 am    Post subject: Reply to: Dataset lenght chaged for unknown reason.....HEPL!
Reply with quote

Since you stated that the library is supposed to contain COBOL source code, did you or someone else attempt to use that PDS as the target ouput loadlib dataset for a COBOL compile process?
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10210
Location: italy

PostPosted: Tue Nov 06, 2007 2:44 am    Post subject: Reply to: Dataset lenght chaged for unknown reason.....HEPL!
Reply with quote

Most certainly Your pds containing source code was the target of a linkage editor and the recfm was changed to U

if You remember the original dcb attributes

RECFM=FB;LRECL=80,BLKSIZE=original_blksize

take a backup of Your corrupted dataset

then You can try to fix the dcb attributes by running a job like:
Code:

//IEB   EXEC PGM=IEBGENER,
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DUMMY LINE
//SYSUT2 DD DISP=SHR,DSN=your_dataset_name(DUMMYMBR),
// RECFM=FB,LRECL=80,BLKSIZE=the_original_blksize


otherwise restore from the most recent copy
Back to top
View user's profile Send private message
rchandran_19

New User


Joined: 08 Mar 2005
Posts: 34

PostPosted: Tue Nov 06, 2007 2:47 am    Post subject: Re: Reply to: Dataset lenght chaged for unknown reason.....H
Reply with quote

superk wrote:
Since you stated that the library is supposed to contain COBOL source code, did you or someone else attempt to use that PDS as the target output loadlib dataset for a COBOL compile process?


YES!!! I used it last week for an unrelated testing of another program. I compiled that program and gave the target as that PDS which is having the problem. Wow!! So, that why it has messed up my other programs in that PDS???!!!

How do I rectify it??? do I just delete the object module that used this PDS??

Please let me know?

Thanks,
RC
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Nov 06, 2007 2:52 am    Post subject:
Reply with quote

Hello RC,

Have you done what Enrico suggested? That has worked for others who have done the same thing.

Is there some reason that you "made up" some compile jcl for your program? Every developer should use standard compile/link jcl for all of their work. Custom jcl should not be used.

Two main reasons to use standard jcl are:
1. When some option is to be changed, it only needs to be changed in the standard jcl.
2. To prevent things like this from happening.
Back to top
View user's profile Send private message
rchandran_19

New User


Joined: 08 Mar 2005
Posts: 34

PostPosted: Tue Nov 06, 2007 2:53 am    Post subject: Re: Reply to: Dataset lenght chaged for unknown reason.....H
Reply with quote

enrico-sorichetti wrote:
Most certainly Your pds containing source code was the target of a linkage editor and the recfm was changed to U

if You remember the original dcb attributes

RECFM=FB;LRECL=80,BLKSIZE=original_blksize

take a backup of Your corrupted dataset

then You can try to fix the dcb attributes by running a job like:
Code:

//IEB   EXEC PGM=IEBGENER,
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
DUMMY LINE
//SYSUT2 DD DISP=SHR,DSN=your_dataset_name(DUMMYMBR),
// RECFM=FB,LRECL=80,BLKSIZE=the_original_blksize


otherwise restore from the most recent copy


You are absolutely correct. The recfm for that PDS has changed from FB to U.

Please let me know how you restore?

Thanks,
RC
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Nov 06, 2007 2:59 am    Post subject:
Reply with quote

Hello,

Your quote contains the step you need to run. . . The IEB step.
Back to top
View user's profile Send private message
rchandran_19

New User


Joined: 08 Mar 2005
Posts: 34

PostPosted: Tue Nov 06, 2007 3:03 am    Post subject:
Reply with quote

dick scherrer wrote:
Hello RC,

Have you done what Enrico suggested? That has worked for others who have done the same thing.

Is there some reason that you "made up" some compile jcl for your program? Every developer should use standard compile/link jcl for all of their work. Custom jcl should not be used.

Two main reasons to use standard jcl are:
1. When some option is to be changed, it only needs to be changed in the standard jcl.
2. To prevent things like this from happening.


Hello Dick Scherrer,

The reason why I had to use my own PDS is becuase that prgram was a sub-routine pgm, used by many other programs and it would not allow us to compile/link in the standard PDS for the object modules. So, i just gave my PDS.

I did not understand the JCL that Erico gave to restore. there are about 30 to 35 programs in that PDS...do I run the jcl for each program one at a time, for each program?

Thanks,
RC
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10210
Location: italy

PostPosted: Tue Nov 06, 2007 3:09 am    Post subject: Reply to: Dataset lenght chaged for unknown reason.....HEPL!
Reply with quote

Hi RC,

the step I gave You will not restore anything,
it will only fix the dcb of the pds so that You might be able to recover some sources...

Ffrom the description of Your actions I am afraid You will not recover too much...

usually the output member has the same name of the source member ...
so You might have overlaid a source with a load.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Nov 06, 2007 3:12 am    Post subject:
Reply with quote

Hello,

First, backup the pds as it is right now.

Second, modify the jcl Enrico posted for your dataset name and use the DUMMYMBR he mentioned ( you are not going to actually do anything to the other members in the pds - your job will reset the dcb attributes and all of your source (except may be the one that got linked over) should be "restored". It is not really a restore, but a reset of the definition of the pds.

Again - first back up what you have now. Hopefully not, but it may be needed.

Good luck, and someone will be here if there are questions.
Back to top
View user's profile Send private message
rchandran_19

New User


Joined: 08 Mar 2005
Posts: 34

PostPosted: Tue Nov 06, 2007 4:11 am    Post subject:
Reply with quote

dick scherrer wrote:
Hello,

First, backup the pds as it is right now.

Second, modify the jcl Enrico posted for your dataset name and use the DUMMYMBR he mentioned ( you are not going to actually do anything to the other members in the pds - your job will reset the dcb attributes and all of your source (except may be the one that got linked over) should be "restored". It is not really a restore, but a reset of the definition of the pds.

Again - first back up what you have now. Hopefully not, but it may be needed.

Good luck, and someone will be here if there are questions.


Thanks a lot!! I have fixed the problem by running the jcl which Enrico posted.

Thanks to both of you.

RC
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Nov 06, 2007 4:21 am    Post subject:
Reply with quote

You're welcome - good to hear it is fixed icon_smile.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts FTP - JCL failed while passing FTP co... Suneetha1612 JCL & VSAM 12 Wed Nov 16, 2016 7:33 pm
No new posts To trim spaces in a pipe delimited da... Nish84 COBOL Programming 16 Mon Oct 10, 2016 1:54 pm
No new posts Allocate dataset withour BLKSIZE Susanta CLIST & REXX 2 Thu Sep 22, 2016 11:51 am
No new posts dataset copy question - REPRO or some... atulxp TSO/ISPF 2 Wed Aug 03, 2016 10:56 pm
No new posts FTOPEN TEMP is failing due to dataset... mbenaud TSO/ISPF 7 Thu Jul 28, 2016 4:28 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us