T4Z INIT command question gets populated with extra characters that were not typed
search cancel

T4Z INIT command question gets populated with extra characters that were not typed

book

Article ID: 410134

calendar_today

Updated On:

Products

Test4z

Issue/Introduction

Using windows terminal (command prompt) while configuring my test4z setup with command:

test4z init

When the question z/OS UNIX System Services workspace directory (does not need to exist) ... was pending, I resized my console window to be fullscreen, then entered my USS path and continued as normal.

Opening my test4z.user.config.json file, the zosWorkspacePath field was populated with vertical bars followed by the USS path entered:

"zosWorkspacePath": "| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |/{uss path}/test4z",

Resolution

The customer noted that the last line of their USS .profile banner has the same line of vertical bars. The USS shell is started and the bars are captured on the window which subsequently populates in the test4z.user.config.json file.

The vertical bars or extra characters preceding the USS path should be edited out of the test4z.user.config.json.