Rick, If you are using Printway Extended Mode, try using Infoprint Central to handle the job. If your printer definition is matching on DEST, CLASS, and FORMS, and you have changed those, you might need to change the DEST, CLASS, and FORMS on the held job to match the printer definition again. It's hard to tell without seeing all the data. You might need to open a problem record with IBM and then send the printer inventory dump and maybe a trace too. The pidu dump command includes job objects and shows more information than just the pidu export.
It sounds like the other suggestion and the comments about messing up the carriage control if copying the spool file to a dataset was referring to the XDC line command in SDSF. To preserve carriage control already in the file, you can preallocate a DDNAME to a dataset and then use the XFC command instead. Regards, --Roger On Tue, Jul 24, 2012 at 11:59 AM, Don Poitras <[email protected]> wrote: > It creates a VBA dataset. The carriage control should be preserved. > > Rick Stetser wrote: > > > > Thanks for the response. Unfortunately, this messes up the carriage > control and the file will no longer print correctly. > > -- > Don Poitras - zSeries R & D - SAS Institute Inc. - SAS Campus Drive > mailto:[email protected] (919)531-5637 Fax:677-4444 Cary, NC 27513 > > ---------------------------------------------------------------------- > 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
