HP3000-L Archives

January 2001, Week 5

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:
Michael Anderson <[log in to unmask]>
Reply To:
Michael Anderson <[log in to unmask]>
Date:
Mon, 29 Jan 2001 13:50:52 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
This has probably been discussed on this list before, but looking back two or three months I haven't found much info. I would like thoughts from others on the list about JOBQ's and how to implement them in an environment of programmatically streamed jobs. When job stream files are created and streamed programmatically I have no way to define different JOBQ's for each user or account. I do not have access to the source code.

My thoughts are to create a system level UDC that will override the real stream command. Then I would be able to add the necessary logic to the stream UDC to launch jobs into various JOBQ's.  

Back in the days of the classic HP3000 I wrote my own 'STREAM' program. This allowed me to (Without buying any third party software) read the stream file, and insert passwords and variables into the stream file before streaming it. I realized that I no longer had a need for this 'STREAM' program after M.P.E. variables came into existence, and PASSEXEMPT was added to the JOBSECURITY command.  Now with the introduction of JOBQ's I am felling the need to resurrect my old stream program. By analyzing the stream file I could programmatically decide what JOBQ it belongs in, and stream it into that Que. Has anyone been here and done this?

Thanks in advance,


--
Michael Anderson
Spring Independent School District
16717 Ella Boulevard
Houston, Texas 77090-4299
office: 281.586.1105
fax: 281.586.1187
-

ATOM RSS1 RSS2