HP3000-L Archives

August 1998, 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:
Andreas Schmidt <[log in to unmask]>
Reply To:
Date:
Wed, 19 Aug 1998 15:22:06 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
Tell to job is CIERROR 1627,
Tell to non existent session results in CIERROR 1619.

But the CIERROR variable looks to the LAST CIERROR, so that you cannot check
consistently.
You have to perform in such a loop a TELLOP per session/job ...

Other way within the same job which is not allowed to run concurrent to sessions
(O.K., I'm a sh enthusiast):

!JOB CHECK,MGR.TEST;OUTCLASS=,1
!
!COMMENT Check sessions in a particular account
!
!FILE X=X!HPPIN
!ECHO S=`callci "SHOWJOB [log in to unmask]"|grep "#S"|grep -c "!HPACCOUNT"` > *X
!ECHO echo $S >> *X
!SETVAR LOOP TRUE
!WHILE LOOP=TRUE
!   PAUSE 60
!   RUN SH.HPBIN.SYS < *X >S!HPPIN
!   INPUT SESS_NUM < S!HPPIN
!   IF SESS_NUM = "0" THEN
!      SETVAR LOOP FALSE
!   ENDIF
!ENDWHILE
!
!COMMENT Now, job may continue, e.g. block the account for sessions
!
!
!
!EOJ


But what will happen if a session may logon during the run of the job ?
If you do not have SEC/3000 in place you must invent own checks to ensure that
nobody will logon during this job's execution..

Best regards, Andreas Schmidt, CSC, Germany







[log in to unmask] on 08/19/98 02:03:21 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  Re: Session Checking for a Specific Account




Patrick,
You could do a "TELL" to "@.accountname" and then check the HPCIERR
variable. The value of it would vary depending on whether there were a
job or session or both logged on. Then it is a simple matter of looping
until the condition is met or stopping if that is what you want to do.
You don't say if the test is performed in a UDC/COMMANDFILE to determine
if the job should be streamed or if it is done by the job itself to
determine if it should continue, wait, or abort. That information would
be helpful.
 --
         --Pete Crosby  ([log in to unmask]  a.k.a. [log in to unmask])

Patrick wrote:
>
>My company has a Stream Job on our HP3000 that can only run if all SESSIONS
>are logged of a specific account.  The problem is the only way we know to
>check to see if there is any sessions logged on is to use the HP variable
>HPSESCOUNT in a IF test (IF HPSESCOUNT = 0 THEN ...) in a stream job.
>
>This works 90% of the time except when a person forgets to log off the
>console.  Does anybody know of a way to check for SESSIONS (Not Jobs) in a
>specific account tha can be used like the above IF test.
>
>Thanks in advance
>
>Patrick K. Faloney

ATOM RSS1 RSS2