Server Space Messages › TN34 Messages

TN34 Messages

TN3401E Failure issuing QEDIT macro

Reason:

During server space initialization, a failure occurred issuing the QEDIT macro.

Action:

The server address space initialization continues. Communication with the server space will not be possible via the Modify command. Contact Customer Support.

Origin: TNSMDFY

TN3402E Invalid wakeup call

Reason:

During server space operation, a POST was issued to the modify command processor. The correct post code was not specified.

Action:

Operation continues.

Origin: TNSMDFY

TN3403I CA MAT now in XDC mode

Reason:

CA Mainframe Application Tuner has processed the DIEXDC modify command. Use of this command is for internal debugging purposes. It should only be used at the direction of Customer Support.

Action:

CA Mainframe Application Tuner continues operation in diagnostic mode.

Origin: TNSMDFY

TN3404E Invalid MODIFY command for CA MAT

Reason:

An invalid command was entered using the MVS MOFIFY (F) command interface. The full text of the invalid command that was entered follows this message. Valid commands are:

Action:

The input is ignored. Reenter the MODIFY command using the proper command name.

Origin: TNSMDFY

TN3405I Valid commands are: PERFORM, FORce, RELoad, SOFt, TRAce, UXIt

Reason:

These are the valid commands accepted by the modify command processor. This message follows TN3404E when an invalid command is entered.

Action:

The input is ignored. Reenter the MODIFY command using the proper command name.

Origin: TNSMDFY

TN3406I Too many MODIFY tokens; only the first five were used

Reason:

More than five tokens were entered on the z/OS MOFIFY (F) command line. Only the first five were accepted.

Action:

The extra input is ignored by the MODIFY process.

The information entered on the MODIFY command was probably incorrect and might need to be reentered. However, the MODIFY process continued with the five tokens that WERE entered. There might be other diagnostic messages besides this one to explain what further action, if any, that needs to be taken.

Origin: TNSMDFY

TN3410I CA MAT module nnnnnnnn loaded at aaaaaaaa ssssssss

Reason:

Either during server space initialization or during the execution of the reload command, the module mmmmmmmm was loaded at virtual address aaaaaaaa. The server space name is ssssssss.

Action:

Operation continues.

Origin: TNSRLOD

TN3411E Unable to load TNELOAD or TNEDIER

Reason:

During initialization of the CA Mainframe Application Tuner, the required routines, TNELOAD and TNEDIER, were not available to be loaded. CA Mainframe Application Tuner cannot be initialized.

Action:

CA Mainframe Application Tuner initialization is discontinued. Contact Customer Support.

Origin: TNSRLOD

TN3421I FORCE command received for profile: pppppppp

Reason:

The modify command processor received a FORCE command to immediately terminate a monitor request.

This message is a result of the modify command 'F SERVER,FORCE profile' being issued by someone with authorization to issue commands from the MVS console. SERVER represents the name of the server space and profile represents the name of the monitor profile to take the FORCE action against.

Action:

The monitor request is terminated immediately (it is not shut down in an orderly fashion - it is forcibly cancelled).

Origin: TNSKILL

TN3422I FORCE successfully completed for profile: pppppppp

Reason:

The modify command processor received a FORCE command to immediately terminate a monitor request. This message indicates that the monitor request was posted to terminate.

Action:

The monitor request is terminated immediately (it is not shut down in an orderly fashion - it is forcibly cancelled).

Origin: TNSKILL

TN3423W FORCE command did not find profile: pppppppp

Reason:

The modify command processor received a FORCE command to immediately terminate a monitor request but it could not locate a monitor request with the profile name of pppppppp.

This message is a result of the modify command 'F SERVER,FORCE profile' being issued by someone with authorization to issue commands from the MVS console. SERVER represents the name of the server space and profile represents the name of the monitor profile to take the FORCE action against.

Action:

The FORCE command is ignored.

Ensure the correct profile name is specified and that the command is issued against the correct Started Task name.

Origin: TNSKILL

TN3424I TRACE command processed for: tttt

Reason:

This message is a result of the modify command 'F SERVER,TRACE tttt' being issued by someone with authorization to issue commands from the MVS console. SERVER represents the name of the server space and tttt indicates the trace type.

This command enables a single trace type whenever CA Mainframe Application Tuner monitors a job step. Valid trace types are:

