HP3000-L Archives

January 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Tue, 18 Jan 2000 14:40:55 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
> While the Help does not indicate that jobname is accepted as
> input, the CI will accept it and perform the process.

I received a few replies like the one above, so I checked the code
and ran some examples.  The code shows no sign of accepting job
names, so why does something like:
   altproc job=jeff,mgr.c1601pat;pri=cs

seem to work?  Or better, substitute SHOWPROC for ALTPROC to
be safer in your testing -- the code exercised is basically
the same.

First notice that showproc job="jeff,mgr.c1601pat" reports an
error:
   Invalid user specification "JEFFV,MGR.C1601PA". (CIERR 11502)

Also, note that the syntax for SHOWPROC and ALTPROC allows a
list of PINs and/or a list of job specs.  So, the unquoted example
above is really specifying TWO job specs: the name "jeff" and the
name "mgr.c1601pat".  The name "jeff" is assumed to be a user name
and thus is qualified with the logon account name.  So, all PINs for
"jeff.logon_acct" and for "mgr.c1601pat" are displayed (or altered).

Hope this helps explain the mystery,
Jeff Vance, CSY

ATOM RSS1 RSS2