What DCB value is best for the //SYSEARL DD ?
Article ID: 103331
Updated On:
Products
Earl
Issue/Introduction
When using the //SYSEARL DD output control statement we sometimes receive a U3000 abend when attempting to force a specific DCB size.
We are not using the OPTION PRINTER=nnn in CA Earl.
When using the //SYSEARL DD output control statement we sometimes receive a U3000 abend when attempting to force a specific DCB size.
How do we avoid this situation?
We are not using the OPTION PRINTER=nnn in CA Earl.
When using the //SYSEARL DD output control statement we sometimes receive a U3000 abend when attempting to force a specific DCB size.
How do we avoid this situation?
Environment
z/OS any level
CA Earl 6.0 and above
CA Earl 6.0 and above
Resolution
The output DCB is dynamic for the //SYSARL DD and really should not be specified unless you are using the OPTION PRT= function. Even then, we have limits to the size of the output. (216 bytes)
The U3000 failure within CA Earl was in the I/O to the invalid DCB that did not match the dynmaic DCB that CA Earl wanted to allocate.
Let CA Earl do the DCB allocations when using the //SYSEARL DD for output files..
The U3000 failure within CA Earl was in the I/O to the invalid DCB that did not match the dynmaic DCB that CA Earl wanted to allocate.
Let CA Earl do the DCB allocations when using the //SYSEARL DD for output files..
Additional Information
see KD KB000053563 for information on the OPTION PRT= statement
See the CA Earl User GUide and the CA Earl System Programmer Guide for examples and specifications for using the the //SYSEARL DD statement for output.
See the CA Earl User GUide and the CA Earl System Programmer Guide for examples and specifications for using the the //SYSEARL DD statement for output.
Feedback
Yes
No
Powered by
