Skip to content

Enabling the Network Data Mover

If your shop possesses at least one remote site and you want to use Connect:Direct as the transmission vehicle, refer to member #NDM in the CMNZMF CNTL file, and do the following:

  1. Copy member #NDM from the vendor CMNZMF CNTL library into your custom CNTL library.

  2. Modify the data set name to conform to your standards for the procedure library.

  3. Create the procedure library by changing all occurrences of $/ to ./ for IEBUPDTE and submit the job. Next, modify CMN$$NDM.

  4. Copy skeleton CMN$$NDM from the delivered skeleton library and put it into your custom skeleton library. If the batch module DMBATCH cannot be found in a linklisted library, a Steplib is necessary.

  5. Further down in the skeleton is a sign on for SYSIN that reads:


    By design, &RSOWNER will not resolve. To prevent ordinary users from seeing the USERID while they browse the skeleton, you must hard code an authorized resource owner USERID outside the skeleton, as follows:

    //SYSIN     DD DISP=SHR,DSN=somnode.NDM.SIGNON <===Secured
    //          DD *
  6. You must secure the data set somnode.NDM.SIGNON from read and update, by all except Connect:Direct, ChangeMan ZMF, and your Global Administrator. The file contents (possibly a secured PDS member) should read:

    SIGNON USERID=(superid) -

    Where superid represents a real userid. The authority level of this userid must be sufficient to do the following:

    • Transmit data sets created by ChangeMan ZMF to remote sites.

    • Allocate and update ChangeMan ZMF target staging data sets at the remote site.

    • Return acknowledgment messages.


    Do not forget to use the continuation dash to get to the next line of the skeleton that describes NETMAP and so on.

As delivered, the parameter to DMBATCH reads PARM=(NNNNNNN). Essentially, this parameter implies NO to each of seven Connect:Direct internal questions.

Changing this parameter value impacts diagnostic messages, activity logging, and the chosen DDNAMES.