Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Customizing OSPI EXECs

The first step in automating a function using OSPI is to use the Scripting application to record the appropriate interactions with a VTAM application in an EXEC.

The generated EXEC will contain only OSPI IMFEXEC commands. It will not contain any conditional logic or other commands.

Depending upon the function being implemented, you might need to further customize the generated EXEC by combining the appropriate logic and commands with the OSPI IMFEXEC commands. This section provides customization information in the following areas:

The following REXX code is an example where an OSPI EXEC logs onto TSO, accesses SDSF and the log, exits SDSF and the log, and then logs off of TSO:

/* THIS REXX EXEC WAS GENERATED BY OSPI ONLINE */                  
ADDRESS IMFEXEC                                                    
IMFEXEC LOGON 'APPLID(BTSOB) LOGMODE(D6327802)'                    
IMFEXEC VGET OSISESS LOCAL                                         
IMFEXEC TYPE 'SESSION('OSISESS') COL(27) ROW( 1) TEXT('baodym5')'  
IMFEXEC TYPE 'SESSION('OSISESS') COL( 8) ROW( 2) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(20) ROW( 8) TEXT('TEST')'   
IMFEXEC TYPE 'SESSION('OSISESS') COL(26) ROW( 8) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL( 6) ROW(20) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(14) ROW( 4) TEXT('sdsf')'     
IMFEXEC TYPE 'SESSION('OSISESS') COL(18) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(21) ROW( 4) TEXT('log')'      
IMFEXEC TYPE 'SESSION('OSISESS') COL(24) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(21) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(21) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') PF3  '                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(21) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') PF3  '                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(14) ROW( 4) TEXT('x')'        
IMFEXEC TYPE 'SESSION('OSISESS') COL(15) ROW( 4) '                 
IMFEXEC TRANSMIT 'SESSION('OSISESS') ENTER'                        
IMFEXEC TYPE 'SESSION('OSISESS') COL(26) ROW( 5) TEXT('3')'        
IMFEXEC TYPE 'SESSION('OSISESS') COL(26) ROW(11) '

Note

This section discusses the OSPI IMFEXEC statements in general terms. See Using-the-IMFEXEC-statements for information about specific parameters, return codes, and so on.

Related topic

Interacting-with-VTAM-applications-with-OSPI

 

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