BF Agent on Z/Os
The Build Forge agent has been installed on the Z/os Platform following the install steps in the BF documentation. I am able to telnet into the mainframe system using the BF port successfully. I also get the BF Agent message when hitting the agent.
When using the BF console to run a simple tso command, I get the below error. Are there any security related steps that has to be followed post BF agent install on the mainframe ? Has anybody successfully tested BF agents on the mainframe. Help is much appreciated. Error Message ------------------ Unable to set working directory to 'userid.BF.LOG' The server definition on build forge (pointing at the mainframe system) has userid.BF.log as the working directory. |
4 answers
the first thing that the job tries to do is change to that directory and then execute a mkdir() to create the working directory for the project to run. It will make the job name directory and the tag name directory, but the parent to that (the server object "Path" field) needs to exist first.
|
the first thing that the job tries to do is change to that directory and then execute a mkdir() to create the working directory for the project to run. It will make the job name directory and the tag name directory, but the parent to that (the server object "Path" field) needs to exist first. We have ensured the flat file exists on the system. We have tried using a PDS (directory kind of structure in distributed world) and a flat file. Get the same error in-spite of the file existing on the mainframe system. Also tried changing the step to run as absolute and relative. Get the same error. |
It sounds like the Build Forge agent is trying to change to an HFS directory specified by that configuration option as a part of the first processing it is performing on the z/OS system.
I suggest trying this: 1) assuming the userid is "user1" and users on that z/OS system have their home directories in HFS under "/home", then create a directory "/home/user1/buildforge-logs" in the HFS and make sure that "user1" has 777 permissions on that directory. 2) change the configuration in Build Forge to specify "/home/user1/buildforge-logs" as the starting directory ("Path" field). Now try and run the test again. |
|
We changed the server home directory to /tmp which seems to have fixed the issue. The user id does have permission to the /tmp directory and also successfully kick off mainframe jobs !!
Thanks |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.