When you created a server message for an OS 2200 TIP Data Source, you specified the message direction as follows:
If you always use the message to send data from the client to the OS 2200 server, you selected Input.
If you always use this message to receive data from the OS 2200 server, you selected Output.
If the message might be used to both send and receive data, you selected Both Input and Output.
If you selected Input or Both Input and Output for the message direction, then you had the option of providing a value for the TIP transaction code. Refer to OS 2200 COBOL Data Source Wizard and DPS Import Form Library Dialog.
As described in Metadata Fields, the server message includes a metadata field named tiptrancode__ to represent the TIP transaction code as configured in the VALTAB on the OS 2200 server. This field has the following property settings:
If you provided a value for the TIP transaction code during import:
InitialValue is set to the transaction code.
Visible is set to False.
If you did not provide a value for the TIP transaction code during import:
InitialValue is empty.
Visible is set to True.
Note: By default, these settings automatically propagate to the corresponding client message as well. Refer to the properties AutoCreateClient and AutoRecreateClient in Message Editor Root Node Properties.
The InitialValue property represents the initial value for the field. For a Web page presentation, the Visible property controls whether the Web page contains a control for the field or not. For a Web service presentation, the Visible property controls whether the field is included as a parameter for the Web method or not.
If you need to set or update the transaction code after the import, perform the following procedure to set the transaction code:
In the ePortal Message View window, expand the Server Messages folder, right-click the server message to be modified, and click Edit. The server message appears in the <server message name>.eprec tab.
Click on the field tiptrancode__ to select it.
Press Alt-Enter to open the property window to see the field properties.
Enter the new transaction code for the InitialValue property. Make sure the Visible property is False.
Click Save from the File menu to save the changes.
If the property AutoRecreateClient is False, repeat steps 1-5 above for the corresponding client message.
If you want to specify the transaction code at runtime rather than at design time, perform the following procedure:
In the ePortal Message View window, expand the Server Messages folder, right-click the server message to be modified, and click Edit. The server message appears in the <server message name>.eprec tab.
Click on the field tiptrancode__ to select it.
Press Alt-Enter to open the property window to see the field properties.
Set the Visible property is True. After a project build, this will cause this field to appear in the presentation so that it can be set at runtime.
You can set InitialValue to a default value if you like, or you can leave this blank.
Click Save from the File menu to save the changes.
If the property AutoRecreateClient is False, repeat steps 1-6 above for the corresponding client message.