Action:

The trace is started for any current and subsequent monitors and remains in effect until a TRACE,OFF request is received.

Origin: TNSTRAC

TN3425W Invalid TRACE operand entered -- valid operands are IMS CICS DB2 USER L1 L2 L3 L4 DCM 4GL and OFF

Reason:

An invalid trace command was entered.

This message is a result of the modify command 'F SERVER,TRACE tttt' being issued by someone with authorization to issue commands from the MVS console. SERVER represents the name of the server space and tttt indicates the trace type. Valid trace types are:

Action:

The trace is not started. Correctly enter the TRACE command and specify a valid trace type.

Origin: TNSTRAC

TN3426I SOFT command processed for ONOFF

Reason:

This message is a result of the modify command 'F SERVER,SOFT ON/OFF' being issued by someone with authorization to issue commands from the MVS console (where SERVER is the name of the server task).

This command 'SOFT ON' causes CA Mainframe Application Tuner to produce a system dump for errors that are otherwise recoverable. CA Mainframe Application Tuner considers these as soft errors. This command should only be used at the direction of Customer Support to gather detailed diagnostic information about a problem.

The command 'SOFT OFF' causes CA Mainframe Application Tuner to process errors normally.

Action:

A dump is produced for abends that would otherwise be recoverable by CA Mainframe Application Tuner. Only one dump is produced and the request is terminated.

Origin: TNSSOFT

TN3427W Invalid SOFT operand entered -- valid operands are ON and OFF

An invalid SOFT command was entered. Valid SOFT operands are:

ON

Enables a dump to be taken for a soft error

OFF

Reverts back to soft error handling

Action:

The command is ignored. Ensure a correct operand is specified.

Origin: TNSSOFT

TN3428I ACTivate command processed for xxxxxxxx

Reason:

This message is a result of the modify command 'F SERVER,ACT xxxxxxxx' being issued by someone with authorization to issue commands from the MVS console.

This command 'ACTivate xxxxxxxx' causes CA Mainframe Application Tuner to activate an application specified by xxxxxxxx. For example: ACT EXPLAIN will activate the DB2 EXPLAIN function. This command should only be used at the direction of Customer Support to activate a special feature before it is released.

Action:

A special feature specified by xxxxxxxx is activated.

Origin: TNSMACT

TN3429I INACT command processed for xxxxxxxx

Reason:

This message is a result of the modify command 'F CA MAT,INAct' being issued by someone with authorization to issue commands from the MVS console.

Action:

The INACT command causes CA Mainframe Application Tuner to disable an application that was previously activated by the ACTivate command. The specific feature that was activated by the ACTivate command will be disabled.

Origin: TNSMACT

TN3430W Invalid ACT operand entered -- 1-8 bytes operand required

Reason:

An invalid ACT command was entered. ACTivate command needs to specify a 1-8 bytes operand, which is to identify the feature to be activated.

Action:

The command is ignored. Ensure a correct operand is specified.

Origin: TNSMACT

TN3431I HARvester command processed for: xxxxxxxx

Reason:

The MODIFY HARvester command was processed.

Action:

None. Contact Customer Support.

Origin: TNSINTR

TN3432W Invalid HARvester operand entered: xxxxxxxxxxxx

Reason:

The MODIFY HARvester command has an invalid operand.

Action:

The command was not processed.

Check for spelling errors or syntax and re-enter the command. Contact Customer Support.

Origin: TNSINTR

TN3433W DB2HVEPT=YES not specified at server start. Command can not be processed.

Reason:

DB2HVEPT must be set to YES at server start before the requested command can be processed.

Action:

The command is not processed.

Re start the server with DB2HVEPT=YES or specify the HARvester MODIFY command for SETFLAG,DB2HVEPT,YES

If the problem persists, contact Customer Support.

Origin: TNSINTR

TN3435W The DB2 HARvester command failed for DB2 xxxx Return xxxxxxxx Reason xxxxxxxx.

Reason:

The START HARvester command failed for the specified DB2 system.

Action:

The DB2 Harvester is not activated.

Insure that the specified DB2 subsystem is fully active and that the CA Mainframe Application Tuner data set is APF authorized.

If the problem persists, contact Customer Support.

Origin: TNSINTR

TN3436W The DB2 Subsystem appears to already be harvesting by this server. DB2 xxxx

