Attributes were recfm=FB, lrecl=120 PDS. There were no I/O errors. I was able to copy the member via 3.3 to the sequential file without issue. Also, viewed it numerous times.
I will have to allocate my own copy and re-check it. As for the FREE... no harm no foul. If I had done an ALLOCATE ... it would be taken care of. The FREE causes no errors. Since there appears to be nothing other than PDS directory update issue... (not that it is normal.. but at least I can conceive of a way it would happen) Thanks for the input.. Rob Rob Schramm Senior Systems Consultant Imperium Group On Mon, Sep 23, 2013 at 1:10 PM, Scott Ford <[email protected]> wrote: > Rob: > > why do you want to free it ...its not clear why you need to ... > > If it was allocated dynamically or a file for temporary usage, 'yes' free > it , but allocated via a '// DD ' ...odd > > Scott J Ford > Software Engineer > http://www.identityforge.com/ > > > > ________________________________ > From: Rob Schramm <[email protected]> > To: [email protected] > Sent: Monday, September 23, 2013 10:31 AM > Subject: Rexx question > > > All, > > I was doing some rexx work in batch on z/OS... attempting to use > > "EXECIO * DISKR INPUTDD (Finis Stem in." > "FREE F(INPUTDD)" > > Where the INPUTDD was > > //INPUTDD DD DSN=SOME.PDS(MEMBER) > > and the results were very strange (multiple lines concatenated, seemed to > be picking up a prior member in the PDS, corrupted data). I ended up > copying the PDS member to a sequential file and the problems went away. > > I have never had a problem reading a PDS member as a sequential file.. > until this occurred. Is there some caveat to reading a PDS member as a > sequential file? Is the exception documented? > > I have been to the manuals, google, various articles on REXX, tutorials > etc.. and not found anything to match (even loosely) what was happening. > > > Rob Schramm > Senior Systems Consultant > > ---------------------------------------------------------------------- > 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
