We also had this problem with z/OS 1.7 and AMASPZAP. We opened a problem
with IBM but it turned out that CA PMO needed a fix.
Here's IBM's response:
I have a possible fix for you if you're running OEM CA PMO according to
ASKQ Item 40076227000 which involves CA fix T458284 PTF QO81747 .
We're also seeing this problem. We're migrating from z/OS 1.6 to 1.8. We
do have the fix for that apar installed.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the
Hi,
After we migrate to z/os 1.7. ASMSPZAP does not work. Anyone knows why? It
only shows SYSLIB I/O ERROR. I have checked the blocksize and dataset
organisation. All definition seems correct.
//FAMVSZAP EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSLIB DD
On Mon, 12 Feb 2007 17:25:28 +0800 Tommy Tsui [EMAIL PROTECTED] wrote:
:Hi,
:After we migrate to z/os 1.7. ASMSPZAP does not work. Anyone knows why? It
:only shows SYSLIB I/O ERROR. I have checked the blocksize and dataset
:organisation. All definition seems correct.
Show it.
://FAMVSZAP EXEC
: AMASPZAP doesn't work
On Mon, 12 Feb 2007 17:25:28 +0800 Tommy Tsui [EMAIL PROTECTED]
wrote:
:Hi,
:After we migrate to z/os 1.7. ASMSPZAP does not work. Anyone knows
why? It
:only shows SYSLIB I/O ERROR. I have checked the blocksize and dataset
:organisation. All definition seems correct.
Show
Tommy Tsui wrote on 2007-02-12 04:25:28:
After we migrate to z/os 1.7. ASMSPZAP does not work. Anyone knows why?
It
only shows SYSLIB I/O ERROR. I have checked the blocksize and dataset
organisation. All definition seems correct.
//FAMVSZAP EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
6 matches
Mail list logo