home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!darwin.sura.net!paladin.american.edu!auvm!UCBCMSA.BITNET!SPGMNF
- Message-ID: <IBM-MAIN%92072212210664@RICEVM1.RICE.EDU>
- Newsgroups: bit.listserv.ibm-main
- Date: Wed, 22 Jul 1992 10:06:34 PDT
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- From: "Mike Friedman (510) 642-1410" <SPGMNF@UCBCMSA.BITNET>
- Subject: Re: ESA 4.2 JES2 Routing Restriction
- In-Reply-To: Message of Wed,
- 22 Jul 1992 08:05:38 GMT from <pgilmart@NYX.CS.DU. EDU>
- Lines: 18
-
- On Wed, 22 Jul 1992 08:05:38 GMT Paul Gilmartin said:
- >
- >BTW, how can one meaningfully use a range of userids? Is there some
- >operator command which takes all jobs are in the range of (e.g)
- >Gilmartin-Woren (oops. typo) as the userid and purges them?
-
- Well, I know we have some VM users with all-numeric userids. Going one step
- further and supposing a userid of (say) 123-456, I suppose there is increasing
- opportunity for command ambiguity. I'm not familiar with all the JES2 commands
- that use ranges, especially in ESA 4.2, so I don't know how confusing it could
- get. In any case, IBM's adding of the parenthesized userid syntax in JES2
- commands (with the aforementioned APAR) is their way, I guess, of avoiding this
- particular kind of problem.
-
- (By the way, I believe the APAR description also says that the hyphen would
- be allowed on a JECL card only if the accompanying node is not the local node.
- Whether this is really enforced, I don't know. We don't even have the APAR
- on yet!).
-