Delete @TCL when building ordersets
When sites copy Service Master from once CICS to another they also copy @TCLs across. If OrderSets have been built seperately in both CICS' then this can cause problems later when adding members to COS.
What may happen is that the user may get an error saying that a @TCL exists and the system will not allow you to add any more members to that COS. This is a problem because the @TCL counter is may not have been completely sync.
So, to prevent this problem you may add code in the pathway to detect old @TCLs as they are about to be 'reused' for the first time. Below is the instruction how.
In $T=OSADDM01 add the stack command:
$T=OOGOSTCL
$T=OOGOSTCL:
| "%GECNGHX"=' ' "%GECNGHX"='02/04/98 - TOME : NEW' "%GECNGHX"='CHECK TO SEE IF THE TCL 530 SELECTED EXISTS, IF SO IT IS' "%GECNGHX"='PROBABLY LEFT OVER FROM AN OLD SM MOVE, GIVE USER OPTION' "%GECNGHX"='TO DELETE IT' "%GECNGHX"='CHECK IF 530 GENERATED TCL ALREADY EXISTS' "%OAVCTYP"='T' "%OAVCNAM"="%DYNTCLA" |
DVA |
| Stack | |
| WHERE "%DYNTCLA" IS VALUED THEN $P=CHPPVCHK, $T=OOGOSTC2 |
Conditional Stack |
$T=OOGOSTC2:
| "%GECNGHX"=' ' "%GECNGHX"='02/04/98 - TOME : NEW' "%GECNGHX"='IF TCL FOUND=Y THEN STACK SCREEN TO GIVE USER OPTION TO DEL' |
DVA |
| Stack | |
| WHERE ALL OF "%OAVCFND" IS VALUED AND "%OAVCFND" EQ 'Y' THEN $S=OOGOSTCL |
Contitional Stack |
$P=CHPPVCHK checks to see if %DYNTCLA actually exists, if so
then stack the screen $S=OOGOSTCL and ask the user if it is ok to remove the
tcl. Commands behind the "YES" probe:
Most of these commands and the user of the program
CHPPVCHK is available in the ARCTOOLS manual, section 20.
Copyright (c) 1998 Philip Tome. All rights reserved