??MARC (Transfer to Menu-Assisted Resource Control)

The ??MARC (Transfer to Menu-Assisted Resource Control) command lets an ODT operate as a data comm remote terminal in an environment directed by SYSTEM/COMS and COMS/ODT/DRIVER.

Syntax

Explanation

The ??MARC command directs control of the ODT to COMS/ODT/DRIVER. The standard ODT operations become unavailable until ??ODT is entered. Refer to ??ODT (Return from Menu-Assisted Resource Control) in later in this section. After ??MARC is entered, the only primitive commands the system recognizes are ??ODT (to resume standard ODT operations), ??MEMDP (to force a system dump), and ??RESTRICT (to restrict standard ODT operations).

COMS/ODT/DRIVER always releases the ODT into MARC through the SYSTEM/COMS MCS. Refer to the Menu-Assisted Resource Control (MARC) Operations Guide  for information about MARC.

Considerations for Use

COMS/ODT/DRIVER allocates a pseudostation for each ODT under its control and handles simulation of a data comm environment. A DATACOMINFO file must be available that defines SYSTEM/COMS, COMS/ODT/DRIVER, and any other MCSs (such as SYSTEM/CANDE) that might be used. The SYSTEM/COMS MCS must be the same code file title used to establish the COMSSUPPORT system (function) library.

If the DATACOMINFO file tables have not already been loaded, some delay can occur before the ??MARC command can begin a transfer. In this case, the following message is issued: 

INITIALIZING MESSAGE CONTROL SYSTEM TABLES.

One of the following messages is issued if the ??MARC primitive command fails: 

  COMS/ODT/DRIVER HAS BEEN DSED.
   
  COMS/ODT/DRIVER IS NOT DECLARED AS AN MCS.
   
  COMSSUPPORT LIBRARY HAS NOT BEEN SL-ED.
  
  <COMSUPPORT code file name> (MCS) REQUIRED.

The following messages are issued when an ODT transfer is started because a delay can occur if the COMS/ODT/DRIVER or SYSTEM/COMS (or <MCS name>) is not running when the ??MARC primitive command is entered: 

  PRIMITIVE EXECUTED.
  SC <unit number> TRANSFER UNDERWAY.

The following messages are issued by COMS/ODT/DRIVER and appear only on the ODT for which they are intended. These messages are not seen by the CONTROLLER. 

#SC <unit> HAS NO MCS ASSIGNMENT. ENTER ??ODT TO RESUME
 AS AN ODT.

The controlling MCS of the station has terminated or the station was returned to the control of COMS/ODT/DRIVER by a log-off or direct-transfer operation. The message also appears if COMS/ODT/DRIVER accepts a <mix number> SM  :  CLEAR <ODT unit>. 

#STATION LIMIT EXCEEDED. ENTER ??ODT TO RESUME AS AN ODT.

The number of pseudostations defined for the system is less than the number of ODT units, and transferring the ODT would exceed the defined number of pseudostations. 

#UNABLE TO EFFECT MCS TRANSFER. ENTER ??ODT TO RESUME AS AN ODT.

A problem occurred during a transfer of the pseudostation to SYSTEM/COMS (or <MCS name>, if given). 

#NO PSEUDOSTATIONS COULD BE OBTAINED. ENTER ??ODT TO
 RESUME AS AN ODT.

COMS/ODT/DRIVER cannot obtain a pseudostation from the system.

COMS/ODT/DRIVER recognizes the following commands if they are entered through the <mix number>  SM command. Refer to  the SM (Send to MCS or Database) command.

Command

Description

QUIT

Lets COMS/ODT/DRIVER be terminated normally. A DCPTERMINATED result is returned to the controlling MCS of any pseudostation that was transferred.

CLEAR <ODT unit>

Causes COMS/ODT/DRIVER to immediately disconnect the pseudostation allocated for <ODT unit> from the MCS to which it has been transferred. After you enter ??ODT to resume ODT operations under the CONTROLLER, a ??MARC command starts a new transfer sequence. The ODT unit must be the unit number of an ODT that was previously switched by the ??MARC primitive command.

ODTS

Causes COMS/ODT/DRIVER to display a list of pseudostations and the corresponding owning ODT unit, followed by a list of ODT units and corresponding pseudostations (if a current assignment exists).

Prev  Up  Next
??HS (Hold Schedule)  Home  ??MEMDP (Dump Memory)