ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

Can you change the owner of a spool file????

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Can you change the owner of a spool file????

    We have a project here at the office - the objective is to take a spool file generated by one user and change the owner of that spool file to another user so that the original owner never sees the spool file.

    Can this be done? And if it can what is the best way? Is there an API that can be called to obtain information?

    Thanks!

  • #2
    Re: Can you change the owner of a spool file????

    I don't believe there is anyway to change the owner of an existing spooled file.
    The only way I can think of doing it is to send the report to another user and delete the original.

    Comment


    • #3
      Re: Can you change the owner of a spool file????

      If you have TAATOOLS on your system, you can use DUPSPLF to make a duplicate of the spoolfile and assign a new owner. Then delete the original spoolfile.

      If you don't have TAATOOLS, then I suppose you could use SNDNETSPLF to a different user on the same system, and then get rid of the original.

      Comment


      • #4
        Re: Can you change the owner of a spool file????

        I'm not aware of any way to change the owner of a spooled file after creation, though one might exist.

        It is possible to manipulate ownership during creation in a few ways. Otherwise, maybe the easiest way is to duplicate the spooled file, e.g., with SNDNETSPLF to a second *OUTQ on the same system, and delete the original spooled file. Determining the timing might be the hardest part for you.

        Changing ownership of a spooled file after creation has a potential for interfering with some audit needs. That might be part of why no clear function exists. Also, the spooling subsystem has been around for essentially the full life of the system line in a relatively unchanged state. It might not be easy to provide a function at the system level without some underlying changes. There might not be many still at IBM who know the internal details well enough to do it economically without some significant number of customers asking for it.
        Tom

        There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

        Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

        Comment


        • #5
          Re: Can you change the owner of a spool file????

          Hey, you could have the print program run under the other user name.
          Hunting down the future ms. Ex DeadManWalks. *certain restrictions apply

          Comment


          • #6
            Re: Can you change the owner of a spool file????

            We used to do thisby running SNDNETSPLF to trannsfer the splf. instead of specifying a diffeent computer, wed specify the same computer but a different userid.

            Comment


            • #7
              Re: Can you change the owner of a spool file????

              Why not use a different output q where the user does not have access?
              Just a different way to solve an issue.

              Best of Luck
              GLS
              The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

              Comment


              • #8
                Re: Can you change the owner of a spool file????

                Originally posted by GLS400 View Post
                Why not use a different output q where the user does not have access?
                The owner of a spooled file can always access it regardless of the *OUTQ. A simple WRKSPLF doesn't require an *OUTQ reference.

                The spooled files will be listed since the spooled file itself doesn't reside on an *OUTQ. The only that is actually on the queue is a kind of "record" that points to where the spooled file physically sits; and if you try to restrict the physical location, lots of problems can follow that no one wants to mess with.
                Tom

                There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

                Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

                Comment

                Working...
                X