But Rob, that depends on the console being at 009 and on the target having a 190 (either as MDISK or as LINK). The good trick is simply "LINK userid", and I've hear somewhere (ages ago) that "IBM is aware of this trick", so they will not revert the logic (logically one would indeed first check the syntax of the LINK command and only when that is OK, start scanning the CP directory)
2007/10/26, Rob van der Heij <[EMAIL PROTECTED]>: > > On 10/25/07, Dale R. Smith <[EMAIL PROTECTED]> wrote: > > > "CP LINK userid" is the best way to tell if a userid is defined in the > > directory or not. "CP SPOOL PUN userid" will give a non-zero return > code > > If you have an ESM, there's a few more things to think of because that > might keep you from doing the SPOOL in the first place. And if you > LINK, make sure not to attempt something that will cause the ESM to > write audit records. And if you have XLINK active, you don't want to > link just for fun of linking. > > A popular trick used to be LINK someone 190 009 RR and inspect > various return codes (knowing that if the user existed, you'd still > not link because you have a console at 9 already). > > Rob > -- Kris Buelens, IBM Belgium, VM customer support
