LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (July 2002, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Wed, 17 Jul 2002 18:08:34 +0100
Reply-To:   Peter Crawford <peter.crawford@DB.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Peter Crawford <peter.crawford@DB.COM>
Subject:   Antwort: Re: Detecting if a batch job is running
Comments:   To: Ace <b.rogers@VIRGIN.NET>
Comments:   cc: Alistair_Gordon@standardlife.com
Content-type:   text/plain; charset=iso-8859-1

it was interesting to test this "filename pipe" for job status. I commented out the 'if...' filter and used my userId as jobname However, although the sas code worked, it was executing / pipe-ing the command , not to jes, but to OS/390 Unix +FSVIEW: WORK.DATA1 (B)---------------------------------------- ! Obs retline ! ! 1 *===================================================== ! 2 * ! 3 * OS/390 Unix System Services ! 4 * ! 5 * connected to system E004 Release ! 6 * ! 7 *===================================================== ! 8 setting up timezone... ! 9 setting up aliases ... ! 10 setting up environment ... ! 11 export: /etc/profile 74: FSUM7354 ":/tools:.:/usr/lpp/hpj/bin" is not !

I'm sure the sas-l archives have a way of executing jes/sdsf in batch and issuing sdsf commands output to a file. I'm not sure if that is possible through a pipe, but it might be possible in the way external progs can be run in sas on os/390, just like proc ftp ! i.e. something along the lines.... 1 allocate filenames for the files needed by sdsf-in-batch 2 write the status commands to the input file for sdsf 3 submit proc sdsf; run; 4 decode the files output from sdsf-in-batch

has anyone donee this already ?

Regards Peter Crawford

Datum: 17.07.2002 17:23 An: SAS-L@LISTSERV.UGA.EDU

Antwort an: Ace <b.rogers@VIRGIN.NET>

Betreff: Re: Detecting if a batch job is running Nachrichtentext:

On 17 Jul 2002 00:58:00 -0700, Alistair_Gordon@standardlife.com (Alistair Gordon) wrote:

>Thanks for all the replys so far. To shed some light on my situation: >we have an interactive SAS AF app that is updated by three overnight >batch jobs and is available for use during the working day in the UK. >We now have users in Hong Kong who need to use the system and as they >are some hours ahead of the UK they are using the system when it's >night here, and they are consequently contending with the batch jobs. >So what I want is something that checks, at system invocation, to see >if the batch jobs are running and stops the user from entering the >system if they are. > >I know I could achieve something to the same effect by updating >flags/files at job start and end, but I was wondering if there might >be a system call or function lurking out there that someone is aware >of.

One poster suggested using the ST (status) command. This could (I think, although I've never done it on MVS) be included in a filename pipe, something like this:

%let jobname = XX1232ABC ; filename status pipe "Status &jobname" ; data ; infile status truncover; input retline $100. ; if index(retline,'EXECUTING') then /* action to avoid continuing, e.g. set a symbolic variable */ run;

If this isn't valid on MVS, you'd perhaps need a REXX program to read the return value instead.

-- Ace in Basel - bruce dot rogers at roche dot com

--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Back to: Top of message | Previous page | Main SAS-L page