IPCS uses the problem identifier to uniquely identify a problem. The problem identifier is composed of a three-character prefix and a five-decimal-digit suffix. The prefix is used to differentiate between problems with similar numbers in different problem directories. It is specified in your session parameters member, but you never specify it on an IPCS subcommand. When IPCS lists problems, it displays their complete problem identifiers, including prefixes. The prefix is not stored in the problem directory and can be changed without affecting previous work. IPCS assigns the suffix when you add a problem. After the problem identifier is stored, you cannot change it. You specify the suffix on any IPCS subcommand needing identification of the problem.

The date and time of problem occurrence allow you to specify when a problem occurred. IPCS sets the date and time of problem reporting when you add the problem to the problem directory. You can modify the problem occurrence attributes but you cannot modify the problem reported attributes.

The group and owner identify both the group and the individual responsible for tracking and resolving the problem. The group is the department or organization name or any other identification you want to use for your installation. You can change the group at any time. You can specify an owner for the problem by specifying a TSO/E userid, or IPCS supplies your TSO/E userid as the default. The owner is significant because certain IPCS subcommands can be run against a problem only by its owner. As owner of a problem, you can modify its attributes and, unless restricted, delete it. You can transfer ownership of a problem by modifying this field.

The system and component attributes identify the environment of the problem. The system identifier refers to the hardware or software system on which the problem occurred. The component identifier refers to the software component you suspect has caused the failure.

The severity attribute allows you to specify a numerical estimation of the severity of the problem, consistent with standard IBM APAR severity codes.

The status and identifier attributes allow you to provide information about the status and resolution of the problem. The status attributes -- PROBLEM, FIX, IBM, and PTF -- allow you to indicate the status of the problem and the status of its resolution. You can indicate the status from your point of view (PROBLEM and FIX status) and from IBM's point of view (IBM and PTF status). For each status attribute, IPCS records the date and time of the last change to that attribute.

The identifier attributes -- APAR, PTF, and FIX -- allow you to indicate the APAR for the problem and the PTF or FIX that might resolve it or that does resolve it.

The abstract and description allow you to describe the problem, first briefly in the abstract, then at length in the description.

The user data attribute allows you to specify additional information about the problem. It is defined by the user or by the installation.