Error during the installation of eTrust DSI: 550 CWD cmd failed: EDC5129i No such file or directory.

Document ID : KB000055529
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

  1. During the installation, the following information is requested by the install process:

    IP Address/Name: 
    Admin ID: 
    Admin Pswd: 
    HFS Directory:/usr/lpp/etldapv3
    ProcLib:SYS1.PROCLIB
    ProcName:SECV3

  2. The first three parameters are filled out appropriately and the last three are left to the default values.

  3. Then the following FTP error is generated:

    550 CWD cmd failed: EDC5129i No such file or directory.

Cause:

Usually this issue is due to the default HFS Directory does not exist on the mainframe.

Some eTrust Admin customers suspect the eTrust DSI installation will create and mount an HFS file system for secv3 during the installation procedure, but actually the HFS Directory should be manually created on mainframe before running eTrust DSI installation. This is a prerequisite task on mainframe, this task should normally be performed by a mainframe administrator.

Effectively the default HFS Directory - '/usr/lpp/etldapv3' would not be used.

This document describes how to solve the problem and finish the installation HFS file system.

z/OS UNIX provides a Hierarchical File System (HFS) for MVS. A file within z/OS UNIX is called an HFS file. HFS files are organized in a hierarchy of files and directories in a tree much like UNIX. A directory can contain files or other subdirectories.

Solution:

Please go through the steps below on the mainframe with the assistance of a mainframe administrator

  1. Ensure you have created an STC user that will run the eTrust DSI server. (Usually the user id would be 'secv3') If the user account was not previously c r e ated on the mainframe, p lease request a mainframe administrator to create it.

  2. Find out the STC user's HFS Directory on mainframe.

  3. Grant r/w access to the 'Admin ID' above as files need to be uploaded to the STC user's HFS Directory on the mainframe.

Additional information:

  1. The 'Admin ID' is just used during eTrust DSI installation, it should get UID(0)

  2. The STC user - 'secv3' is for starting eTrust DSI server after the installation

  3. The 'HFS Directory' is the HFS Directory for 'secv3'

  4. As 3, all eTrust DSI files should be uploaded into the HFS Directory . As a consequence, you need grant r/w to the installer - 'Admin ID' on the HFS directory of 'secv3'