Where allowed to run:
|
Parameters Examples Error messages |
Use the Add CICS File Control Table (ADDCICSFCT) command to add an entry to the file control table (FCT). The FCT defines all the files, both local and remote, that are used either by CICS or by application programs. All files must conform to one of the VSAM file types:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
LIB | Library | Communications name, *LIBL, *CURLIB | Required, Positional 1 |
GROUP | Group | Communications name | Required, Positional 2 |
FILEID | CICS file | Communications name | Required, Positional 3 |
SYSID | Remote CICS system | Communications name, *NONE | Optional, Positional 4 |
RMTFILE | Remote CICS file | Communications name, *FILEID | Optional, Positional 5 |
RMTKEYLEN | Remote maximum key length | 0-32767, 0 | Optional, Positional 6 |
RMTLENGTH | Remote maximum record length | 1-32767, 1 | Optional, Positional 7 |
FILE | File | Qualified object name | Optional, Positional 8 |
Qualifier 1: File | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
MBR | Member | Name, *FIRST | Optional, Positional 9 |
RCDFMT | Record format | *FIXED, *VARIABLE | Optional, Positional 10 |
FILESTS | Status | *ENABLED, *DISABLED, *CLOSED | Optional, Positional 11 |
ACCMTH | Access method | *KEY, *ENTRY, *REL | Optional, Positional 12 |
RECOVER | Recoverable | *YES, *NO | Optional, Positional 13 |
CLRFILE | Clear file | *NO, *YES | Optional, Positional 14 |
ACCPTH | Access path | *FILE, *ARRIVAL | Optional, Positional 15 |
RCDACT | File processing | Element list | Optional, Positional 16 |
Element 1: Add allowed | *NOADD, *ADD | ||
Element 2: Browse allowed | *NOBROWSE, *BROWSE | ||
Element 3: Delete allowed | *NODLT, *DLT | ||
Element 4: Read allowed | *NOREAD, *READ | ||
Element 5: Update allowed | *NOUPD, *UPD | ||
JRNCTL | Journal processing | Element list | Optional, Positional 17 |
Element 1: Number | 0-99, 0 | ||
Element 2: READ ONLY operations | *NOREADONLY, *READONLY | ||
Element 3: READ UPDATE operations | *NOREADUPD, *READUPD | ||
Element 4: WRITE NEW operations | *WRTNEW, *NOWRTNEW | ||
Element 5: WRITE UPDATE operations | *WRTUPD, *NOWRTUPD |
Top |
Enter the name of the OS/400 library that contains the group. Possible values are:
Top |
Enter the name of the group to which this FCT entry is to be added.
Top |
Enter the name by which this file is known. This is the name that will be used in EXEC CICS file control commands. This name is also used to identify this FCT entry.
Top |
This field is only required for remote files.
Enter the identifier of the system where the file is located. The system identifier must have a Terminal Control System Table entry. If this field contains the id of the local system, the entry will be treated as if *NONE had been entered.
Possible values are:
Top |
Enter the identifier by which the file is known on the remote system. This field is not valid for a local file, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Enter the length in bytes of the key field for the file. This field is valid for key-sequenced data sets only. The value must be the same as that specified in the FCT entry on the remote system.
This field is not valid for a local file, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Enter the length in bytes of the maximum record size for the file. The value specified must correspond to the size of the record associated with the file, in the remote system. This field is not valid for the local system, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Enter the library and file name of the file that will be utilized by this file identifier. This field is valid only for a local file, that is when the system identifier field contains *NONE.
Top |
Enter the name of the member in the file that will be utilized by this file identifier. This field is valid only for a local file, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether the record format of the file is fixed length or variable length. This field is valid only for local files, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether or not the file identifier can be used. This field is valid only for local files, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Enter the method that is to be used to access the file. This field is valid only for local files, that is when the system identifier field contains *NONE.
Possible values are:
Note: This field is ignored if you enter *ARRIVAL in the access path field.
Top |
Indicates whether or not the file associated with the file identifier is recoverable or not recoverable. This field is valid only for a local file, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether or not the file is to be cleared when this file identifier is first opened. This field is valid only for a local file, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether the file associated with the file identifier should be processed in arrival sequence (sequential) or in accordance with the value in the access method field (that is by key, entry-sequence number, or relative-record number). This field is valid only for a local file, that is when the system identifier field contains *NONE.
Note: ACCPTH(*ARRIVAL) is not valid when ACCMTH(*KEY) is specified.
Possible values are:
Top |
Indicates whether or not records in the file can be added, browsed, deleted, read or updated. This field is not valid for a local file, that is when the system identifier field contains *NONE.
There are 5 elements to this field. Possible values are:
Indicates whether or not records can be added to the file.
Indicates whether or not records can be browsed.
Indicates whether or not records can be deleted.
Indicates whether or not records can be read.
Indicates whether or not records can be updated.
Top |
Specifies the number of the journal file to be used with this file and which READ and WRITE operations are to be journaled. This field is valid only for a local file, that is when the system identifier field contains *NONE.
There are 5 elements to this field. Possible values are:
The journal number to be used for recording READ and WRITE activity on this file. The journal number must be associated with a file through a Journal Control Table entry.
Indicates whether or not READ ONLY operations will be journaled.
Indicates whether or not READ UPDATE operations will be journaled.
Indicates whether or not WRITE NEW operations will be journaled.
Indicates whether or not WRITE UPDATE operations will be journaled.
Top |
Top |
Top |