Exspans Systems Inc Logo home
 
Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #1 
AutoMan V3.2 streamlines processes and now handles system support subsystems as single units of work that can be be controlled in correct sequence of pre and post requisite considerations.

There are new GAL instructions to handle reconfiguration simply and easily.

You can request some manuals from http://www.exspans.ca/
0
Zamin

Avatar / Picture

Member
Registered:
Posts: 67
Reply with quote  #2 
I don't want to scan thru a whole manual. can you give specific examples?
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #3 
Configurations are in a state, either, down, up, in progress etc. If you defined a configuration for JES2 which referenced the things than must be down before JES can be stopped, you can reduce the startup and shut down of JES2 and its dependencies to a single command.

>CHANGE CONFIG(JES2)=DOWN
>CHANGE CONFIG(JES2)=UP

JES is started very early in the system loading process. It is needed to run jobs and start some subtasks. Some subsystems use JES hooks and must be down before JES is down. That statement to request a state change references a Configuration named JES2. Config JES2 is defined in the configs parameter member. 

CONFIG=JES2
     TIMEOUT=9000
     INTERVAL=300
     ONFAIL=ABANDON
     STATE=UP
        SSIDLIST(UP)=(JES2)
        CONFIGLIST(UP)=(BASIC,MONITOR)
     STATE=DOWN
        SSIDLIST(DOWN)=(JES2)
        CONFIGLIST(DOWN)=(NETWORK,MONITOR)
    PREREQ(UP) SSID(JES2)
        UP=(LLA,VLF)
    PREREQ(DOWN) SSID(JES2)
       DOWN=(NET,OMVS,TCPIP)
0
Zamin

Avatar / Picture

Member
Registered:
Posts: 67
Reply with quote  #4 
On the CHANGE command what is that sideways caret for?

On the definition of configuration JES2 you have shown what do the parameters mean?
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #5 
>CHANGE CONFIG(JES2)=UP

The sideways caret is a symbol to indicate that the command is executed by AutoMan directly, not by the system command handlers. This command is a GAL construct which can be issued inside any GAL code. A character string is defined in the startup parameters which may be entered at the console to direct the command to AutoMan.

So you can enter it at the console as shown with the caret or do something like this in GAL code.

IF CONFIG(JES2) = DOWN DO
 
  CHANGE CONFIG(JES2)=UP
END


The CONFiG statement is quite straightforward when you divide it into sections. It defines simple rules which must be true for the configuration to be in the desired state. It can refer to other subsystems and other configurations to determine its state.


CONFIG=JES2                                /* Configuration name                       */
     TIMEOUT=9000
                          /* If it does not change state in 90s fail  */    
     INTERVAL=300                          /* when changing state check every 3s       */
     ONFAIL=ABANDON                        /* if it fails do not auto retry            */
     STATE=UP                              /* To be in UP state, this must be true     */
        SSIDLIST(UP)=(JES2)                /* Subsys JES2 must be UP                   */
        CONFIGLIST(UP)=(BASIC,MONITOR)     /* 2 other configs must also be UP          */
     STATE=DOWN                            /* To be in DOWN state this must be true    */
        SSIDLIST(DOWN)=(JES2)              /* Subsys JES2 must be down                 */
        CONFIGLIST(DOWN)=(NETWORK,MONITOR) /* these JES dependent configs must be down */
    PREREQ(UP) SSID(JES2)                  /* Prereq. Before JES2 can go into UP state */
        UP=(LLA,VLF)                       /* LLA and VLF must be UP                   */
    PREREQ(DOWN) SSID(JES2)                /* Prereq. Before JES2 can start into DOWN  */                
       DOWN=(NET,OMVS,TCPIP)               /* state, NET, OMVS and TCPIP must be down  */
0
Grazillda

Avatar / Picture

Member
Registered:
Posts: 48
Reply with quote  #6 
You should start a topic on configurations. We use the basic system initialization from the tool kit to get the system booted far enough to log on to TSO. We use that on every test and development system. What we want to do is start about another 45 subsystems hierarchically, so that we can take systems offline at different times of day, and bring them back at others.
0
Grazillda

Avatar / Picture

Member
Registered:
Posts: 48
Reply with quote  #7 
So I have completed my install of AutoMan V3.2. That was a snap. We took the CONFIG option and using the examples for a standard operating environment. We only had to create a couple SSIDs and a couple CONFIGs and we have a self starting, self monitoring system. We have a single Command List running that checks the state of all the services that we critically, and makes sure they are always running. When we IPL the only thing AutoMan does is dispatch this command list as a task. It checks the status of the system CONFIG and if it is not up, it enables the startup process. When we want to shut the system down we used the example in the tips and techniques manual to intercept the word "shutdown" at the operator command interface and signal the shut down procedure. This sets a global variable, which is examined by the command list task. It displays a WTOR asking for confirmation of shutdown. If shut down is confirmed a message is displayed and the system CONFIG is changed to DOWN. The logical structures that you can build with GAL are amazing. You have complete freedom to start subtasks and interact between them.
0
automan

Avatar / Picture

Moderator
Registered:
Posts: 136
Reply with quote  #8 
I am glad you are learning the power of GAL.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!