CSMACT usage

Question: How do I return control of an object’s schedule to CSM?

Answer: The RESET command can be used to return control of a parent and its dependents to CSM control.

When using the CSM panel, use the rese(T) line command and be sure to specify a scope of C for children. From the console or EXCP/VTAM sessions, schedule the CSMACT EXEC as follows:

CSMACT object RESET DEP

where object is the name of the CSM controlled object.

Question: I have tried to stop the MVS object when trying to bring the system down and have received this ALERT message:

I know this means that a dependent of MVS has Verify Force Down set to YES, but is there a way around this ALERT?

Answer: If you shut down the MVS object using the CSMACT EXEC using the following format:

CSMACT MVS MAEARLY DEP X

the Verify Force Down option for the MVS dependent is ignored for this execution of CSMACT. ALERT ACM705A is not issued and all of the dependents of MVS will (assuming they have been properly defined) come down.

Question: I am trying to execute CSMACT by scheduling it through a Rule. The Rule fires and CSMACT is scheduled. The problem I have is that CSMACT appears to have not affected the object specified.

The following parameters were entered:

CSMACT object UPEARLY NOREQ

Answer: CSMACT expects the first parameter passed to it to be the EXEC name. When scheduled by a Rule, CSMACT does not get the EXEC name as the first parameter because of the difference in EXEC scheduling between the Rules Processor and other EXEC submission vehicles. See the MainView AutoOPERATOR Advanced Automation Guide for more information.

To make CSMACT work properly when scheduled through the automation action panel, enter its parameters:

CSMACT CSMACT object UPEARLY NOREQ

Question: Explain how the REQ|NOREQ and DEP|NODEP parameters should be used when CSMACT is scheduled manually.

Answer: Use REQ|NOREQ whenever an UP command needs to be processed (for example, UPEARLY, UP, and so on).

Specifying REQ causes the parents of the object named in the CSMACT parameter list to be checked and, if necessary, brought up before the object named is started. NOREQ causes the check not to be performed.

Use DEP|NODEP whenever a DOWN command is to be processed (for example, DOWNEARLY, DOWN, and so on). Specifying DEP causes the children of the object named in the CSMACT parameter list to be checked and, if necessary, stopped before the object named is stopped. NODEP causes the check not to be performed.

Either DEP|NODEP or REQ|NOREQ can be used with a RESET or RESETC command. If DEP is used with a RESET|RESETC command, the named object, along with its children, is affected. If REQ is used with a RESET|RESETC command, the named object, along with its parents, is affected.

If neither DEP|NODEP nor REQ|NOREQ is specified in the CSMACT parameter list, only the named object is affected.

Question: I am trying to move an object and all of its dependents from one CSM group to another. How can I do that using CSMACT?

Answer: Do this process the same way that you would use CSMACT to move a single object from one CSM group to another. Schedule the CSMACT EXEC in the following way:

CSMACT object MOVE target_group DEP

CSM determines the names of the dependents of the object named in the CSMACT parameters. CSM then finds the first dependent that does not have an object depending upon it. This is the bottom of the dependency structure and CSM stops that object. When the object is down, CSM stops the parent of that object (and so on) until reaching the object named in the parameters.