ESP Workload Automation

Is there a way to tell if SSCAN is active? We had an IPL and schedule scan wasn't started and went undetected for several hours. I want to see if I could put a CA7 BTI on the queue before the IPL and issue a command to check after it. If it is not active I would like to send a WTO to the Master Terminal Is there a way for me to tell if SSCAN is bringing in new work? Will the next WAKE-UP = zeroes or something? I didn't see any examples in the CA7 documentation.

SSCAN

         CURRENT SCHEDULE SCAN VALUES

         ----------------------------

  SPAN = 120 INCREMENT = 60

         QUEUE DWELL = 30              SKELETON RETRY = 1

         REPROMPT    = 10              XP RETRY      =  0

         LEAD TIME   = 0

         STATUS:   REQQ IS ACTIVE      ABR MSGS  = NO

                   RDYQ IS ACTIVE      HOLD JOBS = NO

                             NEXT SCAN WAKE-UP = 16195 AT 1258

                   NEXT SCAN PERIOD START TIME = 16195 AT 1428

/DISPLAY,PRINT=SCH

*** SCHEDULE SCAN DISPLAY ***                                   PAGE 0001

                -------------MINUTES--------------  ---STATUS----

   NEXT SCAN    SPAN INCR QDWL REPR LDTM RTRY XTRY  REQ/Q   RDY/Q   ABR  HOLD

16.195 AT 1258  0120 0060 0030 0010 0000 0001 0000  ACTIVE  ACTIVE   NO   NO

Your next scan wake-up time will be screwy.  It will not be anywhere near to what it should be for this date/time. 

renate.

now for your other question....  That would be cool if we had something that would tell us that we hadn't turned it back on.

What do you mean screwy? I would like to issue the SSCAN command via CA7BTI and capture the SYSPRINT and check the "screwy" date via a SAS program.

the date doesn't make sense.   I don't remember what it says though.  I can't take my 7 down to see right now.  I'm not sure if it always says the same or something different...   Marysue would be the one to ask probably. 

renate

If schedule scan is turned off you will see:

NEXT SCAN WAKE-UP = 99999 AT 3679

from the SSCAN output.  However you cannot do a SSCAN in batch and get the output -- but you can do /DISPLAY,PR=SCH and the output will look much like:

99.999 AT 0000  0060 0060 0030 0010 0000 0000 0000  ACTIVE  ACTIVE   NO   NO 

With the NEXT SCAN being 99.999 AT 0000

So it is safe to say if I look for 99.999 on line # 15 (column # 2) of the BTI output of the /DISPLAY,PR=SCH command, SSCAN is not active?

000001 1BSTR-00  *** INPUT TO BATCH TERMINAL ***

000002

000003  /LOGON ********           * GENERATED LOGON *

000004  /DISPLAY,PR=SCH

000005 /LOGOFF * GENERATED LOGOFF *

000006 0BSTR-00  *** END OF INPUT ***

000007 1  16195  145548    /LOGON ********

000008

000009  CA-7.023 - r11.3(    ) OPERATOR IS LOGGED ON TO TERMINAL TBATCH7 AT 14:

000010 -  16195  145548    /DISPLAY,PR=SCH

000011 1 *** SCHEDULE SCAN DISPLAY ***                                   PAGE 0

000012                  -------------MINUTES--------------  ---STATUS----

000013     NEXT SCAN    SPAN INCR QDWL REPR LDTM RTRY XTRY  REQ/Q   RDY/Q   ABR

000014

000015  16.195 AT 1501  0120 0060 0030 0010 0000 0001 0000  ACTIVE  ACTIVE   NO

000016

000017

000018  SCM6-00 /DISPLAY COMPLETED AT 14:55:48 ON 16.195.

000019 -  16195  145548    /LOGOFF

000020

correct

Thanks Marysue -

Renate - I setup a job to run after our IPL to check SSCAN. It uses CA7 BTI, SORT, IDCAMS, and CA7 Trailer - SASSTRLR.

You can cut and paste and setup according to your installation.

//CHKSS  JOB (***,TEST,***),CLASS=x,MSGCLASS=x

//******************************************************

//* THIS JOB WILL CHECK IF SSCAN IS ACTIVE OR NOT

//* NEXT SCAN DATE = 99.999 MEANS NOT ACTIVE

//* NEXT SCAN DATE = CURRENT JULIAN = ACTIVE

//******************************************************

//STEP01     EXEC CA7BTI (Or your installations PROC)

//******

//STEPLIB    DD DSN=YOUR.STEPLIB,

//           DISP=SHR

//SASSBSTR.SYSPRINT DD DSN=DOCHKSS.OUTPUT,

//           DISP=(NEW,CATLG),

//           UNIT=SYSDA,

//           DCB=(BLKSIZE=23408,LRECL=133,RECFM=FB),

