RE: CL Trigger example?

[ron_adams@xxxxxxxxxxxxxx]

Actually, the first was right for this example.
The program called on the SBMJOB does not have any parms. We're not 
reading the triggered file nor do we care too much about the data in it.


Ron Adams





Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/17/2005 02:10 PM
Please respond to Midrange Systems Technical Discussion

 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: CL Trigger example?


Missing the parms on the call mypgm.

Sbmjob cmd(call mypgm parms(&trgbuf &buflen))

Chris Bipes
Information Services Director
CrossCheck, Inc.


-----Original Message-----
So, the trigger doesn't actually need to know what data was written to 
the transaction header?  No matter what data was written, it'll just 
submit a new job?

In that case, you can do it quite easily in CL. The following CL program 
should work:

PGM PARM(&TRGBUF &BUFLEN)

     DCL VAR(&TRGBUF) TYPE(*CHAR) LEN(9999)
     DCL VAR(&BUFLEN) TYPE(*CHAR) LEN(4)

     SBMJOB CMD(CALL MYPGM)

ENDPGM