Re: bpxpqrmxx and $SYSNAME vs
Thank you everyone This is what I thought. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Smith Sent: Monday, September 12, 2022 8:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: bpxpqrmxx and $SYSNAME vs The examples from the FM seem to generally use &-symbols when available, and $-symbols when not. $VERSION for example isn't a system-provided symbol, although I assign it from On a rather tangential rant, I am annoyed with people who gratuitously stuff $$$ all over in volsers, dsnames, and anything else they get their hands on, evidently just because they think $$$ are so sexy. Inside USS, these become extremely annoying in trying to figure out the required escapage. sas On Mon, Sep 12, 2022 at 11:15 AM Carmen Vitullo wrote: > I know the $SYSNAME. resolves to the system name but in my BPXPRMxx > member I use //etc and //var > > I use /$VERSION for my mount-point for the SYSRES specific mount point > for the version ROOT > > Carmen > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: bpxpqrmxx and $SYSNAME vs
The examples from the FM seem to generally use &-symbols when available, and $-symbols when not. $VERSION for example isn't a system-provided symbol, although I assign it from On a rather tangential rant, I am annoyed with people who gratuitously stuff $$$ all over in volsers, dsnames, and anything else they get their hands on, evidently just because they think $$$ are so sexy. Inside USS, these become extremely annoying in trying to figure out the required escapage. sas On Mon, Sep 12, 2022 at 11:15 AM Carmen Vitullo wrote: > I know the $SYSNAME. resolves to the system name but in my BPXPRMxx > member I use //etc and //var > > I use /$VERSION for my mount-point for the SYSRES specific mount point > for the version ROOT > > Carmen > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: bpxpqrmxx and $SYSNAME vs
I know the $SYSNAME. resolves to the system name but in my BPXPRMxx member I use //etc and //var I use /$VERSION for my mount-point for the SYSRES specific mount point for the version ROOT Carmen On 9/11/2022 11:43 PM, Lizette Koehler wrote: I have a coworker saying we should change our //etc/.. To /$SYSNAME/etc/. I am not familiar with coding this way Could someone provide a cons vs pros (simple words please) on which is needed, or used or preferred? Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: bpxpqrmxx and $SYSNAME vs
Since $ is a valid character in a SYSNAME, I dont think you want to make that change. Joe On Sun, Sep 11, 2022 at 11:44 PM Lizette Koehler wrote: > I have a coworker saying we should change our //etc/.. To > /$SYSNAME/etc/. > > > > I am not familiar with coding this way > > > > Could someone provide a cons vs pros (simple words please) on which is > needed, or used or preferred? > > > > Thank you > > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
bpxpqrmxx and $SYSNAME vs
I have a coworker saying we should change our //etc/.. To /$SYSNAME/etc/. I am not familiar with coding this way Could someone provide a cons vs pros (simple words please) on which is needed, or used or preferred? Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
