Messages and Descriptions › All -G- Messages › GSVC - CICS Command Messages

GSVC - CICS Command Messages

GSVC000I CA SYSVIEW for CICS message <id> unknown

A request has been made to issue an unknown message.

GSVC001I CA SYSVIEW for CICS r<release> SL<srvlevel> Build <build>

The CICS data collection is being initialized.

GSVC002I Copyright (C) <copyright> G$CompanyName

The product is copyrighted and licensed to G$CompanyName.

GSVC003I <opsys> Release = <release> System name = <sysname>

The product is operating on the specified operating system release and system name.

GSVC004I CICS Release = <release>

The product is operating on the specified CICS release.

GSVC005E This release of CICS is not supported

The product is being initialized in a CICS region. The CICS release is not supported.

GSVC006E Product authorization has failed

The product could not be initialized. Product authorization has failed.

GSVC007I Region <parm1> Private = <pvt> E-Private = <epvt> <altered>

This message appears during initialization. The size of the region defined above the 16 MB line is <epvt>. The size of the region defined below the 16 MB line is <pvt>. If you have changed the amount of storage with the configuration option EXTENDED-PRIVATE-LIMIT=, ALTERED is displayed directly after the value. The <parm1> contains the value SIZE or USED.

GSVC008E Configuration option <option> is invalid

The configuration option parameter you have specified is not valid.

GSVC009E Configuration option <option> Parm=<value> is invalid

The parameter specified is not valid for the corresponding configuration option.

GSVC010E Read <libtype> member <dsn(mbr)> failed. <reason>

The specified member could not be located.

GSVC011E Load for module <module> failed

The specified module could not be located. Make sure that the module exists in the assigned STEPLIB JCL statement. The module may also be found in a data set allocated to the linklist.

GSVC012E CICS global user exits <status> error. Exitname <exitname>

An error occurred during the activation or deactivation of CICS global user exits.

GSVC013E CICS CmdLevel error - EIBFN x<eibfn> <fntxt>
EIBRESP <eibresp> x<eibresp> <resptxt>
EIBRESP2 <eibresp2> x<eibresp2>
EIBRCODE x<eibrcode>

An error occurred during execution of the command level request.

• eibfn - Command level function code
• eibfntxt - Command level function text
• eibresp - Internal condition number
• resptxt - Internal condition text
• eibresp2 - Additional details for response
• eibrcode - Response code

Example:

