Without sample RSCS and CP QUERY command output... Try: CP SMSG RSCS CHANGE linkid sfid NOHOLD No transfers required.
Try also: HELP RSCS MENU Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Horlick, Michael" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 12/08/2006 09:13 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject How to find tag info for a spool file not your own Greetings, This is related to another post I put on regarding spool files being sent to RSCS from a VSE machine being placed in ?user-hold?. I would like to know if there is a way to find out the tag information for a spool file in another user?s (in my case, user RSCS) reader. I thought I could do a CP TRANSFER RSCS RDR spoolid? to my userid, do a ?TAG QUERY FILE? on the file to determine the linkid , send a SMSG to RSCS to purge the now missing file, change it to NOHOLD and transfer it back to RSCS?s reader but I see the tag info gets changed and RSCS rejects it. I can work around this by retagging the file before transferring it back to RSCS. I also tried doing a ?CP CHANGE RSCS RDR spoolid NOHOLD? but unfortunately RSCS does know that the file has been changed to NOHOLD and since I don?t know what linkid I can?t issue the equivalent SMSG RSCS CHANGE command to do it. Of course, it would be a lot simpler to just be able to query the tag info of a spool file in RSCS?s reader that is in ?hold? status. I have VM:Spool and see that maybe it can be done but I think it also does a CP TRANSFER. Another solution would be to do a SMSG RSCS Q SYS Q and process the result. We use VM:Operator and I would have to get our automation group involved in trapping and processing the output. That?s a possibility. Maybe I can get to the tag info through some displays of CP control blocks? Any other way? Thanks, Mike The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
