Working Directories Are Not Being Created
I have two servers defined - one each for two physical machines. Depending upon an environmental variable choice that the user makes, the job needs to specifically go to either one server or the other. I accomplish this using the .bset command. The trouble is that if the job starts on the first server (as the default), which then switches the job to the second server, the working directories (from the tag definition) are being created only on the first server. Shouldn't the working directory also be created on the second server? I'm using 7.1.2.
Thanks,
John Bobinyec
Thanks,
John Bobinyec
3 answers
In this case, you're either going to need to only use files in a shared file system (network drive on Windows, NFS mount on Unix), or set the sticky option to sticky in the project definition.
I see how the shared file system would work. I don't understand how "sticky" would solve the problem. The transfer of the job from one server to another is necessary. What doesn't happen when the job transfers is the creation of the working directories on the target server.
Thanks,
John Bobinyec
If you have the sticky option set for a project, it will force all the steps of the project that use the default project server to stay on the same server, and to wait for it to become available if it is busy. That sounds like what you are trying to do here.
From the descriptions in this thread and the other one, it sounds like you need to figure out upon which server the job needs to run, use .bset selector to set the selector. The directories need to be created in a job step that runs after the .bset selector. With the project set to sticky, this should force it to use one server for the rest of the job steps, as long as you have them all set to the default selector. In this case, the directory creation would always be on the same server that does the subsequent processing.
From the descriptions in this thread and the other one, it sounds like you need to figure out upon which server the job needs to run, use .bset selector to set the selector. The directories need to be created in a job step that runs after the .bset selector. With the project set to sticky, this should force it to use one server for the rest of the job steps, as long as you have them all set to the default selector. In this case, the directory creation would always be on the same server that does the subsequent processing.