Re: Why would the existance of a home directory , /home/xxx , change the default path on a CPYTOIMPF of a job run by xxx

On 03-Nov-2015 08:47 -0600, Steinmetz, Paul wrote:

Yesterday, I added a home directory for user xxx to resolve a SFTP
issue/error:
Could not create directory '/home/xxx/.ssh'.

Today, a different non SFTP job run under same user xxx had
CPYTOIMPF fail.
For unknown reasons, /home/xxx was automatically prefixed to the
dest path.

Why would the existence of /home/xxx change the default path of a
job run by xxx.

The Home Directory (HOMEDIR) parameter of the User Profile (USRPRF) is used to establish the Current Directory (CD) for IFS naming. Per the HOMEDIR help text, "If the home directory specified does not exist when the user signs on, the user's initial working directory is the root (/) directory." Since the creation of the /home/xxx, the user's initial working directory [the CD] has been established as the /home/xxx directory rather than previously being established as '/'.

So unless the To Stream File (TOSTMF) specification had made use of an _absolute path_ vs a _relative path_, the location for creation of the named file is variable; i.e. will be placed in whatever is the CD, because a relative path specification is treated as if the './' were the explicitly specified prefix, and the period-slash serves as an effective place-holder\replacement-variable for whatever is the CD.

Thus for a specification of TOSTMF('tmp/output'), prior to the creation of the HOMEDIR, the effect would have been to create the stream file /TMP/OUTPUT whereas after the creation of the HOMEDIR, the effect would have been to create the stream file /HOME/XXX/TMP/OUTPUT