Remember in the old days when issuing a JES2 command, if you had invalid
extra parms on the command string, JES2 would just ignore the invalid
stuff, truncate it and issue the part of the command that WAS correct?
Does it still work that way, or did IBM fix that "added feature" some time
ago?
>I goofed the value, JES2 truncated the bad part, and proceeded to purge ALL
>output
In 1981, $PQ was a valid (and dangerous) JES2 command.
I know: I issued it once (truncation problem).
Now, $PQ is invalid.
You have to have an argument.
To do what I did in 1981, you now have to issue $PQ,ALL (o
In a recent note, Mark H. Young said:
> Date: Fri, 16 Feb 2007 14:05:49 -0600
>
> Remember in the old days when issuing a JES2 command, if you had invalid
> extra parms on the command string, JES2 would just ignore the invalid
> stuff, truncate it and issue the part of the command that WA
3 matches
Mail list logo