How to add KEYRINGFILE to START command.

Answer

First of all, to support TCP/IP connectivity to use SSL, you will need to update your INPRO dataset. For example,

TRANSMIT AUTOSTART(N) AUTOEND(N) RECOVERY(S) COMMTYPE(T);
SSL ENABLESSL(Y);
TCPCOMM IETCPHOST1(nnn.nnn.nn.nn) IETCPPORT1(nnnn);

Since INMSG is dynamically generated by WDI, it cannot be changed manually. In other words, WDI will overlay whatever is in the file prior to execution. Currently, the only START parameters supported by WDI are: ACCOUNT, USERID, IEPASSWORD and NIEPASSWORD. Although it is possible to add constants or new parameters to the network commands via editing specific profiles within WDI, be aware that Network command profiles are provided with the product; therefore, any changes will not be carried forward into new releases.

Instructions for adding a static constant (KEYRINGFILE) to your Network Commands:

Note: this first solution pertains to those who use the same KEYRINGFILE for all mailboxes. If you need to specify a different KEYRINGFILE for each mailbox, then follow the instructions below, "Instructions for adding a dynamic (KEYRINGFILE) to your Network Commands."

• Determine what Network ID is being used by checking the Mailbox profile as specified in the REQID keyword in your PERFORM SEND or PERFORM RECEIVE command.

• From WDI Client, click on the "Adapters" button, then click on the tab labeled "Network Profiles". Open the applicable network id and add "POSIX(ON)/" (omit the quotes) to the Network Parameters field.

• From WDI Client, click on the "Adapters" button, then click on the tab labeled "Network Commands".

• You will see these are sorted by Network ID.

• Assuming IINB41, for example, scroll down to a set of Network commands named SESSIONS (this stands for session start). Then find the one for sequence "2 3". See image below:
  

• Edit this by inserting the constant KEYRINGFILE string after the ")" and before the ";". Be sure to adjust the "Length" field accordingly. You can add up to 56 more bytes of data. See updated profile below:
  

Instructions for adding a dynamic (KEYRINGFILE) to your Network Commands to use for each mailbox:

Note: this solution pertains to those who require a different KEYRINGFILE for each mailbox.

• Determine the Mailbox profile as specified in the REQID keyword in your PERFORM SEND or PERFORM RECEIVE command.

• From WDI Client, click on the "Setup" button, then click on the tab labeled "Mailboxes".

• Enter the specific KEYRINGFILE for each mailbox. Use "Alternate Dial Number" field to specify the KEYRINGFILE value where "nnnnnnnnnnnnnnnn" is your specific value for this mailbox. The contents of this field is limited to 32 bytes.

• Determine what Network ID is being used by checking the Mailbox profile as specified in the REQID keyword in your PERFORM SEND or PERFORM RECEIVE command.

• From WDI Client, click on the "Adapters" button, then click on the tab labeled "Network Profiles". Open the applicable network id and add "POSIX(ON)/" (omit the quotes) to the Network Parameters field.

• Using WDI Client, import the attached Network commands as appropriate for the network you are using:

If your network ID is IINB41, import the attachment IINB41_alt_dial.eif


If your network ID is IINB42, import the attachment IINB42_alt_dial.eif


Note: It is important to import all three profiles as provided in each of the above attachments.

General note: According to the Expedite Base/MVS v4.6 documentation, you can use the IDENTIFY command to supply the KEYRINGFILE parameter. However, IDENTIFY is not valid when AUTOSTART is "N". Since WDI requires AUTOSTART(N) this is not a viable option.