>What will the *PSSR buy me?  Remember, this code detects time-outs
>except when the comm line actually goes down. With the immediate check 
>of MAJMIN and the error indicator, I can use mainline code to direct
>If I use the *PSSR, then won't I need to do something like this?
>     C* Top of calcs...
>     C           CNDCDE    CABEQ'T'       READRC                     
>     C           CNDCDE    CABEQ'E'       CLOSEF                     
>     C* rest of calcs...
>     C* Read a record
>     C           READRC    TAG
>     C                     WRITEINVITE                                
>     C                     READ DMSMTXFM                 80           
>     C* rest of calcs...
>     C* Close up shop
>     C           CLOSEF    TAG
>     C                     CLOSEDMSMTXFM                 
>     C* rest of calcs...
>     C           *PSSR     BEGSR
>     C* check status...
>     C           MAJCOD    IFEQ '03'                                  
>     C                     MOVEL'T'       CNDCDE      
>     C                     MOVEL'*GETIN'  ACTCDE
>     C                     GOTO PSSREN                                 
>     C                     ENDIF                                      
>     C* Rest of PSSR...
>     C           PSSREN    ENDSRACTCDE
>I generally use the *PSSR only for unexpected "catch-all" situations.
>I find it much easier to handle errors by calling the proper subr from
>the mainline.   Maybe this is an outdated way to do this sort of stuff?
>What do the rest of the list think?

 It is the error subroutine.  Think of a timeout as a "hard" error.  If you
don't monitor for it, the program will blow up, just as the line errors
will.  Contrast this w/ a "soft" or expected error such as a CHAIN that
doesn't get a hit.  Of course the CHAIN indicator traps the error, but I
hope you see the difference.


| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].