|
View previous topic :: View next topic
|
| Author |
Message |
Auryn
New User
Joined: 11 Jan 2006
Posts: 83
Location: Lower Saxony (DE)
|
|
|
|
Hi there everybody,
there are a lot of threads and posts here concerning packed datasets (ISPF prof status PACK ON).
A bit too much to read them all and a bit to difficult to find the hints I'm looking for.
And maybe my question is way to specific:
We have an application which runs on a decentral platform but needs sequential PS datasets / PO member downloaded via FTP from the mainframe.
In advance we have several jobs there that prepare (filter, sort, transform a.s.o.) the source data.
Some days ago our application crashed because one of the transfered input datasets looked corrupt somehow.
Examine the source dataset I found out it was saved with option PACK ON.
Now, my question is:
Is there a technical / automatical method to 'unpack' a dataset with any tool in a batch job?
Is there an option in IEBCOPY / IEBGENER?
Or is there an ISPF-Command I can execute via an IKJEFT01 step?
Thank you all for your hints |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| ISRLEMX |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
If you are current with ISPF levels, your systems programmer should be able to disable the use of PACK via the ISPF configuration table. This won't affect existing data sets, but will prevent the use of PACK in the future.
My shop has also been hit with production problems due to this feature. |
|
| Back to top |
|
|
|
|