Reason:

The START HARvester command found the DB2 subsystem had an entry in the internal Harvester table.

Action:

The DB2 Harvester is not activated.

Issue the HARvester START command with the FORCE parameter. If the problem persists, contact Customer Support.

Origin: TNSINTR

TN3437W The DB2 Subsystem Harvesting seed appears to not have been planted by this server. DB2 xxxx

Reason:

The STOP HARvester command did not find the DB2 subsystem name in the internal Harvester table.

Action:

The DB2 Harvester is not deactivated.

Issue the HARvester STOP command with the FORCE parameter. If the problem persists, contact Customer Support.

Origin: TNSINTR

TN3438W Harvester Abend xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx pppppppp jjjjjjjj

Reason:

The Harvester routine has suffered an ABEND for Profile pppppppp and job jjjjjjjj.

Action:

The DB2 Harvester continues processing.

Contact Customer Support with the information supplied in the message. If the problem persists, contact Customer Support.

Origin: TNMMAIN

TN3439I Harvester processing continues. pppppppp jjjjjjjj

Reason:

The Harvester routine has suffered an ABEND for Profile pppppppp and job jjjjjjjj and the maximum ABEND count has not been reached.

Action:

The DB2 Harvester continues processing.

Notify Customer Support with the information in message TN3438W.

Origin: TNMMAIN

TN3440W Max Harvester ABEND count has been exceeded. Harvesting processing ended for pppppppp jjjjjjjj.

Reason:

The Harvester routine has suffered multiple ABENDs and has reached or exceeded the value specified by DB2HVMXA at server start up. DB2 harvesting for profile pppppppp job jjjjjjjj has terminated.

Action:

The DB2 Harvester terminates for this monitor.

Notify Customer Support with the information in message TN3438W.

Origin: TNMMAIN

TN3441W Max Harvester ABEND message count exceeded for pppppppp jjjjjjjj.

Reason:

The Harvester routine has suffered multiple ABENDs and has reached or exceeded the value specified by DB2HVMXM at server start up. DB2 harvesting for profile pppppppp job jjjjjjjj will continue until DB2HVMXA is reached but no additional ABEND messages will be displayed.

Action:

The DB2 Harvester continues for this monitor.

Notify Customer Support with the information in message TN3438W.

Origin: TNMMAIN

TN3442W This CA MAT command can not be processed through the MODIFY facility. Xxxxxxxx

Reason:

The Harvester command SETFLAG option found that the parameter specified was not eligible for modification.

Action:

The option is not changed.

The only way to change this option is through the TUNSSPxx member at server startup. If the problem persists, contact Customer Support.

Origin: TNSINTR

TN3443I The old setting for xxxxxxxx was xxxxxxxx

Reason:

The Harvester command SETFLAG option found that the current setting for xxxxxxxx was xxxxxxxx.

Action:

This message will be accompanied by message TN3444I with the new setting.

Origin: TNSINTR

TN3444I The new setting for xxxxxxxx is xxxxxxxx

Reason:

The Harvester command SETFLAG option has modified the setting for xxxxxxxx and the new value is xxxxxxxx.

Action:

This message will be accompanied by message TN3443I with the old setting.

Origin: TNSINTR

TN3445I The setting for xxxxxxxx is xxxxxxxx

Reason:

The Harvester command SHOWFLAG option will display the current setting for xxxxxxxx. The value is xxxxxxxx.

Action:

This message is displayed when the SHOWFLAG HARvester command is issued or when no value is specified in the SETFLAG command.

Origin: TNSINTR

TN3446I Harvesting has been requested using the old intercept facility. Use the MODIFY INTercept command.

Reason:

The MODIFY HARVESTER command is not valid when DB2ICOLD=YES has been specified. Use the MODIFY INTercept command instead.

Action:

The command is not processed. Re-enter the command using MODIFY INTercept.

Origin: TNSHRVR

TN3447E EXIT conflict. xxxxxxxx and yyyyyyyy are mutually exclusive. Command rejected.

Reason:

The MODIFY HARVESTER command is not valid because EXIT xxxxxxxx also includes EXIT yyyyyyyy and yyyyyyyy is already active on this system.

Action:

The command is not processed.

Re-enter the command or ignore this message.

Origin: TNSHRVR