| Previous | Contents | Index |
The SWRK_OPEN_JOB routine ...
status =SWRK_OPEN_JOB(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_OPEN_JOB routine ...
The SWRK_OPEN_OUTPUT routine ...
status =SWRK_OPEN_OUTPUT(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_OPEN_OUTPUT routine ...
The SWRK_PARSE_DIRECTORY routine ...
status =SWRK_PARSE_DIRECTORY(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_PARSE_DIRECTORY routine ...
The SWRK_PARSE_FILE routine ...
status =SWRK_PARSE_FILE(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_PARSE_FILE routine ...
The SWRK_PARSE_LOG_FILE routine ...
status =SWRK_PARSE_LOG_FILE(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_PARSE_LOG_FILE routine ...
This routine inserts a new message at the beginning of a message vector.
status =SWRK_PREFIX_MSG_VEC (message_vector, status [, value...])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
status
VMS usage: cond_value type: longword (unsigned) access: read only mechanism: by value
Specifies the OpenVMS message id of the message to be logged. See the $GETMSG system service for more details.
values
VMS usage: varying_arg type: longword (signed) access: read only mechanism: by value
Specifies optional expressions whose resultant types correspond to conversion specifications given in the OpenVMS message text.
If no conversion specifications are given, you may omit the output sources. Otherwise, the function call must have exactly as many output sources as there are conversion spec- ifications, and the conversion specifications must match the types of the output sources.
Conversion specifications are matched to output sources in left-to-right order. Excess output pointers, if any, are ignored.
message_vector
VMS usage: cntrlblk type: longword (unsigned) access: modify mechanism: by reference
Specifies the message vector into which a new message will be loaded.
This procedure inserts the message specified by the status and value arguments into the beginning of a message vector. The message vector must be correctly initialized before a call to SWRK_PREFIX_MSG_VEC is made. Any existing entries are moved down. The number of entries inserted (and hence the distance the existing entries are moved) is based on the facility code of the status. See the OpenVMS System Services Reference Manual for details about message vector layouts.To build a message vector with more than one message, a call is made to SWRK_SETUP_MSG_VEC to setup the last message line, followed by calls to SWRK_PREFIX_MSG_VEC to setup earlier lines. The last call to SWRK_PREFIX_MSG_VEC inserts the first message line.
The SWRK_PRINT_FILE routine ...
status =SWRK_PRINT_FILE(arg1, [arg2])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
arg1
VMS usage: arg1_type type: integer (unsigned) access: read only mechanism: by reference
Specifies arg1...
arg2
VMS usage: arg2_type type: character string access: read only mechanism: by descriptor
Specifies arg2...
The SWRK_PRINT_FILE routine ...
The SWRK_PROCESS_FILE routine ...
status =SWRK_PROCESS_FILE( file-spec [,dflt-file-spec] [,rltd-file-spec] [,user-success-clb] [,user-error-clb] [,user-confirm-clb] [,user-arg] [,rslt-file-spec] [,user-file-clb] [,user-record-clb] [,context] [,extended-flags] [,ufsa-type] [,log-flags])
VMS usage: cond_value type: integer (unsigned) access: write only mechanism: by value in R0
file-spec
VMS usage: char_string type: character string access: read only mechanism: by descriptor
String containing the OpenVMS Record Management Services (RMS) file specification of the files to be processed. The file-spec argument is the address of a descriptor pointing to the file specification. If the specification includes wildcards, each file that matches the specification is processed. The string must not contain more than 255 characters. Any string class is supported.
On Alpha systems, set the LIB$M_FIL_LONG_NAMES bit in the flags argument for strings longer than 255 characters in length.
dflt-file-spec
VMS usage: char_string type: character string access: read only mechanism: by descriptor
Default file specification of the files to be processed. The dflt-file-spec argument is the address of a descriptor pointing to the default file specification. This is an optional argument; if the argument is omitted, the default is the null string. Any string class is supported.
See the OpenVMS Record Management Services Reference Manual for information about default file specifications.
rltd-file-spec
VMS usage: char_string type: character string access: read only mechanism: by descriptor
Related file specification of the files to be processed. The rltd-file-spec argument is the address of a descriptor pointing to the related file specification. Any string class is supported. This is an optional argument; if the argument is omitted, the default is the null string.
Input file parsing is used. See the OpenVMS Record Management Services Reference Manual for information on related file specifications and input file parsing.
The related file specification is useful when you are processing lists of file specifications. Unspecified portions of the file specification are inherited from the last file processed.
user-success-clb
VMS usage: procedure type: procedure value access: function call (before return) mechanism: by value
User supplied success routine that is called after a file is successfully processed.
The success routine can be used to display a log of the files that were processed.
user-error-clb
VMS usage: procedure type: procedure value access: function call (before return) mechanism: by value
User supplied error routine that is called when an error is detected.
The error routine returns a success/fail value that is used to determine if more files should be processed.
user-confirm-clb
VMS usage: procedure type: procedure value access: function call (before return) mechanism: by value
User supplied confirm routine that is called before each file is processed. The value returned by the confirm routine determines whether or not the file will be processed. The confirm routine can be used to select specific files for processing based on criteria such as expiration date, size, and so on.
user-arg
VMS usage: user_arg type: longword (unsigned) access: read only mechanism: by value
User supplied argument that is passed to the error, success, and confirm routines each time they are called. Whatever mechanism is used to pass user-arg is also used to pass it to the routines. This is an optional argument; if the argument is omitted, zero is passed by value.
rslt-file-spec
VMS usage: char_string type: character string access: write only mechanism: by descriptor
String into which the RMS resultant file specification of the last file processed is written. The rslt-file-spec argument is the address of a descriptor pointing to the resultant name.
If present, rslt-file-spec is used to store the file specification passed to the user supplied routines, instead of a default class S, type T string. Therefore, this argument should be specified when the user supplied routines are used and those routines require a descriptor type other than class S, type T. Any string class is supported.
If you specify one or more of the user supplied action routines, the descriptor used to pass rslt-file-spec must be:
- Of the same class as the descriptor required by the filespec argument of any action routines. For example, VAX Ada requires a class SB descriptor for string arguments to Ada routines but will use a class A descriptor by default when calling external routines. Refer to your language manual to determine the proper descriptor class to use.
- (Alpha only) Of the same form as the descriptor required by the filespec argument of all action routines. For example, if the filespec argument of an action routine uses a 64-bit descriptor, then the rslt-file-spec argument must also use a 64-bit descriptor.
user-file-clb
VMS usage: procedure type: procedure value access: function call (before return) mechanism: by value
User supplied file routine that is called for each file that is processed.
user-record-clb
VMS usage: procedure type: procedure value access: function call (before return) mechanism: by value
User supplied record routine that is called for each record in then file that is being processed. If this argument is supplied, each file which is to be processed is opened and read. Each record found in the file is then passed to this routine to be processed is some user specified fashion. If this argument is not supplied, the file is not opened and read.
context
VMS usage: context type: longword (unsigned) access: modify mechanism: by reference
A longword integer variable into which the routine stores a context value for use by future calls. The context argument is an unsigned longword integer containing the address of the context. This variable must be set to zero before the first call. You can use the same context argument from one call to another. This argument is used to retain the context when processing multiple input files. Portions of file specifications that the user does not specify may be inherited from the last files processed because the file contexts are retained in this argument. You must not change the value of context in subsequent calls.
extended-flags
VMS usage: mask_longword type: longword (unsigned) access: read only mechanism: by reference
Longword of flag bits designating extended behavior. The flags argument is the address of an unsigned longword containing the flag bits. This is an optional argument; if omitted, the default is that all flags are clear.
Flag Usage BINARY Force binary file types into binary file format. CONFIRM A confirmation is required before any action is performed on a file. COPY . DELETE . IGNORE_DIRECTORIES . HEADER . MULTIPLE . NOSEARCHLIST . NO_RLF . PRT . QUALIFIED The extended file search qualifiers are to be used. RETAIN_CDT . RETAIN_RDT . RECORD Use record mode rather than block mode. SEQUENTIAL . UPDATE Open files with update allowed. The flag values have symbolic names of the form UFSA$M_flag and UFSA$V_flag.
ufsa-type
VMS usage: code type: longword (unsigned) access: read only mechanism: by value
Specifies the structure of the source file specification.
The following table lists the types of file specification argument which can be passed.
Type Structure INDEX A binary index passed by reference (not implemented yet). LNKLST Linked list of strings passed by reference. STRING String passed by descriptor. The type values have a symbolic name of the form UFSA$C_type.
By default, STRING is assumed.
log-flags
VMS usage: mask_longword type: longword (unsigned) access: read only mechanism: by reference
Longword of flag bits designating logging behavior. The flags argument is the address of an unsigned longword containing the flag bits. This is an optional argument; if omitted, the default is that all flags are clear.
The SWRK_PROCESS_FILE routine ...
| Previous | Next | Contents | Index |