So what is needed is a little CI magic. Like

Setvar cierror 0
Showjob job,user.account>tmp1
If cierror = 0
   Print tmp1;start=4;end=4>tmp2
   Input j<tmp2
   Setvar jobnum lft(j,8)
   Altproc job=!jobnum;pri=cs
Else
   Echo cant find job.
Endif

I made this up, so there are probably better ways. I did this just to point
out that this is still do-able.



-----Original Message-----
From: VANCE,JEFF (HP-Cupertino,ex1) [mailto:[log in to unmask]]
Sent: Tuesday, January 18, 2000 1:41 PM
To: [log in to unmask]
Subject: Re: Changing job queue jobpak executes in through glance


> 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