The INCOMPATIBILITY request gives information on all code files in a directory. The report lists the code files that are not able to run on the designated system or systems. Unlike the COMPATIBILITY request, code files that will not run because they are too old for the current MCP level are not listed.
<incompatibility request>
── INCOMPATIBILITY ──<incompatibility specification>───────────────────► ►─┬───────────────────────────────────────────────────────────┬────────┤ │ ┌◄──────────────────────────────────────────────────┐ │ └─ : ─┴─┬─ CONTAINER ─┬─ = <file title> ─┬──────────────┬─┴─┘ ├─ DIRECTORY ─┤ ├─ (CD) ───────┤ ├─ TITLE ─────┘ └─ (CDROM) ────┤ ├─ LEVEL ── = ──<integer>───────────────────────┤ ├─ DATABASE ────┬─ = ──<file title>─────────────┤ ├─ NEWDATABASE ─┘ │ ├─ FAMILYNAME ─┬─ = ──<family name>─┬───────────┤ ├─ PACKNAME ───┘ ├─ (CD) ────┤ │ └─ (CDROM) ─┤ ├─<output option>───────────────────────────────┤ ├─ TAPE ── = ─┬─<unit number>───────────────────┤ │ └─<tape name>─┬───────────────────┤ │ ├─ ( ── CD ── ) ────┤ │ └─ ( ── CDROM ── ) ─┤ ├─ TAPEHEADERS ─────────────────────────────────┤ └─ WRAPPEDFILES ────────────────────────────────┘
<incompatibility specification>
┌◄─────────┐ ──┴─<system>─┴─────────────────────────────────────────────────────────┤
──┬─ CS470 ──┬─────────────────────────────────────────────────────────┤ ├─ CS520 ──┤ ├─ CS580 ──┤ ├─ CS590 ──┤ ├─ CS680 ──┤ ├─ CS690 ──┤ ├─ CS750 ──┤ ├─ CS780 ──┤ ├─ CS790 ──┤ ├─ CS880 ──┤ ├─ CS890 ──┤ ├─ CS4180 ─┤ ├─ CS4190 ─┤ ├─ CS4280 ─┤ ├─ CS4290 ─┤ ├─ CS6280 ─┤ ├─ CS6290 ─┤ ├─ CS7101 ─┤ ├─ CS7201 ─┤ ├─ CS8290 ─┤ ├─ EA1100 ─┤ ├─ EA1400 ─┤ ├─ FS1100 ─┤ ├─ FS1400 ─┤ ├─ FS1600 ─┤ ├─ FS1700 ─┤ ├─ FS1800 ─┤ ├─ FS4100 ─┤ ├─ FS4280 ─┤ ├─ FS4290 ─┤ ├─ FS600A ─┤ ├─ FS600M ─┤ ├─ FS6280 ─┤ ├─ FS6290 ─┤ ├─ LX100 ──┤ ├─ LX6000 ─┤ ├─ LX7000 ─┤ ├─ VSE412 ─┤ ├─ VSE420 ─┤ └─ VSE550 ─┘
Explanation
INCOMPATIBILITY <incompatibility specification>
Produce a report of code files that are not compatible with the systems included in the incompatibility specification. The incompatibility report contains the following information on each code file:
-
FILEKIND
-
First two digits of the SSR level
-
Cycle number
-
TARGET
-
EXECUTE and LASTACCESS dates and times
-
Incompatible systems
When a request includes multiple systems, systems that apply are listed in the report.
When only one system is specified, the system name is implied and will not appear in the report.
<system>
The system name supplied to FILEDATA is validated by the MCP. A system name not known to the MCP is rejected by FILEDATA.
<output option>
For more information about <output option> refer to “Output Options” earlier in this section.
FILEDATA Modifiers
The following FILEDATA modifiers perform functions such as selecting the disk family or file names to be reported on, and specifying the types of information to be reported for each file. These modifiers are explained under “FILEDATA Modifiers” later in this section.
-
CONTAINER
-
DATABASE
-
DIRECTORY
-
LEVEL
-
NEWDATABASE
-
PACKNAME
-
TAPE
-
TAPEHEADERS
-
TITLE
-
WRAPPEDFILES
INCOMPATIBILITY Example
The following is an example of the output for the INCOMPATIBILITY request.
*OBJECT/ED : DCALGOLCODE 47.122, EXECUTEDATE=10/21/1999 14:11:23 PDT LASTACCESSDATE=10/21/1999 14:11:23 PDT *OBJECT/COMP : DCALGOLCODE 46.117, EXECUTEDATE=10/06/1999 20:20:07 PDT LASTACCESSDATE=10/06/1999 20:20:07 PDT *SYSTEM/COMS24 : DCALGOLCODE 45.102, EXECUTEDATE=10/20/1999 19:48:42 PDT LASTACCESSDATE=10/20/1999 19:48:42 PDT