IEFJOBS is a DD you add to MSTJCL00, points to a PDS that contains
JOBCARD and JOBCARD statements for started task
an IPL would be required IIRC for these changes be take place
the reason for your error
IEFC822I KEYWORD JESDS NOT SUPPORTED AFTER FIRST EXEC STATEMENT
is - the output statement need to be after a jobcard and before any EXEC
statement
Carmen
On 1/13/2022 2:09 PM, Phil Smith III wrote:
Gil wrote:
I'm curious: What sort of started task has implicit STDOUT and
STDERR? BPXBATCH? I thought BPXBATCH defaults STDIN,
STDOUT, and STDERR to /dev/null.
A started task that's in C and does printfs!
Does a JCL OUTPUT statement have any effect?
Can you be more specific? I've looked at
https://www.ibm.com/docs/en/zos/2.1.0?topic=reference-output-jcl-statement
and can't imagine what DD it would refer to, is the problem. I mean, if
//STDOUT DD SYSOUT=J
doesn't do anything, it seems like it's not the STDOUT DD?
Carmen Vitullo suggested IEFJOBS (which I don't understand at all), and also
OUTPUT with JESDS=ALL. I tried:
//OUT OUTPUT DEFAULT=YES,JESDS=ALL,CLASS=J
but it said:
IEFC822I KEYWORD JESDS NOT SUPPORTED AFTER FIRST EXEC STATEMENT
and then when I moved it before the first EXEC statement:
IEFC019I MISPLACED OUTPUT STATEMENT
Paging Mr. Wolf (if we were still Hewlett-Packard Enterprise, I'd say
"Enterprise to Kirk".)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
--
/I am not bound to win, but I am bound to be true. I am not bound to
succeed, but I am bound to live by the light that I have. I must stand
with anybody that stands right, and stand with him while he is right,
and part with him when he goes wrong. *Abraham Lincoln*/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
