I think i need to clarify further because from my understanding, that procedure is not what i am trying to do.
I have a procedure where i want to have the users provide a structured list of data, that is stored centrally in the Depot, and the NSH scriptJob can read this data as input to complete tasks directly from the Depot. I want to try to avoid moving copies to /tmp or anything like this, as my assumption is that i should be able to access a "File" stored on the file server and read the data contained and not have to create overhead by transferring it to systems.
I understand that in the fileserver creates a reference path on the filesystem for Depot objects as they are actually stored in the database, but since i am able to "cat" the file from an NSH session, i assumed i can do the same in an NSH scriptJob. So this is the end goal i am trying to achieve.
Hope this clarifies.
what's the problem w/ using a nsh script object for this instead of a depot file ?