You can invoke a development tool under TCF from any of the following locations:
It is important to invoke tools using the task code defined for use under TCF at system generation time. For a list of sample task codes associated with specific product codes, see the product and task code table in SWITCH. For example, specify the task code defined for ADSC under TCF (such as ADSCT) to invoke ADSC directly from DC/UCF.
Select a task code from the Selection Screen by typing a nonblank character in front of the task code name (even if the task code is a function key name).
For example, if SSCT is the task code for the online subschema compiler under TCF, invoke the subschema compiler by selecting SSCT from the list of task codes on the Selection Screen. For more information about the Selection Screen, see TCF Selection Screen.
For example, use the SWITCH command in online IDD to transfer from IDD to ADSC. For more information about transferring from specific tools under TCF, see Development Tools under TCF.
When you invoke a development tool under TCF, you can request to do the following:
For example, start a new session of MAPC to define a new map. TCF handles a request to start a new development tool session as described in the table that follows.
For example, resume a suspended ADSC session to continue working on the dialog being defined in the requested ADSC session.
TCF handles your request to start a new development tool session based on the number of simultaneous sessions you can have for the requested tool.
|
Development tool |
TCF response when you request a new development tool session |
|---|---|
|
Because you can have two or more simultaneous sessions of each of these tools, TCF starts a new session of the requested tool. |
|
Because you can have only one session at a time of each of these tools, TCF:
|
|
Because you can have only one session at a time of each of these tools, TCF restarts a session using retained signon and table information. |
|
Copyright © 2014 CA.
All rights reserved.
|
|