See Naming the Plan for information on how a plan name is created as a result of an application program.
When a source member is created and executed, CA Datacom Datadictionary creates and deletes a plan for that member during the execution. If the execution of the member is successful, the plan is deleted. If you execute the source member again, CA Datacom Datadictionary creates and deletes a new plan for that member.
The name for the plan is formed by concatenating the character string SQLD with the four-byte terminal ID. For example, if the terminal ID is WXYZ, the plan name for a source member executed by the user is SQLDWXYZ.
In certain circumstances, the plan for a source member may not be automatically deleted. For example, if the CA Datacom/DB MUF terminates abnormally while a source member is executing, there is a possibility of the plan not being deleted.
An automatic plan deletion can also fail when CA Datacom Datadictionary issues an internal command to delete the plan. In this case, a message specifying that the command failed is displayed on the output panel after the line stating NUMBER OF INPUT RECORDS READ IS.
If you attempt to execute a source member and receive the message PLAN ALREADY EXISTS, the automatic plan delete failed after a previous execution. You must delete the plan before you can execute the source member.
You can display an index report of PLAN occurrences using the Entity Display (ENTDISPL) Mode of CA Datacom Datadictionary or the display plan command in the SQLADMIN mode. See the CA Datacom Datadictionary Online Reference Guide or CA Datacom Datadictionary User Guide. Also, you can produce an index report for the PLAN entity-type using CA Datacom Datadictionary batch reporting. See the CA Datacom Datadictionary Batch Reference Guide. If the name of any PLAN occurrences in the index report begins with SQLD, the automatic deletion of online plans did not take place and the plan must be manually deleted.
|
Copyright © 2014 CA.
All rights reserved.
|
|