|
Dave,
Coming from a mainframe background, I can relate to your problem ;-)
Unfortunately, on the iSeris (AS400) your limited to the System
Operator's Message Queue, the Joblog or a Diplay Device (Requestor).
>From the manual:
The location of the output data is dependent upon the type of
program initiation as follows:
--------------------------------------------------------------------
Method of Mnemonic-Name Associated Mnemonic-Name UPON Phrase
Initiation with SYSTEM-CONSOLE Associated with Omitted
REQUESTOR
BATCH System operator's message Job Log Job Log
queue
INTERACTIVE System operator's message Workstation Workstation
queue
---------------------------------------------------------------------
When I need to do something like this, I just add an additional
print file to the program (like QPRINT) and WRITE the output to it.
If your not concerned with creating page headers, overlow, etc.
then this is a very quick way to accomplish what you want in just
a few lines of code in the program...
If you find a solution using DISPLAY - I would sure love to see it :)
Terry
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pate, Dave
> Sent: Tuesday, July 19, 2005 3:53 PM
> To: 'MIDRANGE-L@xxxxxxxxxxxx'
> Subject: How can the output of COBOL DISPLAY stmts be sent to
> a separate spool file instead of the JOBLOG
>
> DISPLAY output in the S36e went to a spool file so that you
> could create a
> report using DISPLAY statements.
>
> Is there any way using Native COBOL CBLLE (Batch Job) to have
> the output
> from DISPLAY statements (like counters)
> to be put in it's own spool file instead of being put in the JobLog ?
>
> I tried DISPLAY xxx UPON SYSOUT and it still went to the JobLog.
>
> Thank You
>
>
> Dave Pate
> SC DDS - Information Technology
> (803) 896-6061
> Dave.Pate@xxxxxxx <mailto:Dave.Pate@xxxxxxx>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.