Hitachi MK-96RD647-01 manual FAL Requirements, GetVolSers

FAL Requirements

The FAL functions have the same dataset requirements as FCU (e.g., SAM, standard R0 track format). The FAL also has the following additional requirements:

•The FAL functions support only standard MVS™ VTOC. The FAL functions cannot access MVS™ datasets managed by an index VTOC and cannot access VSE datasets when called from user applications.

•The FAL functions are not “thread-safe.” The FAL functions may not operate properly when used by multiple threads within a single process.

•The FAL functions cannot be used by a “signal handler.” If this accidentally happens and memory space is occupied, use kill to cancel the processes, and use ipcrm to delete the shared memory areas that have KEY=0 (refer to OS manuals). Do not issue the following signals to an FAL/FCU process (UNIX only):

SIGUSR1, SIGUSR2, SIGILL, SIGTRAP, SIGIOT, SIGABRT, SIGEMT, SIGFPE, SIGKILL, SIGBUS, SIGSEGV, SIGSYS, SIGALRM, SIGPOLL, SIGIO, SIGSTOP, SIGTSTP, SIGCONT, SIGTTIN, SIGTTOU, SIGVTALRM, SIGPROF, SIGXCPU, SIGXFSZ, SIGWAITING, SIGLWP, SIGFREEZE, SIGTHAW, SIGCANCEL

•The following terminology is reserved for the FAL functions and cannot be used in function names, variable names, or constant symbols in the user application:

–Words that begin with dataset or fast_

–GetVolSers

6-2 Performing File Access Library (FAL) Operations

Hitachi USP V Cross-OS File Exchange User’s Guide