PowerHouse Migration Questions -- Batch jobs on unix
Joe Boyle
atla38@dsl.pipex.com
Wed, 19 Jan 2005 16:29:21 -0000
Some options - just a couple of the almost limitless possible variations.
I would imagine that you can say quiz auto=mycode.qzs < mycode.paras, where
file mycode.paras contains the responses prompted by a quick screen; you can
use $myfile as the open name for the parameter file and set the variable
myfile on user login or using setsystemval in the postpath proc of the para
request screen.
If you are running in batch the parsing time should'nt be an issue, but
typically quiz would run against the compiled .qzc file.
You can also use << eof syntax as below, again the file has to be written
each time before the file is AT'ed,
quiz << EOF
use mycode.qzs
parm1
parm2
...
exit
EOF
Regards, Joe.
This e-mail and all information contained in it is confidential and may be
legally privileged. If you are not the intended recipient, your access to
this e-mail is unauthorized. Any use, dissemination, distribution,
publication or copying by you of this e-mail or any of the information
contained within it is prohibited and may be unlawful. Do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. The content of this e-mail and any
attachments sent with it may have been altered without the consent or
knowledge of the author.
-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of John MacLerran
Sent: 19 January 2005 15:52
To: powerh-l@lists.sowder.com
Subject: PowerHouse Migration Questions -- Batch jobs on unix
Howdy List-ers!
We are in the <sarcasm> wonderful, glorious, breathtaking </sarcasm>
process of migrating from MPE to unix. One thing (of many) that is
raising some questions is how best to handle PowerHouse in batch on unix
(HP-UX specifically). Does anyone have some 'best practice' tips? A
couple of the most pressing issues are 'inline' code and prompting.
By inline code, I mean something like this:
!quiz dict=xyqdb.prod.acct
acc filexyz
set rep lim 42
set rep dev printer
go
exit
!eoj
I know this gives unix fits, because of the way it handles stdin. My
understanding of the best way to handle the above would be to break the
quiz code out into another file, then do a quiz auto=yadayada... My
question is "is that _really_ the best way, or am I overlooking
something?" I know this is a long shot, but does anyone have a script
(MPE, mpex, qedit, sh, or Perl) that will parse a job and attempt to
break it into separate files in preparation for changing the jobs to use
the auto= notation?
By prompting, I mean this: we use streamx to prompt for user input at
job submission time. The above quiz could look like this:
!quiz dict=xyqdb.prod.acct
acc filexyz
set rep lim ?enter report limit?
set rep dev printer
go
exit
!eoj
We also do more complex prompting, where we substitute the variables in
via the {} notation in streamx, but the concept is similar. Can
PowerHouse even prompt in batch on unix? Would it be better to re-code
the jobs to use system variables? Can items like the report limit above
even be defined that way?
I'd also be curious to find out which batch job 'handlers' are being
used by other PowerHouse shops, and which, if any, are 'better' than
others. (Price is a consideration, but not the only consideration --
some 'extra' money is available, as upper management understands the need.)
So, any takers?
--
----------------------------------------------------------------------
John MacLerran
IT Systems Analyst email: macljohn@isu.edu
Idaho State University V(208) 282-2954
http://www.isu.edu/~macljohn F(208) 282-3673
----------------------------------------------------------------------
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.