Google
 
Trailing-Edge - PDP-10 Archives - BB-J712A-BM - uetp/lib/sender.rel
There are 13 other files named sender.rel in the archive. Click here to see a list.
 0MD9zHp_C9xO3ET	 *9@gtI9(+ 3 P@@ Q*"O	"" " $,,~ "[ B " $, 5@ H`f+Q`f+
`f	*"+
,U ",] H,]+
ZHZT.P,,,, 
DC`!

,#4A
 H .(,9+"\ ]@  E	*
Q""\"],E,~ H`f+
+@@@@@@@@,4@W B " $,	*
Q
*4@] B $,# B $4c,'4@5 B " $,4@k B $	"
E*3,# B $4r ,O@+~ v $\&v,+~,.4@\$	 U
@ ;!"4XB
A 
A4
A\$	 &@ (4 $@/\"		*A(U*D,+?Z
A	+ @@
A+~  $\&,+~  BP+~\" $@	*(AL\&,$" \",+~ ",9+R@ +~O@	,Y,K	 
U,_6B,9+X@DC`+~ " U$@@+ + \",E+~	"P*P ]\"H,E+~ 6@, @@+~  BP\"  $,>,,^4f	 @*f,K1+j,>,>,>,>,>,>) B4l,U,Y P  BP	"A
n,9+q\ 	 @E\"	 $(, * $D * &@+ +  $@	"TQw/\"	, VP+~!+
O"]6@,9+~@\+~1	(+,>,>,>,>,>,>,>/ B D F,4@5,>:\ 	 *( @4:,^+~@@Y <*&
@,9+\ R`< E,9+\ S<E\"},>&\(V,#	 Q",^&"t\(W,# * "P B " $,5@X1B
+"1B
+"1B+"	"Q@!,4C=j+!1+&,>,>,>,>G-!  &$ D 	 *&$ D~ F~,9+1\  `0 G`~0 G`~0E+~1	( 2+5,>,>,>,>KQ",9+9@DC` K \"X$Q$S&}@	 D ;+ +  ",9+@@DC` M +~,9+D@DC`	*C P <,~,9+G@ ,~  

  "Q@@*"!" B0	(DL R B0\"R B0\"S B0,~  

  "Q@@*"!" B0 R	" @T B0\"R B0\"S B0,~7@+
@ $T+@@+ ]	 C] _@ [8\H]`^p_

`

a

 b(`(Hc	(
 e	 @Hg	 @Hhj((Hj	 @Hm	(@*n	(`(Hn	 @Hps@@(HrwWZ	( 
vG @Huy{@@(HwyZO(	 P(`(Hz	 @H{(	y0Px`5@pSENDER>[
	*++

******************************************************************	 **


SENDER Program

FUNCTION	THISPROGRAM IS MEANT TO BE USED BY THE BATCH
	TEST CREATOR FOR UETP COMMUNICATION.  ALL EVENT AND 
	ERROR CONDITIONS OCCURING IN	 * THE BATCH TEST CAN BE RELAYED
	TO THE UETP VIA THIS PROGRAM.  THERE IS NO OTHER WAY	 2
	TO COMMUNICATE WITH THE UETP.



COMMANDS

        a.      Commands which qu	 ;alify the messages to be sent.  

                1.      TEST NAME <text>

     	 C                   The first 10 characters of <text>  go  into  the
                	 L        test name field of all messages to be sent until
                        the	 T next "TEST NAME" command.

                2.      BLABEL <text>

              	 ]          The first 10 characters of <text>  go  into  the
                        b	 eatch test  label field of all messages to be sent
                        until the 	 nnext "BLABEL" command.

                3.                           /  MAJOR  \
 	 v                                           /   MINOR   \
                         TY	 PE  (OF MESSAGE) \   END     /
                                             \  ERROR	   /
                                              \ START /


                   	      A code corresponding to  message  type  will  be
                        placed	   into  the  message  type  field  of  all
                        messages sent unt	 !il the next "TYPE"  command  is
                        given.  The message types ar	 )e:


                        MAJOR   major run milestone
                        	 2MINOR   minor run milestone
                        ERROR   errors  
              	 :          END             end of run (a major milestone message)
                   	 C     START   start of run (a major milestone message)



        b.      Commands	 K which relate to the message text.

                1.       EXTRACT (MESSAGES FROM	 T) <file-spec>

                This tells "SENDER" that the messages are to  come  	 \from
                the  named  file.   These messages will be placed in the
     	 e           ninth (text) position of  message  records.   The  first
                	 meight field being filled in by SENDER.

                Each message sent will also	 v be written to  the  terminal
                assigned  to  the  job, so that in nor	 ~mal usage, running
                under a batch control file, the messages will sho	 w up in
                the test log file.

                All the messages in  t	 he  file  will  be  sent  in  this
                manner.   When  "SENDER"  reaches	   "end of file" it will
                return to the user  terminal  (batch  contro	  l  file)  to
                accept more commands.


                2.       SEN	 )D (MESSAGE TO UETP) <text><carraige return>

                The contents of <text>	 1 will be used for a message  which
                will  be  sent  immediately,  alo	 :ng  with any qualifying
                information provided via the commands a.1  t	 Bhrough  a.6.
                The  time  stamp  will be taken from the current monito	 Kr
                time and will be labeled "origination time  stamp"  ("O"
        	 S        in position 19).


                3.      EXIT (TO MONITOR)

          	 \      This command terminates the execution of SENDER.




RESTRICTIONS

     	 d   The general conventions for running batch jobs are  intended  to
        guarante	 me  communication  with  the  Command  Processor  at  the
        beginning and end o	 uf each batch run.  To  accomplish  this  goal
        each  batch  job  should run t	 ~he SENDER program at the beginning
        and end of each batch run.  

        S	 ENDER  gives the batch run creator
        the  ability  to  communicate  with  UETP	   which  records  all
        information in the error and  event  logs.   This  rec	 ording  is
	 essential  to  the sucess of UETP.  If all batch runs follow the
        recording  conventions  then  their  flow  and  status  can   be
        mo	 (nitored and reported promptly and accurately.

        The basic conventions are qu	 1ite simple.  The first step  in  any
        batch  control  statement  will  be an 	 9execution of SENDER.  The
        information sent must identify the sender  and  gi	 Bve  the  start
        time.  The last logical step must have two components.  first	 J, a
        %ERR::  execution of  SENDER  which  traps  unknown  errors  and
      	 S  informs UETP.  Second, a SENDER run informing UETP that this
        is a succesfu	 [ll end of this run.  An  example  may  clarify  the
        convention:

         	 d       
                @RUN SENDER
                SENDER> TYPE (OF MESSAGE) START	 l
                SENDER> TEST NAME COBOL2
                SENDER> SEND BEGINNING CO	 uBOL2 RUN
                SENDER> EXIT
                        .
                  	 }      .  ACTUAL BATCH RUN
                        .
                @GOTO NOERR
  	               ; We execute here if there was an unexpected error
                %ER	 R::@CHKPNT
                PRINT COBOL2.LOG
                @RUN SENDER
          	       SENDER>TYPE ERROR
                SENDER>BLABEL %ERR
                SEBDER>T	 EST NAME COBOL2
                SENDER>SEND UNKNOWN ERROR IN COBOL2 RUN
           	 (     SENDER>TYPE MINOR
                SENDER>EXTRACT COBOL2.LOG
                SE	 0NDER>EXIT
                ;We always pass through this next section
               	 9 NOERR::@RUN SENDER
                SENDER> TYPE END
                SENDER>TEST NA	 AME COBOL2
                SENDER> SEND END OF COBOL2 RUN
                SENDER> EX	 JIT
                %FIN::;In case of disatorous errors

                @CHKPNT
 	 R               @PRINT  COBOL2.LOG
                
        The basic philosophy of 	 [the convention is to guarantee that some
        message gets back to UETP about the	 c ending status of this run.
        If the run ends with no errors then that fact wi	 lll be  conveyed.
        However,  if  any unexpected errors occur then UETP will st	 till
        receive information about the end of the test.  

HINTS

EXAMPLES
	 
(}
:x,~\"&#4\"J4*4@,4@"Z
 `F`,4,"P ( B
A@B+~U@                                                                              X	.T
Pt	\sH,_@@+
Improper field (input file) in TAKE command\"S,2+~	 PY
?Cannot open TAKE command file
 \"Y,E+~Could not set file byte size f	 "aor TAKE input file\"^,2 , +~
?Cannot open output file for TAKE comm	 T jand
 \"f,E , +~Could not set file byte size for TAKE output file	*D(r\"m,2 ,  , +~HU?Error in BLABEL command (from SENDER)
?Er	 ({ror when trying to parse filespec in EXTRACT command\"z,E,A+~Error open	 *ing file for EXTRACT command\",2+~?ERROR IN OPEN FOR EXTRACT (FROM SE	 T 

NDER)\",f+~?ERROR IN SIN IN EXTRACT (FROM SENDER) 
A
`d+E	*P\",f+~HQ?ERROR IN TEST NAME COMMAND (FROM SENDER)?Error in SEND comma	 nd (from SENDER)
ERROR?SENDER started illegally.  BATCH control error	 @%1:},^,^,^,^,^,~%H	@1:},^,^,^,^	 
.,^,^,~+
?Error parsing TEXT field of current command\"0,E,A	(\6+~ERROR WITH SOUT JSYS AT STTXT:\"7,f+~;YCan't send message t	 "?o UETP because  = @ <g:(AgtI91:~,^,^,^,~D	 G:1:~,^,^,^,~H?SENDER error:  ?Jsys error message:  	 P?GALAXY error:  ?{UETPCMDLOGTake command illegal within a take file..comm	 3Xand ignoredBLABELxcEXIT
0fEXTRACT hHELP
lSEND	8nTAKEXq	&0aTESTx~TYPE	 current label of BATCH control fileto MONITORmessages f	 iromfile to extract messages fromwith SENDERmessage to the UETPcommands from f	 rilefile to take commands fromlogging output onfile to log output inname 	 zof testof messageEND  LOG  MAJORMINORSTARTxUnexp	 (ected error in GETJI at GPID:\",2,K@Unexpected error in NOUT at GPID:	*
\",2,K)`ErroreinoSOUTdJsyssattemptingtobwrite UETP'sPID\"<g9gtI9,4Failu	 (Are in receiving INFO mes  O <g9gtI9,4!Can't get UETP's PID	 "%  (probably not running in this directory) #  % (*gtI9	 PJPJPKz3gP%@[~+sU)Z+ta,dP	@,d6	8v:]R8H.@D89w+HX|J##ll	K!?<JLmf`JLzU 	D"JL=AKQ(T]KRBKRY"L>GWRMo/M^$GVROI@RO:	Du?RQ	Pgs	P
_sGfR`=3
	"	LRd=_6M\E6kL
A	Wcw?SB1VSe&S
14S
1g	S
2~K "jK5kbKO.&

A
NtY#
NvyK+l>@K+lu_	 K+mP
XVS,;:"?C~K1+G\ 
k[L
l
E$X,cg|		SWaI@SWbSWbBSWbxPeSvP%u@|>[K`+	g`	DS`'uKi

Xp4@

Xw5@(P~s]T+#RT:QI	T:"hT:"z;

:XP>.@C>9t	C?2YQut
=Pm&XLYf7D@	"0JHB(TUHu^#zu^5,u^;LPUgd@P	P		 P
P
u}C3Uus~uC

K
eu?Z

	uAUTI@UTTfUTmxxUTuN$c	]PWx`%B[S+	

=w
U

)u/U

)uWU

)uk)Y~4z-xw*[3	 1;+~P*&5tQ+}8Q}I cM[+M[+"M[+!PE	PEUJuRdUJuRzUJuS/UJuSmUJuSvPst*MD:Ky?V	@P99@9EIUP9@@UPK	8(Rp2	!Rp@,E9s	UT9<HPeP:	 UX8z!PYPYPZPZ	D">'5c;W>#9G>#9Oc;@c;zc;+,c;1Ac;r{	e-!TP;3@;F3S;F3h0G#W3Qn5@"nJqUnK';U	PkU/`UqRW@PkU2UqRWjUqRWoUqRWqUqRWrUqRWrqQ9N	qQ;t]UqQUdEUqQUf UqQUjUqQUk`UqQUk UqQUm`UqQUm@UqQUnD	 UqQUoC`UqQUp@UqQUs qQSUqR$.@~:aC
A
=}PbK	V;/VKP?`XVP@^t=c=VT@	_	f_	h	D"=Zoj_wl_]Xn_c&q=ws=ww=wy=wz_cz~	D _g	=xi=xi7
tV7
z.@z{PPG@Pba	2Z#,W+PW.	{~KM;,~P@+PG+
W1UK ~OPBiWPC%[gtI9	W(Y1W+e=W+|+W+|.W.IdW0"W4SPtP7	PdWLoWuPq_WuPrWuV~WuVWvPGjPGp	WmvPPHg
PHg
PHgPHgPHhjPHho~W7	ODpONkON-ON36ON?)ON@IONK]ON_}OOw	@iMKScu:O/L`O{OXO/gOKiOQVnE%P	O(hO(hO(hO(h,Oi),O9RHPI=OOrc PIYD GKd%~3GzoJ8 ( -