PI60022: SCRIPT BODY TEXT ${LIBPATH} IN FILE UTILS STEP CREATE FILE IS RESOLVED TO A VALUE INSTEAD OF BEING IGNORED

IBM UrbanCode Deploy 6.2.4

APAR status

• Closed as Permanent restriction.

Error description

• ${LIBPATH} will always be resolved to what the environment
  Libpath specifies. The script body text ${LIBPATH} in File Utils
  step Create File is resolved to a value instead of being
  ignored.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * users on a linux system using a LIB_PATH environment         *
  * variable                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ${LIBPATH} in ucd scripts resolves to the enviornment        *
  * libpath instead of the linux libpath without a replace token *
  * step.                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• There is a workaround in Deploy using the replace tokens step to
  put in the actual lib_path
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels