A description of each of the action items identified in the above table follows.
Add
Specifies that a new entity is being added.
Using the Add action, the developer can copy an existing entity into the current work file and give it a new name.
When the application developer specifies an entity name, the compiler ensures that no entity exists with the specified name and version number and returns the message:
DC498104 DIALOG1 was not found, use the Add action to create or copy the dialog
To request the add operation, the developer must either open the Add window by moving the cursor to the action bar, or type the word ADD on the command line.
Note: The compiler does not assume that the add operation is requested when it does not find the entity in the dictionary.
If an entity with the specified name and version number exists, the compiler assumes a modify operation and returns the following message:
DC498102 Currency set for dialog empdemo version 1
When you add an entity, you have explicitly checked it out, and no one else can access it until you check it in.
If another developer owns the entity, or if another entity type has already used the name, the following error message is issued:
DC498103 Currency not established. Dialog is currently checked out DC498107 to user MET on dictionary TESTDCT.
The following screen shows the Add window on the dialog compiler Main Menu.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ │ Copy from dialog │A ADS Online Dialog Compiler │ Name JPKD5___ │ │ Version 1 │CA, INC. │-----------------------│ │ F3=Exit │ │_______________________│ Dialog name . . . . . . . JPKD1 Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Dialog added using copy request. Command ===> Enter F1=Help F3=Exit F10=Action
Modify
Specifies that an existing entity is being modified or, if the specified entity belongs to a suspended session, that the suspended session is being resumed.
You can resume a session by filling out the entity name. MODIFY CHECKOUT is the name CA ADS gives to entities not yet checked out.
When the application developer specifies the Modify action, the compiler ensures that an entity exists with the specified name and version number and returns the message:
DC498102 Currency set for dialog empdemo version 1
If the specified entity exists, the compiler retrieves and displays the definition. When the Compile action is selected, a new load module is created for the entity.
If an entity with the specified name and version number does not exist, Modify is invalid.
If an entity is currently in use, the name of the owner is displayed. The owner can release the entity, if desired, without having to compile it and without deleting the current changes in the work file. To release an entity, the developer chooses item 2, Release, from the Modify pulldown window. Another developer can then assume control of the entity by issuing a reserve request.
To see a list of the entities checked out, the developer chooses item 3, List Checkouts.
Modify is the default for an existing dialog.
The following screen shows the Modify window on the dialog compiler Main Menu.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ │ 1 1. Checkout │ Online Dialog Compiler │ 2. Release │ │ 3. List Checkouts │A, INC. │-----------------------│ │ F3=Exit │ │_______________________│ Dialog name . . . . . . . JPKD1 Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Command ===> Enter F1=Help F3=Exit F10=Action
Compile
Specifies that the current entity is being compiled.
When the application developer specifies the Compile action, the compiler ensures that an entity exists with the specified name and version number.
If the specified entity exists, the compiler compiles the entity (including all process modules in the case of a dialog) and, if the compilation is successful, creates a load module. The load module is stored in the data dictionary.
Upon compilation, the compiler deletes any queue records saved for a suspended session of the entity definition.
If an entity with the specified name and version number does not exist, the Compile action is invalid and an error message is displayed.
If errors are encountered during the compilation process, they are written to a log file that allows scrolling access and is chosen from the Compile window.
The following screen shows the Compile action on the dialog compiler Main Menu.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ │ 1 1. Compile │ log Compiler │ 2. Display messages │ │-------------------------│ │ F3=Exit │ │_________________________│ Dialog name . . . . . . . METDLG1 Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Command ===> Enter F1=Help F3=Exit F10=Action
When errors are encountered in the compilation process, the application developer chooses item 2, Display messages, from the Compile action on the action bar. Messages on the Messages screen indicate where there are errors.
The following screen shows the Messages screen resulting from dialog compilation:
Sample Messages screen
Compiled Process Modules Page 1 of 1 Dialog METDLG01 Ver 1 Name MET-ERROR 1 Commands Version 0001 Type 2 1 Errors Key _____ Value _ 1. Display 2. Print Name ________________________________ Commands Version ____ Type _ Errors Key _____ Value _ 1. Display 2. Print Name ________________________________ Commands Version ____ Type _ Errors Key _____ Value _ 1. Display 2. Print Name ________________________________ Commands Version ____ Type _ Errors Key _____ Value _ 1. Display 2. Print Type: 1=Declaration 2=Premap 3=Response 4=Default Response Select a process for Display or Print. F1=Help F3=Exit F7=Bkwd F8=Fwd F11=Dialog-level messages 4B7 A IBM 07/62
The Messages screen displays the source statements for a premap or response process that contains errors in its process code. It also contains other messages encountered during the compilation of the dialog.
Enter 1, Display, to display a copy of the dialog process source errors.
Sample Dialog Process Source screen
Dialog Process Source Page 1 of 1 ._____________________________________________________________________________. <PROCESS> MET-ERROR 0001 100 MOBE ZNTRAIL(MYNUMBER) TO WK-PART-CODE $ <E> DC157001 INVALID INITIATING KEYWORD FOR COMMAND. STMT FLUSHED. 200 DISPLAY. .____________________________________________________________________________. Module currently displayed: MET-ERROR VERSION: 1 F3=Exit F5=IDD F7=Bkwd F8=Fwd F11=Next.error
Data dictionary sequence numbers appear to the left of the source statements. If the listed code includes another process module, the source statements from the included module are listed after the INCLUDE statement.
Process statements that are in error are flagged with a dollar sign ($), followed by a CA ADS error code and message. One erroneous process source statement can cause subsequent statements to be found in error, even if they are coded correctly.
Note: For more information about the error messages used by CA ADS, see the CA IDMS Messages and Codes Guide.
The Messages screen cannot be used to correct errors in the process source code. To correct stored process code, the application developer must use IDD. To toggle to IDD press [PF5].
Note: In order to toggle to IDD, you must be running ADSC under the CA IDMS Command Facility. For more information about the CA IDMS Command Facility, see the CA IDMS Common Facilities Guide. For more information about correcting errors in process code, see the CA ADS User Guide.
Delete
Specifies that an existing entity, or changes to an existing entity, be deleted.
When the application developer specifies the Delete dialog action from this window, the compiler ensures that an entity exists with the specified name and version number.
If the specified entity exists and the action is Delete dialog, a confirmation window is presented to the user, allowing the request to be confirmed or rescinded. If the deletion is confirmed, the compiler deletes the load module from the data dictionary, any dictionary definitions, and any queue records saved for a suspended session of the definition.
If an entity with the specified name and version number does not exist, the Delete dialog action is invalid and an error message is displayed.
The entity must not be reserved to another user if it is to be deleted.
If Delete changes has been chosen from this window, the working file is reconstructed from the most recently stored (compiled) definition.
If Delete changes is chosen, the entity remains checked out to the current developer.
The following screen shows the Delete window on the dialog compiler Main Menu. A confirmation window is displayed so that the request to delete the dialog can be confirmed or rescinded.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ │ 2 1. Delete changes │ piler │ 2. Delete dialog │ │-----------------------│ io .__________________. │ F3=Exit │ │ │ │_______________________│. │ 2 1. Confirm │ │ 2. Reject │ Dialog name . . . . . . . SOME1 │__________________│ Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Enter 1 to confirm the delete request. Command ===> Enter F1=Help F3=Exit F10=Action
Display
Specifies that summary information for the named entity be displayed.
The following screen shows the Display window on the dialog compiler Main Menu.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ CA AD │ _ 1. Browse │ er │ 2. Summary │ CA, │ 3. Map image │ │ 4. Print Sum │ │------------------│ │ F3=Exit │ Dialog name . . . . . . . │__________________│ Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Command ===> Enter F1=Help F3=Exit F10=Action
From the Display window, the developer can choose Browse or Summary. Other options available from this window depend on the compiler being used.
Browse
The Browse option allows the developer to walk through the entity definition process without changing any information about the entity. All fields on the compiler screens are protected.
If the entity is currently checked out to another developer and changes have been made but not saved, the Browse option returns the entity definition as it exists in the dictionary.
Summary
The Summary option gives an overview of the entity definition.
The following screen shows the Summary option taken from the dialog compiler Main Menu.
Dialog Summary Display Page 1 of 1 ._____________________________________________________________________________. DIALOG: PROCEMP VERSION: 1 Entry Point......: PREMAP Mainline.........: YES Symbol Table.....: YES Diagnostic Tables: NO Cobol Moves......: NO Retrieval Lock...: NO Autostatus.......: YES Message Prefix...: DC Status Rec: ADSO-STAT-DEF-REC Version: 1 Access Module: JMASQLD ANSI-flag: Date Format: Time Format: Online Map: MAP1 Version: 1 Record: SQLCA Version: 1 NC Process: USER2-PM Version: 1 Premap Process: USER1-CONTINUE Version: 1 Response Execute on error: NO Key: ENTER Value: .____________________________________________________________________________. F3=Exit F7=Bkwd F8=Fwd
Map image
The Map Image screen displays the dialog map as it appears to the user at runtime. The application developer can position the cursor at map data fields and enter information.
Map modifications defined in process code associated with the dialog are not in effect when the screen is displayed. Map data fields do not contain any values on the Map Image screen.
Hit any key to return to the menu screen.
Print Sum
The Print Sum option prints a copy of the Print Summary screen.
Switch
Specifies that control is to be passed to another CA IDMS/DC or DC/UCF task. Switch suspends the current dialog compilation session and transfers control to another DC/UCF task, to the transfer control facility Selection screen, or to a new or suspended session of another task.
A task code must be entered into the Task code field.
The following screen shows the Switch window on the dialog compiler Main Menu.
Add Modify Compile Delete Display Switch ._____________________________________________________________________________. │ │ CA ADS Online │ Task code ________ │ │-----------------------│ Computer Associate │ F3=Exit │ │_______________________│ Dialog name . . . . . . . JPKD1 Dialog version . . . . . 1 Dictionary name . . . . . TSTDICT Dictionary node . . . . . ________ Screen . . . . . . . . . 1 1. General options 2. Assign maps 3. Assign database 4. Assign records and tables 5. Assign process modules Command ===> Enter F1=Help F3=Exit F10=Action
|
Copyright © 2014 CA.
All rights reserved.
|
|