On Thu, 14 Jul 2022 12:27:49 -0400, Phil Smith III wrote:
>Paul Gilmartin wrote:
>
>>Which component recognizes the '#' or the '15'x? CP or VM (or XEDIT)?
>
>CP. But if you type DEF STOR 16M#IPL on the CMS command line, then CP splits
>it into two lines that CMS sees, so the IPL gets lost. If you do CP DEF STOR
>
IBM couldn't have done it worse. Obviously. Because if they could have, they
would have.
>16M#IPL, same thing. If you do #CP DEF STOR 16M#IPL, it works because the
>#CP goes directly to CP and CMS never sees the command at all.
>
I use PA1 to do about the same thing.
>>I've generally turned '#' off; it's a pitfall when I enter a command that
>contains
>
>>that character. This astonishes and dismays experts who try to assist me.
>
>Right, perverts :) like you are troublemakers.
>
Long story. I tried to view a file *distributed* by*IBM* with XEDIT. My
PROFILE XEDIT had such as:
ADDRESS CMS
... do some CMS stuff ...
ADDRESS XEDIT
'LOAD' FN FT FM /* Splits at the "#" in FN. */
I couldn't turn "#" off because of the implied LOAD.
>
To their credit, IBM took an APAR and made the XEDIT initial setting of
LINEND that from CP TERM.
>>But it's a valid filename character and occurs in some files distributed by
>>IBM.
>
>Sure. Just as \ is a valid character in a *ix filename (as is * for that
>matter).
>
but: 598 $ date >"foo \\ *
> bar"; printf '%s\n' foo*
foo \ *
bar
... they leave me a way around it. UNIX designers were thoughtful; IBM's
werem't.
Could I protect it with "#? I doubt it.
>My usual way to do this from an EXEC is DIAG 8-try this, it won't reIPL but
>will prove the point (and then it also works with DEF STOR 16M#IPL):
>
>call diag 8, 'M * HI1' '15'X 'M * HI2'
>
If you're not careful, you're left at CP READ with your VM reset.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
