Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Operating ROBAR-CL

ROBAR-CL on a BS2000 system consists of the DCAM application ROBAR-CL-DCAM and the user program ROBAR-CL-SDF, which are operated separately.

Starting ROBAR-CL-DCAM

Configure ROBAR-CL before starting ROBAR-CL-DCAM for the first time, see section "Configuring ROBAR-CL". Also ensure by means of the SHOW-MESSAGE-SUPPRESSION command that output of the messages NBR0740 and EXC0031 is not suppressed (by means of the SET-MESSAGE-SUPPRESSION command).

ROBAR-CL-DCAM is started by means of the SYSPRC.ROBAR-CL.<ver> start procedure (see "Modifying the start file for ROBAR-CL-DCAM") using /ENTER-PROCEDURE or /CALL-PROCEDURE.
Start ROBAR-CL-DCAM on every BS2000 system that wants to communicate with ROBAR-SV (and therefore with an archive system).
If a BS2000 system is to work with several ROBAR-SV instances (and therefore with several archive systems), ROBAR-CL-DCAM must be started the corresponding number of times.

You can monitor the status of the connection between ROBAR-CL-DCAM and ROBAR-SV by means of a job variable which you can define in the ROBAR-CL-DCAM start procedure (JV-NAME parameter). The job variable indicates whether the connection between the BS2000 system and ROBAR-SV is functioning or whether it has been interrupted. The precise content of the job variable is contained in the installation file SYSPAR.ROBAR-CL.<ver>.TEXT.D or E, see "Installing ROBAR-CL". This function is available if you are using the JV software product (see the “Job Variables” manual [7]).

If you are using MAREN, you must start the start procedure in an environment in which the MARENADM program can also run. This means in particular that

  • Disclose the MAREN password in the start procedure (see "Modifying the start file for ROBAR-CL-DCAM").

  • The user ID under which the start procedure is started must be able to access the MAREN syntax files.

  • The user ID under which the start procedure is started must have the system privilege TAPE-ADMINISTRATION if the software product SECOS is in use.

Terminating ROBAR-CL-DCAM

You should terminate the ROBAR-CL-DCAM application that was started via the ENTER job by entering the /BCAPPL command (see the “BCAM” manual [1]):

/BCAPPL APPLICATION=<application_name>

        [,MODE=DEACTIVATE,TYPE=NORMAL,W=YES]

This command must be called with its default values.The <application_name> was defined as parameter PARTNER in the start procedure, see "Modifying the start file for ROBAR-CL-DCAM".

 

Starting ROBAR-CL-SDF

The ROBAR-CL-SDF user program is called via /START-ROBAR or /ROBAR.

ROBAR-CL-SDF supports the SPIN-OFF mechanism, see section "ROBAR-CL-SDF supports the SPIN-OFF mechanism" in chapter "ROBAR-CL-SDF statements".
Some statements of ROBAR-CL-SDF can only be used for particular archive systems, see section "ROBAR-CL-SDF statements".

Terminating ROBAR-CL-SDF

The ROBAR-CL-SDF user program is terminated with the statement END.