On Fri, 12 Oct 2012 17:39:57 -0500, John McKown wrote:
>>
>> -----Original Message-----
>> >From: "Bass, Walter W" <[email protected]>
>> >Sent: Oct 12, 2012 3:27 PM
>> >
>> >
>> >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.
>> > 
This is another case of implementation in the wrong layer.  This operation
should be performed, if at all, by DFSMS, so it would be available to all
applications, and a packed SYSLIB or even STEPLIB could be used directly,
without unpacking all the members.

But this becomes increasingly irrelevant as virtual DASD controllers can
perform pack/unpack at the control unit level.  I suppose this trades
channel bandwidth for CPU cycles and compatibility.

>> >I cannot test this at my site as they have ISPF installed with PACK ON
>> disabled.
>> >
Good idea.  But can you still UNPACK archival data sets?

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to