Space banner


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Distributed automated solutions

Solutions distributed by BMC can encompass FLST/RLST statements, SMEVNTxx definitions, MainView AutoOPERATOR Rules in Rule Sets, and skeleton JCL members. Some solutions might simply issue events, while other solutions might use job submission or MainView AutoOPERATOR Rules to perform their process.

Multilevel solutions (described in Multilevel automation (MLA) processing) use several of the individual distributed solutions. You can issue the invocation command for these solutions through the operator console or through a MainView AutoOPERATOR Rule that is fired on a timed interval.

Best Practice

Because of varying definitions within each solution, BMC recommends reading the supplied documentation for all solutions, even if you do not plan to implement some solutions.

These distributed solutions might not meet the goals of your data center and, therefore, might require customization. Before implementing any distributed solution, review the FLST/RLST selection criteria and the SET keywords. Also, check the content of the JCL statements for the batch jobs and the content of the MainView AutoOPERATOR Rules.

When creating and implementing solutions, note that it might not be appropriate to run certain solutions simultaneously or during certain times of the day, depending on the operations of your data center.

You also must understand your goals for using automated solutions and how to create or modify solutions to meet those goals. With knowledge of the operation of your data center, you can devise a plan for the implementation of those solutions.

Libraries for the distributed solutions

Library members that are used in the distributed solutions are copied into your production libraries during the customization step of the installation process.

The following table specifies where you can find these members.

Library members


Distributed to this library

Copied to this library

View for element

Function definitions

FLST/RLST definitions




(used to browse, edit, and refresh the FLST/RLST)

MainView AutoOPERATOR Rules


MainView AutoOPERATOR ?prefix.UBBPARM

See the MainView AutoOPERATOR Basic Automation Guide.

Skeleton JCL




(used to edit and browse BBSLIB members)





(used to browse, edit, and refresh the SMEVNTxx member)

Viewing functionality without JCL submission

Some of the distributed solutions use the ACT_JOB keyword to submit skeleton JCL.

The ACT_EVENTID keyword is also coded as a comment line in the RLST of these solutions. A matching event is coded in the SMEVNT00 member. The ACT_EVENTID keyword can be used in place of the ACT_JOB keyword to cause event generation rather than job submission. Using the ACT_EVENTID keyword and then installing and activating MainView AutoOPERATOR Rule Set RULSRS02, you can view the results of the solution in the MainView AutoOPERATOR Journal display without any action being taken against any resource.

All MainView SRM Automation distributed Rule Sets are in a disabled status when MainView AutoOPERATOR is started. To have these Rule Sets be enabled automatically when MainView AutoOPERATOR is started, add them to the Rule Set parameter in MainView AutoOPERATOR ?prefix.UBBPARM (AAOPRM00). All Rules in the distributed Rule Sets are defined as enabled.

Testing distributed skeleton JCL

The distributed skeleton JCL contains a generic JOB card that needs to be customized for your environment.

The control card statements and DD statements have been commented out in the JCL. Using the JCL this way allows for variable substitution to take place in the skeleton JCL, the submission of the batch job, and allows the job to run to completion while no action is taken against any resource. The output of the job can then be viewed to verify the expected results.

Another method to test the results of the variable substitution is by using TYPRUN=HOLD on the JOB card (also provided in the distributed JCL as a comment line). This method allows the variable substitution to take place and the submission of the job. The results can be viewed using the SDSF input view. You will have to issue the INPUT ON command in SDSF to view the SYSIN control statements. You will also need to have cancel authority to purge the job.


When TYPRUN=SCAN is used in skeleton JCL, SVESA will be unable to determine when the job ends. In this situation, the JobEnd line command on the AUTOSJOB view can be used to mark the job as completed.

For information about the distributed solutions, see the following items:

Was this page helpful? Yes No Submitting... Thank you