//           SPACE=(TRK,(1,1),RLSE)

/DISPLAY,PRINT=SCH

//******

//STEP02     EXEC PGM=SYNCSORT

//******

//SYSUDUMP   DD SYSOUT=Z

//SYSOUT     DD SYSOUT=Z

//SORTIN     DD DSN=DOCHKSS.OUTPUT,

//           DISP=SHR

//SORTOUT    DD DSN=SSCAN.SORTOUT,

//          DISP=(NEW,CATLG,CATLG),UNIT=SYSDA,

// DCB=(BLKSIZE=0,LRECL=132,RECFM=FB),

//          SPACE=(TRK,(1,1),RLSE)

//SYSIN      DD *

  SORT FIELDS=COPY

  INCLUDE COND=(2,06,CH,EQ,C'99.999')

//******************************************************

//** IDCAMS - SET COND CODE 4 IF NO 99.999 RECORD FOUND

//******************************************************

//IDCAMS01   EXEC PGM=IDCAMS

//DD1        DD DSN=SSCAN.SORTOUT,

//           DISP=SHR

//SYSPRINT   DD SYSOUT=Z

//SYSIN      DD *

PRINT INFILE(DD1) COUNT(1)

//*****************************************************************

//*WILL SEND A MESSAGE TO THE CONSOLE IF 99.999 record found

//*****************************************************************

//CA7TRLR    EXEC PGM=SASSTRLR,

//           COND=(0,NE,IDCAMS01),

//           PARM=INACT

//SYSOUT     DD SYSOUT=Z

//SYSUDUMP   DD SYSOUT=Z

//SYSIN      DD *

/WTO,HI=YES,MSG="SSCAN MAY NOT BE ACTIVE AND BRINGING IN NEW WORK."

/WTO,HI=YES,MSG="IN CA7 ISSUE THE COMMAND SSCAN AND MAKE SURE THE"

/WTO,HI=YES,MSG="NEXT SCAN WAKE-UP = TODAYS JULIAN DATE AND THE"

/WTO,HI=YES,MSG="TIME IS WITH THE NEXT 2 HOURS. IF NOT, CONTACT"

/WTO,HI=YES,MSG="SUPPORT TO SEE WHY SSCAN IS NOT ACTIVE."

//

Thanks  @Srosenfe   now if we could just figure out a way to make this kick off when CA7 dropped or was stopped outside of an IPL...   We haven't had any problems with scan not being turned on after an ipl (it is in the instructions) but when CA7 is dropped during the week to input a fix real quick, now THAT we have had problems with....   sscan was forgotten and we had a HUGE problem one day.   No one noticed or notified anyone until about 16 hours later.

renate

Same here - we had an emergency IPL and when CA7 came back up, we didn't want schedule scan to bring new work in so it was commented out. The next weekend when we IPL'd, no SSCAN and it wasn't noticed for quite some time. What about putting it as a Repeat job that runs each hour each day? Kind of like a monitor?

Interesting that it is stated that you can't retrieve SSCAN command output from a batch BTI job, it works for me...

CA-7.023 - r11.3(    ) OPERATOR IS LOGGED ON TO TERMINAL BTERM1  AT 11:25:10 ON 16.196
16196  112510    SSCAN
CURRENT SCHEDULE SCAN VALUES :

SPAN = 0060
INCR = 0060
QUEUE DWELL = 30
REPROMPT = 00
LEAD TIME = 0000
SKELETON RETRY = 05
XPJOB RETRY = 10
REQQ IS ACTIVE
RDYQ IS ACTIVE
ABR MSGS = NO
HOLD JOBS = NO
NEXT SCAN WAKE-UP = 99999 AT 3679
NEXT SCAN PERIOD START TIME = 00000 AT 0000

SPO0-00 SSCAN FUNCTION SUCCESSFUL REQUEST COMPLETED AT 11:25:10 ON 16.196.

It does work in our shop also -

  16196  124032    SSCAN

  CURRENT SCHEDULE SCAN VALUES :

     SPAN = 0120

     INCR = 0060

     QUEUE DWELL = 30

     REPROMPT = 10

     LEAD TIME = 0000

     SKELETON RETRY = 01

     XPJOB RETRY = 00

     REQQ IS ACTIVE

     RDYQ IS ACTIVE

     ABR MSGS = NO

     HOLD JOBS = NO

     NEXT SCAN WAKE-UP = 16196 AT 1301

     NEXT SCAN PERIOD START TIME = 16196 AT 1431

SPO0-00 SSCAN FUNCTION SUCCESSFUL REQUEST COMPLETED AT 12:40:32 ON 16.1

  16196  124032    /LOGOFF

Leave it to you, Jonathan--used to be (boy do I sound OLD--OK am OLD) that there wasn't a batch format block for SSCAN--times 'they are a-changin' :-)