Re: single thread job streams with the same name - Hewlett Packard

This is a discussion on Re: single thread job streams with the same name - Hewlett Packard ; Quoting Michael Caplin : >I searched the archive looking for something that would prevent multiple jobs >with the same job name from running at the same time. I found some >solutions but they were not fail-safe so I wrote something ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: single thread job streams with the same name

  1. Re: single thread job streams with the same name

    Quoting Michael Caplin :

    >I searched the archive looking for something that would prevent multiple jobs
    >with the same job name from running at the same time. I found some
    >solutions but they were not fail-safe so I wrote something that seems to be
    >fool-proof. It's a one line command at the front of a stream that invokes a
    >command file. The command file runs a small cobol program. If anyone has a
    >use for it, let me know.
    >Mike


    What does the small cobol program do?

    Any problem with posting a detailed description of the function of the cobol
    program and possibly the source on the list?

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  2. Re: single thread job streams with the same name

    I'll be happy to send the source and the command file to anyone who wants it. This is what it looks like when it's used in a stream. In this case, there were no other instances so the stream was allowed to run.

    :JOB SRXTRPJS,OPER.OPTICSBG,PRODEXEC.
    Priority = DS; Inpri = 8; Time = UNLIMITED seconds.
    Job number = #j3029.
    THU, NOV 1, 2007, 7:17 AM.
    HP3000 Release: C.70.01 User Version: C.70.01
    MPE/iX HP31900 C.39.06 Copyright Hewlett-Packard 1987.
    All rights reserved.
    STREAMED BY MONTHEND,OPER.OPTICSBG (#J2919) ON LDEV# 10
    STREAM DATE: THU, NOV 1, 2007, 4:17 AM
    :
    :COMMENT ************************************************** *****
    :COMMENT * IF THIS STREAM IS RUN BY MULTIPLE USERS AT THE SAME *
    :COMMENT * ONLY ONE AT A TIME WILL BE ALLOWED TO RUN. *
    :COMMENT ************************************************** *****
    :PAUSEJOB.COMMAND 600
    PAUSING (IF REQUIRED) WILL BE FOR 600 SECONDS

    THIS JOB = #J00003029
    CHECKING FOR: SRXTRPJS,OPER.OPTICSBG
    JOB IN QUEUE = #J00003029 EXEC
    LOWEST JOB# = #J00003029
    THIS JOB IS THE OLDEST, IT CAN RUN

    END OF PROGRAM
    THU, NOV 1, 2007, 7:17 AM

    >>> Matthew Perdue 11/19/2007 1:04 PM >>>

    Quoting Michael Caplin :

    >I searched the archive looking for something that would prevent multiple jobs
    >with the same job name from running at the same time. I found some
    >solutions but they were not fail-safe so I wrote something that seems to be
    >fool-proof. It's a one line command at the front of a stream that invokes a
    >command file. The command file runs a small cobol program. If anyone has a
    >use for it, let me know.
    >Mike


    What does the small cobol program do?

    Any problem with posting a detailed description of the function of the cobol
    program and possibly the source on the list?

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


+ Reply to Thread