Chapter Contents

Previous

Next
SIGOPER

SIGOPER



Operator Communication

Portability: SASC


Description
Default handling
Ignoring the signal
Information returned by siginf


Description

SIGOPER is an asynchronous signal. The SIGOPER signal is raised when the operator issues a STOP or MODIFY command or if a parm was included in a START command that initiated program execution.

Note:   Operator commands will only raise the SIGOPER signal after a program call to the opcmd function to enable this interface. If the SAS/C program was invoked from an operator START command, the signal for the START command will generally be raised on return from the call to opcmd.  [cautionend]

Because SIGOPER is an asynchronous signal, the SAS/C library discovers the signal only when you call a function, when a function returns, or when you issue a call to sigchk.


Default handling

By default, SIGOPER causes the program to abnormally terminate with a user ABEND code of 1225.


Ignoring the signal

It is possible, but not particularly useful, to ignore SIGOPER.


Information returned by siginf

When siginfo is called in a handler for SIGOPER, it returns a pointer to an OPER_t structure. It is defined as:

typedef struct {                                                       
    unsigned char type;   /* Type of request                        */ 
#define OPER_start  0x01  /* START                                  */ 
#define OPER_stop   0x02  /* STOP                                   */ 
#define OPER_modify 0x03  /* MODIFY                                 */ 
    char request[105];    /* text from operator - null terminated   */ 
    char unused[22];      /* future use                             */ 
   } OPER_t;

type contains an indicator showing which operator command was issued. For START and MODIFY, the request field will contain a null-terminated string containing the parameter the operator entered.


Chapter Contents

Previous

Next

Top of Page

Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.