HP3000-L Archives

July 2000, Week 4

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:
Tracy Pierce <[log in to unmask]>
Reply To:
Tracy Pierce <[log in to unmask]>
Date:
Fri, 28 Jul 2000 13:06:49 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (98 lines)
So your solution may be to force MPE to execute your inner command, thus
avoiding the MPEX set-processing features which will try to overwrite the
same-name temp files.

> -----Original Message-----
> From: Emerson, Tom # El Monte [mailto:[log in to unmask]]
> Sent: Friday, July 28, 2000 12:01 PM
> To: [log in to unmask]
> Subject: Re: MPEX question (revisited)
>
>
> It's been a few years since I was a Vesoft tech, but the
> basic cause of this
> is that commands such as "listjob" AS WELL AS the
> REPEAT...FOR<whatever>
> routines internally use temporary files to build the list of
> "qualified"
> entities [files, jobs, sessions, accounts, whatever...]
> Because of this,
> most "set" related commands may fail when executed within a
> repeat...forxxx
> loop.
>
> [another way of looking at is is that the repeat...forxxx
> construct allows
> you to apply "set"-handling capabilites to a
> single-entity-only command by
> using the same internal logic that the already-set-enabled
> commands use, so
> executing a set-handling command inside of the "logic" that
> handles sets of
> objects causes confusion, much like this paragraph]
>
> > -----Original Message-----
> > From: Eben Yong [mailto:[log in to unmask]]
> > Sent: Friday, July 28, 2000 11:19 AM
> > To: [log in to unmask]
> > Subject: [HP3000-L] MPEX question (revisited)
> >
> >
> > Hi folks,
> >
> > I have been able to reduce the problem to what I feel is the
> > "irreducible
> > point".  Take a look at the session below.  Why is MPEX
> > refusing to do this?
> >
> > Eben
> >
> > %SHOWJOB JOB=@J
> >
> > JOBNUM  STATE IPRI JIN  JLIST    INTRODUCED  JOB NAME
> >
> > #J2     EXEC        10R LP       THU  7:20P  BACKG,MANAGER.VESOFT
> > #J4     EXEC        10S LP       THU  7:22P  FTPMON,FTP.SYS
> > #J5     EXEC        10S LP       THU  7:22P  JINETD,MANAGER.SYS
> > #J353   EXEC        10S LP       FRI  6:50A  JHTTPD,MGR.AIHBETA
> > #J437   EXEC        10S LP       FRI 10:11A  JRPCD,MANAGER.SYS
> > #J409   WAIT   D 5  10S LP       FRI  9:09A  CLMADT7,USER.AIHBETA
> > #J410   WAIT   D 5  10S LP       FRI  9:09A  CLMADT7,USER.AIHBETA
> >
> > 7 JOBS (DISPLAYED):
> >     0 INTRO
> >     2 WAIT; INCL 2 DEFERRED
> >     5 EXEC; INCL 0 SESSIONS
> >     0 SUSP
> > JOBFENCE= 7; JLIMIT= 7; SLIMIT= 20
> >
> > %LISTJOB #J409 <-------- SYNTAX IS OK; OUTPUT VERIFIES THIS
> > JOB#    STATE     DEV   INTRODUCED  Q PROGRAM  LOGON
> >
> > #J409   WAIT D5              9:09A
> > CLMADT7,USER.AIHBETA,PUB
> >
> > JOBFENCE = 7; JLIMIT = 7; SLIMIT = 20
> >
> > %REPEAT <-------- THIS REPEAT CONSTRUCT IS OK
> > %>LISTJOB #J409 <-------- BUT THE LISTJOB FAILS... WHY?
> > %>FORJOBS J409
> > Executing LISTJOB #J409
> > DUPLICATE TEMPORARY FILE NAME  (FSERR 101)
> > Error: Doing Frename (SR121.PUB.VESOFT) of SW121.PUB.VESOFT.
> > %REPEAT <---------- THIS REPEAT CONSTRUCT IS OK
> > %>ECHO ![RJOB.FMTJOB] <--------- THE ECHO STATEMENT IS OK
> > %>FORJOBS J409
> > #J409
> > %REPEAT <------- ANOTHER PROPERLY CONSTRUCTED REPEAT LOOP
> > %>ECHO ![RJOB.FMTJOB] <------- ECHO IS OK
> > %>LISTJOB ![RJOB.FMTJOB] <----- LISTJOB FAILS........???????
> > %>FORJOBS J409
> > #J409
> > Executing LISTJOB #J409
> > DUPLICATE TEMPORARY FILE NAME  (FSERR 101)
> > Error: Doing Frename (SR121.PUB.VESOFT) of SW121.PUB.VESOFT.
> > %
> >
>

ATOM RSS1 RSS2