"John P. Hartmann" wrote: > You need to allocate SYSTSPRT to see the REXX error message. The book > is very clear about this, but then nobody reads the book.
One of the TSO REXX books? One of the many other TSO books? A BatchPipes book? I don't even have a clue where to find that one. Oh, I see, the Pipelines Author's Edition, right in the "Where Do I Start?" chapter. I'm just so used to finding everything I need from there in the HELPLIB! Hmmmm, something the book doesn't mention is that SYSTSIN must also be allocated for any console input (PARSE EXTERNAL, TRACE ?). At least with SYSTSPRT allocated that became obvious as soon as it mattered, though: IRX0555E The input or output file SYSTSIN is not allocated. It cannot be opened for I/O. For MVS ignorami like me trying to get started using familiar tools, it could be useful to include these specific commands as examples for routing I/O to the terminal: ALLOCATE FILE(SYSTSPRT) DATASET(*) ALLOCATE FILE(SYSTSIN) DATASET(*) Even then, interactive trace didn't recognize null input lines. I had to enter "TRACE 1" to get each instruction to run. Am I missing some other TSO arcana, or am I just stuck with this? This fixes my abends, but REXXVARS called by RUNPIPE still can't see the caller. REXXVARS called by CALLPIPE can, so I suppose I could reallocate SYSTSPRT temporarily to toss the error messages: ALLOCATE FILE(SYSTSPRT) DUMMY > You are aware that BPW is 1.1.9? I was as soon as I tried to use INSERT! Fortunately, what I need most right now, LOOKUP AUTOADD, is there. ¬R