GSVC013E (GSVI) CICS CmdLevel error - EIBFN x7014 SET MONITOR
  EIBRESP 070 x46 NOTAUTH
  EIBRESP2 100 x64
  EIBRCODE x000000460000

 \Common EIBRESP response code values.`

GSVC014I Subtask <name> <status>

This message logs the status of the specified subtask name. Status values are STARTING, INITIALIZED and TERMINATED.

GSVC015I Connection established with SSID=<ssid> Jobname=<jobname> Logger=<logger>

A successful connection has been established with the CICS data logger.

• <ssid> - Subsystem ID
• <jobname> - Jobname of CICS data logger. If the logger is not active, the jobname is displayed as Inactive.
• <logger> - Name of CICS data logger

GSVC016E CICS Data Logger Address Space is not active SSID=<ssid> Logger=<logger>

A connection could not be established with the CICS data logger. The CICS logger needs to be started.

• <ssid> - Subsystem ID
• <logger> - Name of CICS Data Logger

GSVC017I <action> CICS global user exit <exitname>

A request has been made to enable or disable a CICS global user exit for the exitname specified.

• <action> - Action type

  Possible values:

  • Enable
  • Disable
• <exitname> - Name of global exit

GSVC018I Subsystem <ssid> was not found

A successful connection has been established with the CICS data logger. The CICS data was not found connected to the specified subsystem.

• <ssid> - Subsystem ID

GSVC019E Initialization of PC parmlist failed. R15=<r15> R0=<r0> R1=<r1>

The initialization call to the PC failed. Failure information is returned in registers R0, R1, and R15.

GSVC020I <dsa> Size = <size> HWM = <hwm> Limit = <limit>

During product initialization the message will be displayed showing the current size, high water mark and limit values for the CICS Dynamic Storage Areas.

GSVC021E System configuration options could not be found for SSID <ssid>

During product initialization system configuration must be located. The SYSVIEW Main Services address space must have been previously started for this information to be available.

The system configuration information is obtained from the parmlib member GSVXssid in the system parmlib concatenation.

GSVC022E System global anchor table could not be found

The SYSVIEW system global anchor table could not be located. The SYSVIEW Main Services address space must have been previously started for this information to be available.

GSVC023E Unable to connect to the data store <name>

The command entered is trying to connect to the data collection data store.

Possible problems:

• Data collection is not active.
  • Resolution: Start the main data collection address space.

GSVC024I CA SYSVIEW Performance Management

This is a product initialization message.

GSVC025I (<default>) <description> Tranid = <tranid>

During initialization SYSVIEW will dynamically determine the transaction IDs that are to be used to operate the product.

The variable fields in the message contain the following information:

• <default> - The default transaction ID for the specified description.
• <description> - Transaction description
• <tranid> - The transaction ID defined to process function.

GSVC026E A module build mismatch has been detected

A module has been loaded that contains an incorrect build value.

GSVC027I (<tran>) <description> Userid = <userid>

The CICS transaction is being attached with the specified userid.

The variable fields in the message contain the following information:

• <tran> - Transaction ID for the specified description.
• <description> - Transaction description
• <userid> The userid that has been assigned to the specified transaction.

GSVC028I <request> LibType <libtype> DDname <ddname> Dsn <dsn> <message>

A dynamic allocation request has been issued.

The variable fields in the message contain the following information:

• <request> - Request type
• <libtype> - Library type
• <ddname> - The DD name for the request
• <dsn> - The data set name for the request or "SYSOUT"
• <message> - Additional information

GSVC030I Preallocated DDname <ddname> Dsn <dsn>

A dynamic allocation request has been issued for the specifed ddname and data set name. The ddname was already allocated. If this ddname is currently in the JCL for the job, it can be removed.

The variable fields in the message contain the following information:

• <ddname> - The DD name for the request
• <dsn> - The data set name for the request or "SYSOUT"

GSVC031E Preallocated DDname <ddname> Dsn <dsn> does not match

A dynamic allocation request has been issued for the specified ddname and data set name. The ddname was already allocated with a different data set name. If this ddname is currently in the JCL for the job, it can be removed.

The variable fields in the message contain the following information:

• <ddname> - The DD name for the request
• <dsn> - The data set name for the request or "SYSOUT"

GSVC032I STATS LibType <libtype> DDname <ddname> Dsn <dsn(mbr)> Records <count> Elapsed <elapsed> CPU <cputime>

A request has been made to read a member from a data set. The request resulted in <count> records being read.

GSVC034I <type> start has been initiated

The CICS data collection process is being started. The process is in a "WARM" or "COLD" start.

The start mode can be specified using two different methods.

1. Define a CICS System Initialization Table (SIT) INITPARM for the program GSVCGSVS.

   Add the following SIT parameter:

   INITPARM=(GSVCGSVS='initialization parameters')
   

   Example:

   INITPARM=(GSVCGSVS='GSVI=tran,USERID=user,START=start,SSID=ssid')
   

2. Specify initialization options on the initialization transaction GSVS.

   GSVS <initialization parameters>
   

   Example:

   GSVS GSVI=tran,USERID=user,START=start,SSID=ssid
   

3. Specify initialization options on the termination transaction GSVT if a RESTART is being performed.

   GSVT RESTART <initialization parameters>
   

   Example:

   GSVT RESTART GSVI=tran,USERID=user,START=start,SSID=ssid
   

If a start mode of COLD is specified, all configuration data will be read from the respective parmlib members.

If a start mode of COLD is specified, all configuration data will be read from the respective parmlib members. The following configuration options found in the parmlib member CICSOPTS will be ignored and processed as a COLD start.

If WARM is specified above, the following settings will be respected (WARM or COLD).

• ARTM-STARTTYPE
• DUMP-MANAGEMENT-STARTTYPE
• SCHEDULER-STARTTYPE
• THRESHOLD-STARTTYPE
• TRANSACTION-CANCEL-STARTTYPE
• TRANSACTION-GROUPS-STARTTYPE
• TRANSACTION-OPTIONS-STARTTYPE
• VSTATUS-STARTTYPE

GSVC035I <member> : <card>

The card or line from a PARMLIB member is being echoed to the log. The )ECHO statement was coded in the PARMLIB member is initiate the echoing of the cards.

GSVC036I Processing configuration options from <source>

Configuration options are being processed from the specified source.

GSVC037W Datalib object <dataid>.<sysname>.<ssid> was not found

A request was made to read a specific object from the persistent data store. If was not found.

GSVC038I Member <member> DataID <datalib>

A request was made to read an object from the persistent data store. The member name and data ID are shown.

GSVC039I Extended CPU monitoring is <status>

The extended CPU monitoring facility is enabled for disabled. If the facility is enabled, SYSVIEW is able to monitor the the amount of CPU overhead that is added to a transaction during the data collection process.

View the status of the 'Extract CPU Time' facility.

GSVC040E Invalid variable name - <variable>

An invalid substitution variable was specified.

GSVC041E Variable not defined - <variable>

The substitution variable was not found.

GSVC042E Truncation occurred during variable substitution

Truncation occurred during the substitution of a variable.

GSVC044E Load for module <module> failed. Invalid build found <rRR.M>

The specified module was loaded. The build of the module was invalid. It does not match the currently executing build.

GSVC045W Configuration option <option> is obsolete

The configuration option parameter you have specified is obsolete and no longer valid. Review prior release guides and online help for changes in prior releases.

GSVC046E Configuration option <option> can only be set at initialization

A request was made to modify a configuration option. The specified option can only be set during initialization.

GSVC047I Monitor exit interface has been <status>

The monitor exit interface has been successfully initialized or terminated.

GSVC048E Monitor exit interface initialization failed. RC=<rc> <reason>

An error has occurred during the initialization of the monitor exit interface.

GSVC049I <block> <address> has been <action>

An action has been attempted for the specified control block.

GSVC050I System configuration options loaded for SSID <ssid>

The system configuration has been loaded.

The system configuration information is obtained from the parmlib member GSVXssid in the system parmlib concatenation.

GSVC051I CICS <type> monitoring has been set <action>. CICS setting <state>. CVDA value <cvda>.

During the initialization of the SYSVIEW for CICS data collector, CICS monitoring is activated. At termination, the monitoring setting will be restored.

The message logs the actions being taken.

• type - Monitoring class
  • blanks - MN - CICS monitoring option
  • Conversational - MNCONV - Monitoring converse recording
  • Exception - MNEXC - Monitoring exception class
  • Performance - MNPER - Monitoring performance class
• action - The monitoring is being set to:
  • ON - Set monitoring on
  • OFF - Set monitoring off
  • * - Use existing CICS monitoring setting
• state - The CICS monitoring state prior to the initialization of the SYSVIEW for CICS data collector.
• cvda - The CICS CVDA value of the CICS monitoring state.

GSVC052I <request> LibType <libtype> DDname <ddname> Dsn <dsn(member)>

The message is a diagnostic message produced while processing a parmlib member.

GSVC053I BLDL LibType <libtype> DDname <ddname> Dsn <dsn(member)> TTR <ttr> Concat <concat>

A dynamic allocation request has been issued. This is resulting diagnostic information from a BLDL request.

GSVC054I <request> LibType <libtype> <type> <count> DDname <ddname> Dsn <dsn>

The message is a diagnostic message produced while processing a parmlib member.

GSVC055E LibType <libtype> <dsntype> is not defined

The requested library type was not found.

GSVC056E Invalid DCB attributes found. LibType <libtype> Dsn <dsn> <reason>

A request has been made to open a data set. The DCB attributes do not match the required attributes.

GSVC057E LibType <libtype> Dsn <dsn> not found

A request has been made to retrieve a data set name for the specified libtype. A matching data set name does not exist.

GSVC058I <request> LibType <libtype> Dsn <dsn> directory cache has been <action> <address>

A directory for the specified data set has been added or deleted from cache.

GSVC059I <request> LibType <libtype> Dsn <dsn> was <message> in directory cache

A request was made to determine if a specific member was located in a data set directory list cache.

GSVC060I Invalid <libtype> dataset record length, <lrecl1> found, <lrecl2> required

The libtype specified requires specific LRECL values. The LRECL found for the data set does not match the requirements.

GSVC061E Service <service> request <req> failed. RC <rc> RS <rs> <msg>

A service request has failed.

GSVC062I <component> <service> <result> <reason text>

A component service request has completed.

If the request failed, the reason will be displayed as either a text reason for "RC=nnnnnnnn RS=nnnnnnnn".

GSVC063E Function <function> has an invalid <parm> parameter

An invalid parameter has been supplied to the specified function.

GSVC064I CICS <type> monitoring SMF 110 records will be <action>

During the initialization of the SYSVIEW for CICS data collector, CICS monitoring is activated. This message will indicate the current state of creating CICS SMF 110 records.

• type - Monitoring class
  • Exception - MNEXC - Monitoring exception class
  • Performance - MNPER - Monitoring performance class
• action - The state of CICS SMF 110 records
  • Created
  • Suppressed

GSVC065I Dispatching priority - <product> CICSLOGR job <sysvjobn> <sysvdp> is <sysvdp> <status> CICS job <cicsjobn> <cicsdp>

During initialization, each CICS connects to a specific CICS logger task running in a SYSVIEW Main Services address space or SYSVIEW Auxiliary Services address space.

The CICS logger is responsible for the logging of all historical data for the CICS region.

The address space that executes the CICS logger must execute with a dispatching priority that is higher than the CICS that is connecting to it. Multiple CICS regions can connect to a single CICS logger.

If the CICS region's dispatching priority is higher than that of the CICS logger address space, it will be possible for the CICS regions to overload the CICS logger address space. If the CICS logger is overloaded, data can be lost or discarded.

The activation of dispatch priority monitor will monitor or compare the dispatching priorities of the CICS region and connected SYSVIEW CICS logger address space.

If the dispatching priority of the CICS region is greater than or equal to the SYSVIEW CICS logger address space, an error message "GSVC065" will be issued.

• product - SYSVIEW name
• sysvjobn - SYSVIEW jobname
• sysvdp - SYSVIEW jobname dispatch priority
• status - Status

  Possible values are:

  • less than
  • equal to
  • greater than
• cicsjobn - CICS jobname
• cicsdp - CICS jobname dispatch priority

GSVC066I SSID=<ssid> Logger=<logger> is inactive. Retry <count> of <limit> in <interval> seconds

During the initialization process of the CICS data collector, an attempt will be made to connect to a CICS logger that executes in the SYSVIEW Main Services Address Space or Auxiliary Address Space. If the connect fails, multiple retry attempts can be made up to the retry limit count specified.

The following configuration options are available in the parmlib member: CICSOPTS

• LOGGER-CONNECT-RETRY-COUNT
• LOGGER-CONNECT-RETRY-INTERVAL
• LOGGER-NAME

GSVC099I Initialization complete

The initialization of the CICS data collector has completed.

GSVC100W <type> [set the product group or family] <metric> <rsce1> <rsce2> <oldstat> <newstat> V= <value> W= <warning> P= <problem> <ruletype> <elapsed> <jobname> <tran> <task#> <term> <user> Desc='<description>'

An exception has been triggered. The dynamic fields in the message contain the following information:

• <type> - Type of threshold checking

  Possible values:

  • STATE - States
  • SYSTEM - System data collection
  • TIMER - Timers
  • TRANDYN - Transaction - dynamic
  • TRANEND - Transaction - end of task
  • TRANSYS - Transaction - system data collection
  • TRANSUMM - Transaction - summary
• [set the product group or family] - Name of the group that the threshold belongs to
• <metric> - Name of the emtric
• <rsce1> - Name of the resource that triggered the exception
• -<rsce2> - Name of the resource that triggered the exception
• <oldstat>- Old status value
• <newstat> - New status value
• <value> - Value that violated the limit
• <warning> - Warning limit value
• <problem> - Problem limit value
• <ruletype> - Exception rule type

  Possible values:

  • UPPER - Upper limit threshold
  • LOWER - Lower limit threshold
  • CHANGE - Change in value threshold
  • STATE - State
• <elapsed> - Elapsed time since notification
• <jobname> - CICS jobname
• <tran> - Transaction ID
• <task#> - Transaction number
• <term> - Terminal ID
• <user> - Userid
• <description> - Description of metric

This message will be written as a multi-line WTO.

GSVC101I <userid> has issued a <action> for the transaction <tran> <task#> <jobname>

A request has been made to cancel the specified CICS transaction. The variable fields in the message contain the following information:

• <userid> - User ID or task that made the request
• <action> - Action type
• <tran> - Transaction ID
• <task#> - Transaction number
• <jobname> - CICS jobname

GSVC102I <action> Tran <tran> Task <task#> WaitType <type> WaitName <name> Jobname <jobname>

A request has been made to cancel the specified CICS transaction. The current wait reason for the task is shown.

• <action> - Cancel action
• <tran> - Transaction ID
• <task#> - Transaction number
• <type> - Wait type
• <name> - Wait name
• <jobname> - CICS jobname

GSVC103I Set configuration option <option> Parm=<value>

A request has been made to modify the specified configuration option.

GSVC104E Storage OBTAIN failed. LENGTH=<length> R15=<rc> <block>

A storage OBTAIN request has failed. <length> is the amount of storage requested, and <rc> is the return code from the storage OBTAIN request. <block> is the internal block name for the storage requested.

GSVC105I ALET <function> TCB <tcb> ASCB <ascb> SToken <stoken> ALET <alet> SToken <stoken> ALET <alet>

A new ALET has been added to the primary address space access list.

GSVC106W Delete module <module> failed. Address=<address> RC=<rc>

The deletion of a module has failed.

GSVC107I <dump-type> dump suppressed for TRAN=<tran> PROGRAM=<pgm> ABCODE=<abend-code>

The SYSVIEW for the CICS Dump Management Function has suppressed a dump at the request of the user.

• dump-type - Transaction or system
• tran - Transaction creating dump
• program - Program creating dump
• abend-code - Abend code of dump

GSVC108I Module <module> EP=<address> Len=<length> Build=<fixlevel>

A module or program has been loaded at the specified address.

GSVC109I <cemt-response>

When a CEMT or CEDA command or function is issued from the online interface, the response is written to the GSVCLOG ddname using this message.

GSVC110E Invalid <table-type> table entry. <entry>

An entry found in parmlib <table-type> is invalid. The invalid entry is echoed in the message as <entry>.

GSVC111I Control block <name> <address>

Diagnostic information displaying a specific control block ID and associated address in storage.

GSVC112I Shutdown routine <module> has been inserted into PLT phase 2

The shutdown routine has been dynamically inserted into the shutdown PLT.

GSVC113I <module> <offset <apf> <sup> <key> <ziip>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC114I <name> Elapsed=<elapsed> CPU=<cpu> Start=<start> End=<end>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC115I Processing request type <type>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC116I TSF <owner> <hierarchy> Entities <entities> Metrics <count> Zero <skip>

Metrics data is being sent to the Time Series Facility server for the hierarchy. The number of entities is a count of unique entity instances at the lowest level. The number of metrics added is the individual values sent. The number of metrics not added or skipped due to a zero value.

GSVC117E <request> PC request failed. RC=<rc> <reason>

A request made to a SYSVIEW Program Call failed. The return code and reason text is provided.

GSVC118W TSF period data bypassed. Interval resynchronized.

TSF period data collection is being resynchronized.

GSVC119W <userid> has issued a <action> for the task <task> jobname <jobname>. Task <task> was not found.

A request has been made to cancel the specified CICS transaction. The requested task was not found.

• <userid> - User ID or task that made the request
• <action> - Action type
• <task> - Transaction number
• <jobname> - CICS jobname

GSVC120I CA Datacom CSF interface initialized

The CA Datacom CICS Service Facility has been successfully initialized.

GSVC121I CA Datacom CSF interface terminated

The CA Datacom CICS Service Facility has been terminated.

GSVC122I CSF Trace Fn MF TCB# TCA----- TCB----- REQUEST- CVT----- MODIFY-- DBID-- R1------

Internal debugging message used with CA Datacom CSF.

GSVC123I CSF Trace <fn> <tcb#> <tca> <tcb> <request> <cvt> <modify> <dbid> <r1> <elapsed> <cputime>

Internal debugging message used with CA Datacom CSF.

GSVC124I CICS <jobname> has been made non-swappable

The CICS jobname <jobname> has been changed to non-swappable.

GSVC125W CICS monitoring has been enabled.

Data collection for transactions has been resumed.

The data collection for transaction information has previously been dynamically turned off. CICS monitoring was disabled. CICS monitoring has been enabled and transaction data collection will resume.

GSVC126W Data collection for transactions has been quiesced

The data collection for transaction information has been dynamically turned off. CICS monitoring has been disabled. Transaction data collection will be quiesced until CICS monitoring is enabled.

GSVC127W CICS monitoring has been found to be in a disabled state

The data collection for transaction information has been dynamically turned off.

GSVC128I <component> data collection Elapsed=<elapsed> CPU=<cputime>

A trace message logging the start and end time of a data collection interval.

• <component> - Data collection component
• <elapsed> - Elapsed time for the data collection
• <cputime> - Amount of CPU time consumed for the data collection

GSVC129W The variable <variable> is obsolete. Entry was not created.

A request was made to create a monitoring entry or definition for the variable specified. This variable is obsolete.

• <variable> - Obsolete variable name

GSVC130I XDIC Req=<req> RC=<rc>/<rsn> Len=<len> Elapsed=<elapsed> CPU=<cpu>

A trace message logging an external data interface request.

• <req> - Requested function
• <rc> - Return code
• <rsn> - Reason code
• <len> - Length of data returned
• <elapsed> - Elapsed time for the request
• <cputime> - Amount of CPU time consumed by the request

GSVC131I Data collection for transactions was not initialized by user request

The data collection for transaction information was not started during initialization.

The CICSOPTS parmlib option PERFORMANCE-COLLECTION is set to NO.

GSVC132W Unable to return XDIC request <req>. Reason <reason>

An external data request for CICS data was unable to return the requested data to the caller.

• <req> - Requested function
• <reason> - Reason for failure

GSVC133I SNMP Trap <name> <arg> <oldstat> <newstat> <value> <dest>

An SNMP trap has been sent to the destination specified.

GSVC134E <request> request failed. R15=<r15> R0=<r0> R1=<r1>

The specified request failed. Failure information is returned in registers R0, R1, and R15.

GSVC135E CA OPS/MVS Event Notification error. RC=<rc> RS=<rs>

An event notification request made to CA OPS/MVS has failed. The return code and reason code is given.

Return code and description:

• x08 - Call parameter error
• x0C - Storage management error
• x10 - No CA OPS/MVS subsystem is active to process the request.
• x14 - An abend occurred.

GSVC136W CA OPS/MVS Event Notification is not available

No CA OPS/MVS subsystem is active to process an event notification request.

GSVC137W CA OPS/MVS Event Notification has been disabled

An event notification request made to CA OPS/MVS has failed. No more attempts will be made. The interface has been disabled.

GSVC138I Capture event <event> for <variable> <action>

A request is being made to capture an event.

GSVC139I <tran1> started <tran2> via MQ trigger queue <queue> process <process>

Transaction 1 has issued a start request for transaction 2. The transaction initiation was performed due to an MQ trigger queue request.

GSVC140E CA Common Service <function> failed, rc <rc> vrc <vrc> xrc <xrc> fdbk <fdbk>

A request was made to a CA Common Services function. The resulting response and reason codes are displayed.

GSVC141E Description <description>

A request was made to a CA Common Services function. The resulting error description is displayed.

GSVC142E Monitor Exit Interface request <request> failed, rc <rc>

A request was made to a Monitor Exit Interface. The request failed with the specified return code.

Return code and description:

• 00 x00 Okay
• 04 x04 Warning
• 08 x08 No commarea
• 12 x0C Unable to locate anchor
• 16 x10 Unable to obtain workarea
• 20 x14 Workarea initialization failed
• 24 x18 Abend
• 28 x1C Invalid function code
• 32 x20 Unable to locate task pointers
• 36 x24 Unable to locate monitor block
• 40 x28 Invalid commarea length
• 44 x2C Error allocating segment
• 48 x30 Requested segment not found
• 52 x34 Requested event not started
• 56 x38 Invalid field type
• 60 x3C Invalid parameter list
• 64 x40 Cannot add segment, full
• 68 x44 Invalid data type
• 72 x48 Invalid data length
• 76 x4C Data type mismatch
• 80 x50 Data length mismatch
• 84 x54 Data collection is inactive

GSVC143I Monitoring environment has been <action>

During initialization the monitoring environment will be created if this is the first time the CICS region has been monitored since IPL. If the region has previously been monitored, the environment will be reused.

GSVC146I <interface> Debug <func> <tran> <Task#> <data>

Internal debugging message used with the Monitor Exit Interface.

GSVC147I <interface> Trace <func> <tran> <Task#> <elapsed> <cputime>

Internal debugging message used with the Monitor Exit Interface.

GSVC150W Function <function> Response <response> Reason <reason>

A request was made to an internal CICS function. The resulting response and reason codes are displayed.

• Function: NORMAL_CANCEL, FORCE_CANCEL

     Response  Reason
     01 - OK   		01 - INSUFFICIENT_STORAGE
     02 - EXCEPTION	02 - INVALID_TASK_TOKEN
     03 - DISASTER	03 - INVALID_STATE
     04 - INVALID	04 - NOT_PURGEABLE
     05 - KERNERROR	05 - CANCEL_INHIBITED
     06 - PURGED		06 - INVALID_FORMAT
       07 - INVALID_FUNCTION
       09 - LOOP
       10 - ABEND
       11 - MODE_NOT_ACTIVE
       12 - INVALID_STATE_PURGE
       13 - TASK_SLOT_UNAVAILABLE
       14 - NO_TCBS_ACTIVE
       15 - INVALID_MODENAME
       16 - INVALID_MODENAME_TOKEN
       17 - TIMED_OUT
       18 - TASK_CANCELLED
       19 - LOCK_FAILED
       20 - ACTIVATE_MODE_FAILED
       21 - ADD_TCB_FAILED
       22 - SUSPEND_FAILED
       23 - TCB_FAILED
       24 - NOT_SUBSPACE_ELIGIBLE
       25 - TOO_FEW_TCBS
       26 - INVALID_TCB_TOKEN
       27 - INVALID_FRESH_TCB_USAGE
       28 - TCB_NOT_OWNED
  

• Function: DEFERRED_ABEND

     Response  Reason
     01 - OK		01 - ADD_TASK_ERROR
     02 - EXCEPTION	02 - ADD_KTCB_ERROR
     03 - DISASTER	03 - DEFERRED_ABEND_NOT_SENT
     04 - INVALID	04 - INVALID_CALLING_MODE
     05 - KERNERROR	05 - ATTACH_KTCB_ERROR
     06 - PURGED		06 - TERMINATE_FAILED
       07 - INQUIRE_ERROR
       09 - LOOP
       10 - ABEND
       11 - INVALID_FUNCTION
       12 - VECTOR_FULL
       13 - INVALID_TASK_TOKEN
  

• Function: SET_DSA_LIMIT

     Response  Reason
     01 - OK		01 - INSUFFICIENT_STORAGE
     02 - EXCEPTION	02 - INVALID_DSA_LIMIT
     03 - DISASTER	03 - INVALID_ELEMENT
     04 - INVALID	04 - INVALID_DSA_SIZE
     05 - KERNERROR	05 - INVALID_FUNCTION
     06 - PURGED
  

• Function: SET_MXT

     Response  Reason
     01 - OK		01 - INVALID_MXT_LIMIT
     02 - EXCEPTION	02 - LIMIT_TOO_HIGH
     03 - DISASTER	03 - INVALID_FUNCTION
     04 - INVALID	04 - ABEND
     05 - KERNERROR	05 - LOOP
     06 - PURGED		06 - LOGIC_ERROR
  

• Function: CANCEL_AID

     Response  Reason
     01 - OK		01 - NOT_FOUND
     02 - EXCEPTION	02 - MATCHED_TERMID_ONLY
     03 - DISASTER	03 - SECURITY_MISMATCH
     04 - INVALID	04 - UNKNOWN_TERMID
     05 - KERNERROR	05 - UNKNOWN_TRANID
     06 - PURGED		06 - UNKNOWN_SYSID
       07 - NULL_TERMINAL_TOKEN
       08 - NULL_SYSTEM_TOKEN
       09 - TOR_LINK_NOT_ACTIVE
       10 - ALLOCATE_FAILURE
       11 - ALLOCATE_PURGED
       12 - INVALID_FORMAT
       13 - INVALID_FUNCTION
       14 - ABEND
       15 - GETMAIN_FAILED
       16 - ATTACH_ERROR
       17 - LOGIC_ERROR
  

GSVC151I Attempting function <function>

This message will be in combination with message GSVC150W. The requested function specified in message GSVC150W failed. An additional attempt is being made.

GSVC152E Function <function> Return code <rc> Reason <rsn>

A request was made for the specified function. The resulting return code and reason code is displayed.

GSVC154I <message>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC155I Data has been exported to Member=<member> Dsn=<dsn>

A request to exported data has been made. The data has been written to the data set and member specified.

GSVC156I Checkpoint data has been saved for <datatype>

A request to checkpoint data has been made.

GSVC158E <type> ENQ unavailable for <resource>

An attempt to obtain an enqueue on the specified resource has failed.

• <type> - Enqueue type: Shared | Exclusive

GSVC159I ENQ retry <cnt> of <limit> in progress

An attempt to obtain an enqueue on a resource is being retried.

• <cnt> - Retry count number
• <limit> - Retry limit

GSVC160E ENQ retry attempts exhausted - limit of <limit> exceeded

An attempt to obtain an enqueue on a resource has failed. The enqueue was attempted <limit> times.

GSVC161I DATALIB enqueued <type>

An enqueue has been obtained for the persistent data store ddname DATALIB.

• <type> - Enqueue type: Shared | Exclusive

GSVC163I DATALIB dequeued

An enqueue has been dequeued for the persistent data store ddname DATALIB.

GSVC164W Dequeue DATALIB failed, not enqueued

An attempt was made to dequeue the persistent data store ddname DATALIB. The resource was not currently enqueued.

GSVC166E Checksum <checksum> for DATALIB member <member> <message> CRC=<crc>

A checksum was performed to verify the contents of an object in the persistent data store. The verify failed. This can occur is the object has been manually edited or modified. Editing of an object in the persistent data store is not allowed.

GSVC167I Data collection request for <type> has been <action>

An action has been taken for the specified data collection request.

GSVC168I Start TranID <tran> Parms <parameters>

A request has been made to start the specified transaction ID with the supplied parameters

GSVC170I Allocation of G-PVT complete. Size <size> Address <address>

A memory object has been obtained above the 2G bar. SYSVIEW manages its storage above the 2G bar.

GSVC171E Allocation of G-PVT failed. Size <size> Rc <rc> Rsn <rsn>

An attempt was made to obtain storage above the 2G bar. The attempt failed.

• <size> - Size of storage request
• <rc> - Return code
• <rsn> - Reason code

GSVC172I G-PVT limit has been increased from <before> to <after>

The memory limit value that restricts the amount of storage that can be obtained the 2G bar has been increased.

• <before> - The memory limit value before increase
• <after> - The memory limit value after increase

GSVC173E Grande storage GETMAIN failed. Size <size> Rc <rc> <message>

An attempt was made to obtain storage above the 2B bar from the storage that is being managed by SYSVIEW. This request has failed.

• <size> - Size of storage request
• <rc> - Return code
• <message> - Failure mesage text

GSVC174E Grande storage FREEMAIN failed. Address <address> Rc <rc> <message>

An attempt was made to release storage above the 2B bar from the storage that is being managed by SYSVIEW. This request has failed.

• <address> - Address of storage to be released
• <rc> - Return code
• <message> - Failure mesage text

GSVC175I G-PVT Alloc <alloc> Count <count> MemLimit <memlimit>

During product initialization the message will be displayed showing the current status of grande private storage.

GSVC176I Checkpoint data for <dataid> has been bypassed. Data is unchanged.

A request was made to checkpoint the specified dataid. The data had not been changed and therefore the update was bypassed.

GSVC178I Metric <name> Arg1 <arg1> Arg2 <arg2> Rule <rule> XDRB <xrdb> <status>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC179I Metric <name> Arg1 <arg1> Arg2 <arg2> Tran <tran> Task <task> Rule <rule> Status <status>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC180E Invalid date parameter - <dateparm> - <reason>

The specified date parameter is invalid.

GSVC181E Invalid time parameter - <timeparm> - <reason>

The specified time parameter is invalid.

GSVC182I Data collection metrics for <type> have been reset

A request has been made to reset the status of all metrics for the specified data collection type.

GSVC183E Data collection type <type> is invalid

A request has been made for the specified data collection type. The type specified is invalid.

GSVC184E Data collection type <type> cannot be reset while collection is active

A request has been made to reset the status of all metrics for the specified data collection type. A reset cannot be performed while the collection for the type is active.

GSVC185I <member> : <lineno> : <control> : <card>

The message is a diagnostic message produced while processing a parmlib member.

GSVC187I Echo contents <Begin|End> LibType <libtype> DDname <ddname> Dsn <dsn(member)>

A request has been made to echo the resulting contents of a parmlib member.

GSVC188I Monitor <type> <address>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC189I <internal debug values>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC190I PUT Channel <channel> Container <container>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC191I <internal debug values and codes>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC192I ALET <alet> Class <class> Pool <pool> Cell <cell>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC193I <internal debug values and codes>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC194I <internal debug values and codes>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC195I <internal debug values and codes>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC196I Variable <variable> Value <value>

Internal debugging message displaying the current value for a data collection variable. Contact CA Technical Support for more information if this message is displayed.

GSVC197I Current value Tran <tran> Variable <variable> Value <value>

Internal debugging message displaying the current value for a data collection variable. Contact CA Technical Support for more information if this message is displayed.

GSVC198I Trace point <id>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC199I Routine <id> R0=<r0> R1=<r1> R15=<r15>

Internal debugging message. Contact CA Technical Support for more information if this message is displayed.

GSVC200E CICS Transaction Abend Information

An abend has occurred within a CICS program.

GSVC201E Tran=<tran> Task=<task> Code=<code> Program=<program> ReqID=<reqid> Resource=<rsce>

An abend has occurred within a CICS program.

• <tran> - transaction ID
• <task> - task number
• <code> - abend code
• <program> - current program
• <reqid> - request ID
• <rsce> - resource

The issuing of this message can be controlled using the configuration option ABEND-NOTIFICATION found in the parmlib member CICSOPTS.

GSVC202E PSW <program-status-word>

An abend has occurred within a CICS program. The PSW (program status word) at the time of the abend.

GSVC203I CICS <jobname> Tran <OTran> Task <OTask> NetName <netname> UOW <uow> GroupID [set the product group or family] Token <token>

CEAPM GUID Correlation ID tracing.

• tran - Current transaction ID
• task - Current task number
• action - Action in process
• jobname - GUID origin CICS jobname
• otran - GUID origin transaction ID
• otask - GUID origin transaction number
• netname - GUID origin network name
• uow - GUID origin unit-of-work ID
• group - GUID origin transaction group ID
• token - GUID tracking token

GSVC210E Delimiter error on parameter <parmnumb>

The parameter <parmnumb> specified did not specify the ending character delimiter.

GSVC211E Length error on parameter <parmnumb>

The parameter <parmnumb> specified exceeds the maximum parameter length.

GSVC212E Number of parameters specified exceeds maximum allowed

More parameters are specified than supported.

GSVC213E Only 1 parameter allowed on <comname> command

The command <comname> is issued with two or more parameters. Issue the command again, specifying only one parameter.

GSVC214E Only <x> parameters are allowed on the <comname> command

The <comname> command is issued with more parameters than are allowed. Issue the command again, specifying <x> (or fewer) parameters.

GSVC215E Closing delimiter not found on <parm> command parameter <parm>

The issued command requires a closing delimiter on the parameter <parm>. Issue the command again, specifying a closing delimiter.

GSVC216E <parm> command parameter <???> is too long, the max length is <len>

The parameter <parm> is too long. <len> is the maximum length of the parameter. Issue the command again, specifying a parameter of valid length.

GSVC217E No parameters allowed on the <comname> command

The <comname> command has been issued with parameters. The command does not have any parameters. Issue the command again, without specifying any parameters.

GSVC218E <parmname> parameter required by <comname> command

The <comname> command requires the <parmname> parameter. Issue the command again, specifying the required parameter.

GSVC219E Closing delimiter not found on <parmname> parameter

This is a general purpose error message indicating that a parameter started with the character-delimiter character but no closing character-delimiter character was found.

GSVC220E String qualifier '_' not supported for <parmname> parameter

An unsupported character-string qualifier was used on the <parmname> parameter.

GSVC221E Invalid character delimiter usage in <parmname> parameter

An invalid character delimiter was found in the parameter.

GSVC222E <parm> parameter too long, max length is <len>

The parameter <parm> is too long. <len> is the maximum length of the parameter.

GSVC223E Keyword <keyword> is not valid on a SETDEFAULT entry

The specified keyword is not valid on a SETDEFAULT entry definition.

GSVC230I <workarea> <tran> <task#> <xm_txn> <tt> <exn> <dfhuepar>

Internal debugging message used with CICS global user exits.

• workarea - Work area
• tran - Transaction ID
• task# - Transaction number
• xm_txn - The address of the XM_TXN control block
• tt - TCB type
• exn - Exit number
• dfhuepar - The address of the DFHUEPAR control block

GSVC231I <workarea> <tran> <task#> <xm_txn> <tt> <exn> <elapsed> <cputime>

Internal debugging message used with CICS global user exits.

• workarea - Work area
• tran - Transaction ID
• task# - Transaction number
• xm_txn - The address of the XM_TXN control block
• tt - TCB type
• exn - Exit number
• elapsed - Elapsed time of request
• cputime - CPU time of request

GSVC240E <seckeyword> keyword invalid for <command> <keyword> command

The secondary keyword is invalid for the command and keyword.

GSVC241E <keyword> is not a valid keyword for the <command> command

The keyword specified with the command is not valid.

GSVC242E Keyword <keyword> is ambiguous - Specify more chars for exact match

The keyword is not long enough to be unique.

GSVC243E Invalid line command - <linecmd>

The line command is not a valid line command.

GSVC244E Line command <linecmd> ambiguous, enter more chars for exact match

Line command is not long enough to be unique.

GSVC245E Invalid subcommand - <subcommand>

The subcommand is invalid.

GSVC246E Subcommand <subcmd> is ambiguous, enter more chars for exact match

Subcommand is not long enough to be unique.

GSVC247E Keyword value required by <command> <keyword> command

This general purpose error message indicates that the command was issued with the keyword but the required value for the keyword was not supplied.

GSVC248E <errkwd> is not a valid <command> command <keyword> keyword

This is a general purpose error message indicating that an invalid keyword was supplied.

GSVC249E <valname> keyword value required by <command> <keyword> command

This is a general purpose error message indicating that a required keyword was omitted.

GSVC250E Keyword value required by <command> <keyword> command

A value is required when specifying the keyword.

GSVC251E <kwd2> keyword value required by <cmd> <kwd1> command

A value is required when specifying the keyword.

GSVC252E <kwd2> keyword invalid for <cmd> <kwd1> command

An invalid keyword was specified.

GSVC253E Value required by <kwd> keyword

A value is required for the specified keyword.

GSVC254E <parmname> value required by <kwd> keyword

A parameter value is required for the specified keyword.

GSVC255E <kwd> is not a valid keyword

The specified keyword is invalid.

GSVC256E <kwd> is not a valid <parmname> keyword

The specified keyword is not a valid parameter name keyword.

GSVC257E <kwd> keyword invalid for <kwd> keyword

An invalid keyword value has been specified.

GSVC258E Invalid keyword <keyword> specified

An invalid keyword value has been specified.

GSVC259E Invalid value for <keyword> keyword

A keyword was entered that requires a value. A value that was supplied is not valid.

GSVC261E Group [set the product group or family] is invalid

The group name specified is invalid.

GSVC262E Group type <type> is invalid

The definition for the group is invalid.

GSVC263E Group [set the product group or family] instance <instance> type <type> already exists

A request to create a new group has failed. The combination of group, instance, and type already exists.

GSVC264E Group [set the product group or family] instance <instance> type <type> was not found

The requested group does not exist.

GSVC265E Member <member> was not found in group [set the product group or family] instance <instance> type <type>

The <member> requested does not exist in the group.

GSVC266E Member <member> is already in group [set the product group or family] instance <instance> type <type>

A request has been made to add a member to a group. The member specified is already in the group.

GSVC267E Storage allocation for logical group failed

A request was made to allocate storage for a logical group. The request failed.

GSVC268I Group [set the product group or family] instance <instance> type <type> has been added

A new group has been created.

GSVC269I Member <member> added to group [set the product group or family] instance <instance> type <type>

A member has been added to an existing group.

GSVC270I Group [set the product group or family] instance <instance> type <type> has been deleted

A new group has been deleted.

GSVC271I Member <member> deleted from group [set the product group or family] instance <instance> type <type>

A member has been deleted from an existing group.

GSVC272E Group names of type <type> are limited to <len> characters

A length of the group name is limited to the specified number of characters.

GSVC273E Group type <type> does not allow excluded members

An attempt to add an exclude member was made to a group type that does not support exclude members.

GSVC274E Group [set the product group or family] was found but not with type <type>

The requested group does not exist as requested type

GSVC276E Group type <type> does not support an instance name

The requested group does not support an instance name.

GSVC280I Schedule events have been loaded from member <member>

Event scheduler definitions have been loaded from the specified parmlib member.

GSVC281I Schedule event processing has been <status>

Indicates the status of the event scheduler.

• status - Current status:
  • activated
  • inactivated
  • suspended
  • resumed

GSVC282I Schedule event <event> scheduled at <date><time> Interval <int>

An event has been scheduled.

• event - event name
• date - event date
• time - event time
• int - interval until event expires

GSVC283I Schedule event scan complete. Interval=<int>

The event scheduler has determined the interval until the next event.

• int - interval until event expiration

GSVC284I Schedule event <event> is being processed

An event has been processed.

• event - event name

GSVC285I Schedule event <event> has been <action>

An action was taken on an event.

• action - Action code:
  • created
  • modified
  • deleted
  • enabled
  • disabled

GSVC286I Schedule event <event> has not been scheduled

The event has not been scheduled for today.

GSVC288E Schedule event <event> was not found

A requested event was not found.

• event - event name

GSVC289E Schedule event <event> has invalid parm data

The event has invalid parameter data.

• event - event name

GSVC290E Schedule event <event> definition contains errors

The event definition contains invalid statements or keywords.

• event - event name

GSVC291E Schedule event <keyword> is invalid

The event definition contains invalid statements or keywords.

• keyword - keyword name

GSVC292I Function <function> is not supported via a LIST in schedule event <event>

The function specified cannot be specified as part of a LIST. The function must be scheduled as a primary event function.

GSVC300I SVC dump Requested

An abend has occurred. An SVC dump has been requested.

GSVC302E SDUMPX failed, rc <rc> rsn <rsn>

An abend has occurred. An SVC dump has been requested. The SDUMPX macro requested failed.

GSVC303E SDUMPX failed, <reason>

An abend has occurred. An SVC dump has been requested. The SDUMPX macro requested failed.

GSVC304W SDUMPX complete, some data not captured

An abend has occurred. An SVC dump has been requested. The SDUMPX is complete, but some data was not captured.

GSVC305I SDUMPX complete, SVC dump captured

An abend has occurred. An SVC dump has been requested. The SDUMPX is complete.

GSVC306I SDUMPX retry <cnt> of <limit> in <seconds> seconds

An abend has occurred. An SVC dump has been requested. The SVC dump capture process is currently busy. The SVC dump will be retried.

GSVC307E SDUMPX retry failed, <reason>

An abend has occurred. An SVC dump has been requested. The SVC dump capture process failed.

GSVC310E Exception definition for <metric> contains errors.

An exception definition is being processed. The definition contains errors.

GSVC311E Exception definition <keyword> is invalid

The exception definition contains invalid statements or keywords.

GSVC312E Exception definition for <metric> failed. <reason>

An attempt was made to define or change an exception definition. The reason for failure is included.

GSVC400I zIIP environment has been <status>

The zIIP environment has been enabled or disabled.

GSVC401I zIIP environment - Release <release>

The zIIP enviroment with the specified release has been loaded.

GSVC402W zIIP environment is not available

The zIIP environment services are not available. zIIP processing is disabled.

GSVC403I zIIP environment - <defined> <type> defined <online> online

The zIIP environment current has the specified number of processors defined and online.

GSVC404I Task <tasK> has been zIIP <status>

The task has been enabled or disabled for zIIP processing.

GSVC405E Task <tasK> zIIP service <service> failed. RC=<rc>

The zIIP service request has failed.

GSVC406I <module> <offset> zIIP <type> <service> State <state> Lvl <lvl>

This is zIIP service trace diagnostics message.

GSVC407W zIIP environment module <module> was not found

The zIIP environment module was not found. Validate that the module can be located via one of the following:

• Link Pack Area (LPA)
• Link list
• STEPLIB or JOBLIB concatenation

GSVC408W zIIP environment will be termined. <reason>

The zIIP environment will be terminated.

GSVC700I CA SYSVIEW for CICS initialization started

Initialization of the CICS data collector has started. This message is displayed when using the transaction GSVS.

GSVC701W CA SYSVIEW for CICS is already initialized

The transaction GSVS was used to issue a request to initialize the CICS data collector. The request failed because the collector was already active.

GSVC702I Please use transaction GSVS to initialize CA SYSVIEW for CICS

The transaction GSVI was used to attempt to initialize the CICS data collector. The GSVS transaction must be used to initialize the data collector.

GSVC703W CA SYSVIEW for CICS is not active

The transaction GSVT was used to attempt to terminate the CICS data collector. The request failed because the data collector was not active.

GSVC704I CA SYSVIEW for CICS is being terminated by request

The data collector was terminated by user request.

GSVC705E Error during initialization. CA SYSVIEW for CICS startup terminated

An error occurred during initialization of the data collector.

GSVC706E Error during initialization. Unable to locate the initialization program.

An error occurred during initialization of the data collector. The CICS transaction with program(GSVCGSVI) could not be found.

GSVC707E Request for restart aborted due to timeout waiting on termination

A request to restart the data collector has failed. A timeout has occurred while waiting for the executing data collector to terminate.

GSVC708I CA SYSVIEW for CICS is being restarted by request

The data collector is being restarted by user request.

GSVC900E Initialization has terminated due to error. Return code = <rc>

An error occurred during initialization.

Return codes and description

• 000 x0000 - Okay
• 008 x0008 - Could not locate DFHSIP TCB
• 016 x0010 - SVC validation failed
• 020 x0014 - CICS data logger has not been initialized
• 028 x001C - Not authorized for CICS component
• 032 x0020 - Invalid release of CICS or MVS
• 036 x0024 - Error during buffer allocation
• 040 x0028 - Error activating subtasks
• 048 x0030 - Error initializing SVC services
• 052 x0034 - A module build mismatch has been detected
• 060 x003C - Unable to locate system configuration
• 064 x0040 - Unable to locate anchor table
• 068 x0044 - Unable to locate subsystem
• 072 x0048 - Allocation of RMCA failed
• 076 x004C - MEIX allocation failed
• 080 x0050 - VAT allocation failed
• 084 x0054 - VAT not found
• 088 x0058 - VAT invalid
• 092 x005C - CAAT allocation
• 096 x0060 - CAAT not found
• 100 x0064 - CAAT invalid

GSVC901I CA SYSVIEW for CICS shutdown started

Termination of the CICS data collector has started.

GSVC902W Monitor activation was disallowed by request

The activation of the monitor was disallowed by site request.

GSVC910I Address <address> Length <length> <text>

An unexpected abend has occurred. Messages GSVC910, 911, and 912 are displayed with debugging information.

GSVC911I Offset-- ------+0 ------+4 ------+8 ------+C *---Characters---*

An unexpected abend has occurred. Messages GSVC910, 911, and 912 are displayed with debugging information.

GSVC912I_______ ______ ________ _______ _______ _______ _______

An unexpected abend has occurred. Messages GSVC910, 911, and 912 are displayed with debugging information.

GSVC920I<statistics statistics information>

Statistics information message used to display shutdown statistics during termination.

GSVC921I<process> process> termination started

Termination has started for the specified process.

GSVC922I<process> process> termination complete

Termination has completed for the specified process.

GSVC990E CA SYSVIEW for CICS r<release> Abend Information

An abend has occurred in the CICS data collector.

GSVC991E Task <subtask> Module <module> Offset <offset>

This message further describes the abend in message GSVC990E.

• <subtask> - Subtask in which the abend occurred
• <module> <offset> - Module name and offset of PSW at abend

GSVC992E Abend <code> PSW <program-status-word>

This message further describes the abend in message GSVC990E. The PSW (program status word) at the time of the abend.

• <code> - Completion code
• <psw> - Program Status Word
• <ilc> - Instruction length
• <intc> - Interrupt code

GSVC993E AR/GR ®: <AR00/GR00> ®: <AR01/GR01>

This message further describes the abend in message GSVC990E. This message is displayed eight times during an abend. Each message displays the value of two registers at the time of the abend.

GSVC995E AR/GR ®: <AR00/GR00> ®: <AR01/GR01>

This message further describes the abend in message GSVC990E. This message is displayed eight times during an abend. Each message displays the value of two grande registers at the time of the abend.

GSVC996E <message>

An abend has occurred. This message will be displayed prior to the GSVC993 or GSVC995 message indicating the type of registers being displayed.

• Registers at entry to abend
• Registers at time of interrupt

GSVC997E User <userid> Group [set the product group or family] Profile <profile> Session <interface> <session> Function <request>

An abend has occurred. This message will be displayed if the abend has occurred as part of a user session request.

GSVC998E End of symptom dump

An abend has occurred. This is the last message in the group.

GSVC999I CA SYSVIEW for CICS terminated

This is notification that the CICS data collector has terminated.