Skip to Content
Information
End of support This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Conducting simulation testing

The MainView SRM AUTOJCL view has a line command of BSE (Build Skeleton JCL and Edit).

If you invoke the BSE command against a member in the AUTOJCL view, skeleton tailoring is invoked for that member and the result is displayed in an ISPF edit session. If you enter the AUTOJCL view directly (meaning that the view is not displayed as a result of tagging action) and you enter the BSE command, the variables in the member are replaced with simulated values (for example, MYVOL for &VOLSER, MYDSN for &DSN, and so on). You can use this process to verify that the expected results of the tailoring process are received and that the coded variables are valid.

The BSE command process creates a data set by using the high-level qualifier code in the AUTOJ_OINDX parameter in the SMMSYSxx member and a suffix of AUTOJCL appended with a date and time. The data set is deleted after the edit session is exited. If you want to keep the data set you can issue the BSK command instead of the BSE command. The BSK command executes the same process as the BSE command but does not delete the data set when the edit session is exited.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView SRM Enterprise Storage Automation 7.9