Funny! Now I don't feel so bad about my own silly mistakes. Maybe it's
something to do with "sleeping on it". I spent 2 hours last night
wondering why the remote email server my C program was talking to would
not respond to a command line. This morning I got up and thought -
wait, it can't be that easy, and added a CRLF to the end of the command.
Duh...
On 11/10/2021 9:47 AM, Phil Smith III wrote:
Yesterday I needed to run a quick test of a USS-resident program from batch,
which I certainly knew was possible but had never done before. Found various
pages talking about how to use BPXBATCH, tried it. RC=0 but no program
output. None. Zero. Nada. Tinkered with DDs for STDOUT and STDERR
(SYSOUT=*), no joy. Tried routing to DASD, no joy. Scratched head, gave up
for the day.
Looked at it again this morning and saw the problem instantly. Now, as we
all know, there is no new JCL: every bit of JCL is descended from a fragment
found on a stone tablet on the side of a mountain near Poughkeepsie back in
the early 1960s. Every "new" job is just an old job, modified.
And it happened that the job I'd taken as my template had TYPRUN=SCAN.
Wasn't even aware I had any such.!
Presumably I won't make that mistake again.*
...phsiii
*This week
----------------------------------------------------------------------
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
