I don't have a magic answer for you, but it has been my observation over
the years that tag handling in RSCS is one of the most commonly modified
pieces of code you can find. It is common to find something missing in
what RSCS will pass in the tag info to whatever kind of OS is on the other
end of the connection, so you end up with an RSCS exit or mod.
Jim
At 02:25 PM 2/2/2006, you wrote:
I am trying to get VM spool members to VSE to be printed by PSF/VSE. I
have
found references on this list to many different methods of using 'CP
TAG'
but none have resulted in the actual retention of the '* $$ LST' info I
am
trying to pass. I am using RSCS, which I CP TRANSFER to his RDR. Here
is
what the closest SPOOL/TAG/CHANGE combination I have come up with:
'CP TAG DEV PUN VSEOO2 CLASS U FORMS BPD1 CHARS GT12'
'CP TAG FILE spoolid PWR07 VSEOO2 1 JOBNAME=PROFILE () USER=OPERATOR
CLASS=U FNO=BPS1 JSEP=(1,Y)'
and then:
'CP CHANGE P spoolid FORM BPD1 CHARS GT12'
The result is a LST Q member with just the correct form of "BPD1" and
"CLASS
U" (not sure if CHARS is passed cause' you can't see this with a
PDISPLAY
LST,U,FULL=YES). The JOBNAME of "PROFILE' gets passed correctly. I
have
tried putting the $$ LST parms inside the parens, and also seperated by
commas, but RSCS seems to ignore them.
Any clues???
Thanx for your time.
Jim Bohnsack
Cornell Univ.
(607) 255-1760
