dcstart [-ngU]

The dcstart command starts OpenTP1 normally or restarts OpenTP1 in the computer.

-n

Specifies that OpenTP1 is to be started normally, regardless of the previous termination mode.

When this option is omitted, the startup mode is determined from the previous termination mode. If the previous termination mode was normal termination, OpenTP1 is started normally; otherwise, OpenTP1 is restarted in order to inherit the previous processing status.

-g

Suppresses inquiries to the operator in the event of failure to start a user server or forced normal startup of OpenTP1.

-U

If you specify this option, the user server is not started when rerunning OpenTP1. Use this option to recover the OpenTP1 in which an error occurred by keeping OpenTP1 in the online mode without starting the user server.

You can also use this option to start OpenTP1 in the standby system in the system switchover configuration. By using this option, you can use OpenTP1 in the standby system for postprocessing, such as determination of undecided transactions and management of the integrity of the database for OpenTP1 in the running system. For details about starting OpenTP1 in the standby system by using this option, see the manual OpenTP1 Description.

• The -g option must be specified when executing the dcstart command in the background.
• Note the following when using the dcstart -U option:
  
  • -U is ignored for normal startup.
  • This option's specification at the archive-journal target node is ignored.
  • Use the dcsvstart command to start the user server by this option after starting the online operation.
  • If you want to recover the user server configuration by this option after starting the online operation, shut down the system by means other than normal termination and forced normal termination and then start the online operation by the dcstart command without the -U option specified.
  • If any messages remain in the disk queue ITQ when rerunning OpenTP1, the messages are discarded because the AP is not started. At this time, the AP which processes ERREVT2 is also not started, so ERREVT2 is not reported. This is the same when the application program is started on the user server and the messages remain in the disk queue ITQ or OTQ.
  • If you specify this option when rerunning OpenTP1 after using the remote API facility at the previous online operation, the remote API configuration is not recovered. If you want to use the remote API facility after specifying this option, start the online operation and then start the RAP-processing listener manually by the dcsvstart command. Alternatively, shut down the system by means other than normal termination or forced normal termination and then start the online operation by the dcstart command without the -U option specified.
  • The communication event processing SPP for the client/server mode communication using OSI TP is assumed as a UAP. If you use this facility when the communication event processing SSP is set to start at the start of OpenTP1, the communication event processing SPP does not start so that the association fault detection or reconnection cannot be done. To avoid this, be sure to start the communication event processing SPP after starting OpenTP1 by the -U option.
  • Use of the server shutdown inheritance facility causes the following problems:
  1. The schedule shutdown status is not inherited in the online operation which is rerun by dcstart -U.
  2. If an SPP in the schedule shutdown status exists and you perform planned shutdown or forced shutdown of the online operation which was rerun by dcstart -U and you use dcstart to restart the online operation, the schedule shutdown status in the previous online operation before using dcstart -U is inherited. To avoid this, take the following countermeasures:
     - Perform the normal shutdown or forced normal startup of the online operation which was rerun by dcstart -U.
     - Specify set hold_recovery=N in all the user service definitions.
     - Specify set scd_hold_recovery_count=0 in the scheduling service definition.
     - OpenTP1 may terminate abnormally if you use an OS command to forcibly stop the dcstart command.
     
• When the dcstart command is used to start OpenTP1, the process server is notified that OpenTP1 has started. If the notification fails, the dcstart command automatically retries notification.
  When you use the function for retrying startup notification, the command outputs a KFCA01801-E message or a KFCA01861-E message if the notification fails and the command retries notification.
  For details about the definition for retrying startup notification, see the manual OpenTP1 System Definition.
  
• The following messages may be output when you use the dcstart command to start OpenTP1:
  
  • KFCA01801-E (Cause: SETUP or PAUSE)
  • KFCA01861-E (Cause: COMMUNICATION or TIMEOUT)
  If this occurs, take the following action:
  
  • Execute the dcstart command again.
  • Specify the retry count and retry interval for OpenTP1 startup in the dcstart_wakeup_retry_count and dcstart_wakeup_retry_interval operands, respectively, in the system common definition.