Moving spool files from one LPAR to another.

45 pts.
Spool files
How do I give permission to a programmer to move spool files from one LPAR (development) to another LPAR (production)? Is it a system value? Or a profile parameter? Thank you

Answer Wiki

Thanks. We'll let you know when a new response is added.

Start with their user profile authority, it should list *SPLCTL as a Special authority.
If they have that, they may not be authorized to the outq. Need a little more specific detail as to how they’re trying to access and move the spool file.


There is no authority to copy spooled files between systems. First, two systems are involved so two sets of authorities are needed, not necessarily for the same profile.

Second, authorities begin with access to the the spooled files. If the programmer created them, then s/he already has all necessary authority since owners are authorized to their own spooled files. If someone else owns them, then whatever authorities are needed to manipulate spooled files for that owner might be required. (Is the owner an *ALLOBJ profile?)

And authority might be needed to access the output queue or the output queue’s library. Or spooled files on that output queue.

Those authorities could be covered by allowing *SPLCTL, but that grants authority to <b>all spooled files</b> from every user, not just ones that might be copied to another system. Since it’s a development system, that’s probably not an issue.

Then would come potential communications obstacles. Is the programmer blocked from sending information out from the system? Is the programmer blocked on the remote system? Overcoming those would depend on the mechanism. Exit programs might be in place, and you’d have to look at their documentation for steps to open any blocks that would be in place.

Next, what method is used for the transfer? There would be three that would be common — SNDNETSPLF, SNDTCPSPLF and remote output queue.

SNDNETSPLF is the old SNADS method of transferring spooled files. The programmer would an entry in the system directory in order to start the request. There would also need to be an entry that would determine who the recipient would be on the remote system. (That might best be via a ‘generic’ entry on the source system.) The actual recipient would need to have an individual entry in the system directory on the target system, but that gets away from any ‘authority’ for the programmer.

SNDTCPSPLF is based on LPR/LPD, pretty much the same as remote output queue. If authority exists to access the spooled files, then basic object authority to the command itself is about all that’s needed. As long as the remote system has no communications block, there should be no authorities involved. The programmer doesn’t even need to be defined on the remote system.

Everything for SNDTCPSPLF goes as well for remote output queue.

Perhaps the question isn’t so much about what authority is needed, and it’s more “Why isn’t it working for us?” If that’s the case, then a description of what has been configured, what actions are being attempted and what error messages are seen would be useful. If error messages are given, the message identifiers need to be included.


Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • BCBGTina
    Thank you. She does have *SPLCTL in her user profile authority. Are you able to explain how SNDNETSPLF works with WRKDIRE?
    45 pointsBadges:
  • Whatis23
    If you want to distribute reports to another system defined LPAR, the user receiving the report must be set up in WRKDIRE to receive via SNDNETSPLF. The User ID parm is for the user profile and the Address parm is the remote system name defined in WRKDIRE.
    5,665 pointsBadges:
  • pdraebel
    I use another command SNDTCPSPLF. I believe that when using this command you would not need to bother with Directory entries, but would need an OUTQ for the user at the destination LPAR.
    7,545 pointsBadges:
  • Teandy
    This article may help.
    5,860 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: