ISPF option 3.3 can copy to a new PDS and unpack as it copies. It's an
option on the panel.
 On Oct 12, 2012 5:34 PM, "Lizette Koehler" <[email protected]> wrote:

> Okay, I looked at the Dataset for PACK (DUH!!).  You are correct PACK ON
> is on the individual member.
>
> So now, is there a way to do PACK OFF  enmasse?
>
> Otherwise I have 342 members to individually edit.
>
> Thanks.
>
>
> Lizette
>
> -----Original Message-----
> >From: "Bass, Walter W" <[email protected]>
> >Sent: Oct 12, 2012 3:27 PM
> >To: [email protected]
> >Subject: Re: Strange PDS members
> >
> >Lizette,
> >
> >I agree with Skip Robertson.  EDIT PACK is probably on.  This not
> something defined per the dataset.  This is specified in the EDIT PROFILE
> and is applied at the MEMBER level, not the dataset level.  I.E. You can
> have just one member within a PDS saved with PACK ON and still have others
> saved with PACK OFF.  To verify, edit the member in question.  While in
> edit, show the PROF.  If it shows ....PACK ON.... in the profile, that is
> the problem.  To fix the member, type PROF UNLOCK on the command line (if
> the profile is locked), then type PACK OFF, then SAVE the member.  Now it
> should be OK.
> >
> >This is also why copy of the member gives you a good member.  ISPF COPY
> is smart enough to recognize the PACKed data and unpack it when it is
> copied.
> >
> >If this is the issue, you will need to repeat this for every member that
> has the problem.  Beware!  If you edit a member that has PACK ON, and your
> profile is UNLOCKED, your profile will automagically switch to PACK ON.
> >
> >I cannot test this at my site as they have ISPF installed with PACK ON
> disabled.
> >
> >Good luck,
> >Bill Bass
> >United HealthCare
> >Greenville, SC
> >
> >-----Original Message-----
> >From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Lizette Koehler
> >Sent: Friday, October 12, 2012 5:50 PM
> >To: [email protected]
> >Subject: Re: Strange PDS members
> >
> >The INFO on the dataset does not show PACK or SCLM turned on.
> >
> >The browse shows NO hex chars in the member.  Only when I unload the file.
> >
> >So far I have
> >
> >1)  Member looks normal
> >2)  Dataset does not have SCLM or PACK
> >3)  Dataset is NON SMS
> >4)  Unload of PDS using SAS Unload shows Hex Chars
> >5)  Browse, EDIT or VIEW does not show any HEX chars
> >
> >
> >Now the weirder part - I can copy the file to "fix" it.  then a later it
> is once again "magically" broken
> >
> >Lizette
> >
> >-----Original Message-----
> >>From: "Pommier, Rex R." <[email protected]>
> >>Sent: Oct 12, 2012 2:40 PM
> >>To: [email protected]
> >>Subject: Re: Strange PDS members
> >>
> >>Liz,
> >>
> >>What happens if you try to either edit or view the file?  Just as an
> experiment, I just edited a PDS member and purposefully added a hex
> character to it.  Browsing the member then just showed a period instead of
> the non-displayable character.  Editing or viewing the member threw up the
> "caution - data contains invalid characters" message that didn't appear in
> browse..
> >>
> >>Rex
> >>
> >>-----Original Message-----
> >>From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Lizette Koehler
> >>Sent: Friday, October 12, 2012 4:33 PM
> >>To: [email protected]
> >>Subject: Strange PDS members
> >>
> >>I have a strange issue. I browse a member of a PDS and it looks fine.
>  But if I use SAS UNLOAD and that same member is showing tons of hex
> characters.  IEBCOPY does not show any errors.
> >>
> >>Are there any FREEWARE PDS analysis tools?
> >>
> >>Or any ideas why a member might look normal in ISPF but with SAS Unload
> show lots of hex characters?
> >>
> >>Thanks..
> >>
> >>Lizette
> >>
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >send email to [email protected] with the message: INFO IBM-MAIN
> >
> >This e-mail, including attachments, may include confidential and/or
> >proprietary information, and may be used only by the person or entity
> >to which it is addressed. If the reader of this e-mail is not the intended
> >recipient or his or her authorized agent, the reader is hereby notified
> >that any dissemination, distribution or copying of this e-mail is
> >prohibited. If you have received this e-mail in error, please notify the
> >sender by replying to this message and delete this e-mail immediately.
> >
> >
> >----------------------------------------------------------------------
> >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

Reply via email to