|
|
|
Reason:
The file transfer schedule P1 is inactive, and the next scheduled start is described by P2 .
System Action:
None.
User Action:
None.
Reason:
The file transfer schedule is inactive and its checkpoint dataset does not contain any entries.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the Schedule Checkpoint dataset failed. The above
Retcode and VSAM error code were generated.
System Action:
The request is rejected.
User Action:
Interpret the error code using the VSAM Programmer Manual.
Reason:
The time interval in the Longest Transfer field cannot be greater than that in the Processing Period field.
System Action:
The Longest Transfer field is highlighted.
User Action:
Either decrease the value in the Longest Transfer field or increase the value in the Processing Period field.
Reason:
You cancelled the updates you made to the file transfer schedule entries on the Schedule Entries List panel.
System Action:
The updates are not retained.
User Action:
None
Reason:
The Repeat action tries to add a file transfer schedule entry. However, the definition already contains the maximum number of entries and cannot accept another entry.
System Action:
The action is disallowed.
User Action:
None
Reason:
The value, P1 , in the Day/Date or Criteria Name field is not valid.
The valid day values are:
MON TUE WED THU FRI SAT SUN
The valid date formats are:
- dd-MMM-yyyy (for example, 31-JAN-1998)
- dd-MMM , indicating a date for any year
- dd , indicating a date for any month and year
To display the list of valid criteria names, enter ? in the field.
System Action:
The field is highlighted.
User Action:
Enter a value in one of the valid forms.
Reason:
The highlighted file transfer schedule entry is the same as another entry.
System Action:
The duplicate is highlighted.
User Action:
Either delete the duplicate, or change the value in its Day/Date or
Criteria Name field or in its Start Time field such that it is no longer a duplicate.
Reason:
The time value, P1 , is not valid. A time value must be of the form
hh.mm , where hh is from 0 through 23 and mm is from 0 through 59.
System Action:
The field in error is highlighted.
User Action:
Enter a valid time value.
Reason:
The Maximum File Size specified must be greater than or equal to the Minimum File size previously specified.
System Action:
The Maximum File Size field is highlighted.
User Action:
Either increase the value in the Maximum File Size field or decrease the value in the Minimum File Size field.
Reason:
Valid values for this field are ID (Transfer Id), SRC (Source), TGT (Target) or CTL (Control). I, S, T, or C are also acceptable.
System Action:
The field in error is highlighted.
User Action:
Enter one of the valid type values.
Reason:
You cancelled the updates you made to the file filter entries on the File Filters List panel.
System Action:
The updates are not retained.
User Action:
None
Reason:
The Repeat action tries to add a file filter entry. However, the definition already contains the maximum number of entries and cannot accept another entry.
System Action:
The action is disallowed.
User Action:
None
Reason:
A CTL filter entry must use a valid dataset name or a DDNAME with no embedded wildcard characters. If DDNAMEs are used it must be in the format DD(ddname) or DDNAME(ddname).
System Action:
Request rejected.
User Action:
Provide a valid dataset name. The dataset name should be in uppercase.
Reason:
Duplicate dataset names not allowed for CTL entries.
System Action:
The action is disallowed.
User Action:
Review the list of filters or check the spelling of the dataset name for this CTL entry.
Reason:
Quotes are not allowed in any of the file filter attribute fields.
System Action:
None.
User Action:
Correct the entry.
Reason:
A CTL filter entry must use a valid dataset name or a DDNAME with no embedded wildcard characters. If DDNAMEs are used it must be in the format DD(ddname) or DDNAME(ddname).
System Action:
Request rejected.
User Action:
Correct the entry.
Reason:
A CTL filter entry must use a valid dataset name or a DDNAME with no embedded wildcard characters. If DDNAMEs are used it must be in the format DD(ddname(member- name)) or DDNAME(ddname(member-name)).
System Action:
Request rejected.
User Action:
Correct the entry.
Reason:
The filter specification is incomplete. The source data, target data, transfer ID, or CTL file must be identified.
System Action:
The field in error is highlighted.
User Action:
Specify a value in the Source Data or Target Data or Transfer ID field.
To remove a filter entry, you must clear all its fields.
Reason:
A required parameter was not available when this procedure was invoked.
System Action:
Procedure is terminated.
User Action:
Check the parameters used to invoke this procedure.
Reason:
An invalid option was used to invoke this procedure.
System Action:
Procedure is terminated.
User Action:
Check the parameters used to invoke this procedure.
Reason:
The specified file name is too large.
System Action:
None.
User Action:
Correct the FILENAME entry in the CTL file. You can use the wildcard characters % to specify a larger file name.
Reason:
The select CTL file has no entries.
System Action:
None.
User Action:
Verify the contents of the file selected.
Reason:
A file filter requires either a filename or a process ID.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
A CTL file cannot contain CTL entires.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
A file filter TYPE was not supplied or is invalid. Valid values for TYPE are 'TGT', 'SRC' and 'ID'.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
A non-numeric value was supplied for MINSIZE/MAXSIZE.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
The MAXSIZE value was less than the MINSIZE value.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
A negative numeric value was specified in keywords MINSIZE, MAXSIZE, or NUMBER.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
A check of the CTL entry was successful.
System Action:
None.
User Action:
None.
Reason:
An error was detected while evaluating a CTL entry.
System Action:
The action is disallowed.
User Action:
Select 'V' or 'CHK' on the CTL entry in error to determine the cause.
Reason:
The expansion of the file filter list exceeds the maximum number of 99 entries.
System Action:
The action is disallowed.
User Action:
Review all file filters and reduce the number of entries to 99.
Reason:
The upper limit for parameter P2 has been exceeded.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
Quotes are not allowed in any of the CTL keywords.
System Action:
None.
User Action:
Correct the FILTER entry in the CTL file.
Reason:
The select CTL file has no FILTER entries.
System Action:
None.
User Action:
Verify the contents of the file selected and ensure that at least 1 FILTER statement exists.
Reason:
A value must be entered in field P1 .
System Action:
The field in error is highlighted.
User Action:
Enter a value for the field.
Reason:
The value P2 is not permitted in the P1 field.
System Action:
The P1 field is highlighted.
User Action:
Enter a valid value for the field.
Reason:
The ruleset with the name P1 is not in the database.
System Action:
The field in error is highlighted.
User Action:
Enter ? (question mark) in the highlighted field to list the rulesets in the database and select one.
Reason:
The value in the File Name field contains the * or ? character. These characters are invalid in that field.
System Action:
The field in error is highlighted.
User Action:
Use the following wildcard characters to match file names that contain disallowed characters:
% (percent) matches any string of characters
_ (underscore) matches a single character
Reason:
The value P1 is invalid in the User List field. The field value must be a userid or list of userids separated by commas. Each userid may consist of alphabetic, numeric and national ($, @, #) characters only. Spaces are permitted between values, but are not required.
System Action:
The field in error is highlighted.
User Action:
With the cursor in the field, press F1 to display the Help. Correct the value that is in error.
Reason:
When the Allow Request field is set to NO the Log field cannot be set to FAIL. The 'FAIL' only occurs when Allow Request is set to YES and a request is disallowed by the external security facility.
System Action:
The field in error is highlighted.
User Action:
Correct the value.
Reason:
The low and high remote IP addresses are incorrectly ordered.
System Action:
The field in error is highlighted.
User Action:
Ensure that the value in the Remote IP Address [low] field is less than the value in the Remote IP Address [High] field.
Reason:
The P1 ruleset already exists in the database.
System Action:
The error is highlighted.
User Action:
Specify a name that has not been used for an FTP policy ruleset.
Reason:
The user P2 is currently maintaining the P1 FTP policy ruleset. Only one user can maintain the a ruleset at a time.
System Action:
Your request is rejected.
User Action:
Wait until the other user has finished with the ruleset, then retry.
Reason:
The P1 FTP policy ruleset was successfully loaded in the SSI.
System Action:
None.
User Action:
None.
Reason:
The P1 FTP policy ruleset failed to load.
System Action:
The ruleset is not loaded in the SSI.
User Action:
See the activity log for detailed messages on why the ruleset failed to load. To access the log, enter the $LOG command from any panel.
Reason:
The P1 FTP policy ruleset failed to load because there was not enough space in the configuration area in the SSI.
System Action:
The ruleset is not loaded. Any previously loaded ruleset remains in effect.
User Action:
Reduce the number of rules in the P1 ruleset, and retry. If the problem persists contact Technical Support.
Reason:
The P1 FTP policy ruleset failed to load because there are no rules in the ruleset.
System Action:
The request is denied.
User Action:
Load a policy ruleset that contains rules.
Reason:
A SAF call to your external security subsystem (RACF, ACF2, or Top Secret) was made for READ, UPDATE, or ALTER access to the FTP policy ruleset and rule definitions.
The SAF resource that is checked to determine access to the definitions is a FACILITY class rule named $SOLVE.FTP.CONTROL .
Your user ID was denied the level of access requested. The levels are as follows:
- READ access is required to browse definitions
- UPDATE access is required to update definitions
- ALTER access is required to add, delete and load definitions
SAF security must be defined before you can use the FTP policy functions.
System Action:
The request is denied.
User Action:
Check the activity log for any additional details about this failure. Provide this information to your security administrator.
To set up SAF security for the FTP policy functions, add a FACILITY class rule called $SOLVE.FTP.CONTROL , then provide permissions to the users of the FTP policy functions.
Reason:
If the value of the Allow Request? field is NO, matched FTP requests are disallowed and the SAF Qualifier field serves no purpose.
System Action:
The field in error is highlighted.
User Action:
If FTP requests are to be disallowed based on the matching criteria alone, remove the value in the SAF Qualifier field.
Reason:
The request cannot be processed when the SSI is inactive.
System Action:
None.
User Action:
To perform this action, start the data space manager task first (for example, S SOLVESSI).
Reason:
While creating an FTP policy ruleset, you pressed F6 (Rules) before saving the ruleset definition. Your ruleset has not been created yet.
System Action:
None.
User Action:
Press F4 (Save), then press F6 (Rules).
Reason:
While creating an FTP policy ruleset, you pressed F6 (Rules) before you complete the Name field.
System Action:
None.
User Action:
Create your ruleset, then press F6 (Rules).
Reason:
The P1 FTP policy ruleset failed to load because another load is in progress by the user ID specified in P2 on the region specified in P3 .
System Action:
The request is denied.
User Action:
Contact the specified user or wait and retry to load this ruleset.
Reason:
A SAF call to verify access to the $SOLVE.FTP.CONTROL resource definition has completed. The requested access level was permitted.
System Action:
Processing continues.
User Action:
None.
Reason:
A SAF call to verify access to the $SOLVE.FTP.CONTROL resource definition has failed.
RC displays the return code from the SAF interface (UTIL0039).
SFRC displays the sub-function return code.
SFREAS displays the sub-function reason code.
ENV displays environmental information.
The most common RC and SFRC combinations are:
04 PROGRAM ACTIVATION FAILURE
04 Program not APF-authorized
08 Invalid parameter
0C Missing parameter
10 Parameters inconsistent
08 SAF INTERFACE FAILURE
SAF/RACROUTE RETURN CODES:
04 Requested function was not processed
08 Requested function was processed, but failed
12 ACCESS VERIFICATION FAILURE
RACROUTE REQUEST=VERIFY CODES:
04 No security profile defined
08 Password invalid
0C Password expired
10 New password invalid
14 Group definition is missing
18 Security exit denied access
1C User temporarily revoked
20 Security system not active
24 Access to group is closed
?? others as per specific security system
16 ACCESS AUTHORIZATION FAILURE
RACROUTE REQUEST=AUTH CODES:
04 Resource is not security protected
08 Resource access not allowed
99 NO ENTRY PARAMETERS
System Action:
The user access request is denied.
User Action:
Contact your system administrator. Use the displayed codes and messages to investigate the cause of the error.
You also need the following documentation:
Ensure that:
Reason:
A user has attempted to access the $SOLVE.FTP.CONTROL resource definition. A SAF call was done to check the user's authority level, but failed because the necessary resource is not defined to SAF.
System Action:
All requests, by all users, for any level of access (including READ) to the $SOLVE.FTP.CONTROL resource will be rejected. Requests will only be allowed when the necessary resources and access permissions are defined to SAF.
User Action:
Ask your Security Administrator to define the $SOLVE.FTP.CONTROL resource profile to SAF. Until this is completed, all access requests (even read-only ones) are denied.
Reason:
A user has attempted to access the $SOLVE.FTP.CONTROL resource definitions. A SAF call was done to check the user's authority level. This user does not have the level of access required to perform the function they requested. This message is followed by RF38SEC004, which lists the user ID and requested access.
System Action:
The request is rejected.
User Action:
Ask your security administrator to give this user ID the required level of access to the $SOLVE.FTP.CONTROL FACILITY class rule.
For information about defining $SOLVE.FTP.CONTROL to your external SAF security system (CA ACF2, CA Top Secret, or RACF), see the CA NetMaster File Transfer Management Administration Guide.
Reason:
This message is written to the Activity Log following any SAF check failure messages. It contains the parameters used by the failing SAF RACROUTE REQUEST=VERIFY macro call. These parameters may include:
USRID - the user ID requesting access to $SOLVE.FTP.CONTROL
GRPID - the user ID's SAF default group
CHKENV - the SAF checking environment (APPL|USER|FULL)
ACCTYP - the access type requested (READ|UPDATE|ALTER)
RSNAME - the SAF resource name
RSCLSS - the SAF class
System Action:
None.
User Action:
Use this information, combined with the information in the previous error message, to determine the cause of the error. For more specific information, see the User Action in the previous error message.
Reason:
There are no queued Auto Connects which match the List Names defined in the monitor definition.
System Action:
None.
User Action:
None.
Reason:
The List Name specified by P1 has been successfully deleted by the user specified by P2 .
System Action:
The List Name is deleted from the Auto Connect queue.
User Action:
None.
Reason:
The command is not supported by CONNECT:Direct for P1 .
System Action:
The command is rejected.
User Action:
None
Reason:
The Auto Connect Queue Monitor has issued a heartbeat to the CONNECT:Mailbox STC and has not received a response.
System Action:
None.
User Action:
None.
Reason:
The Auto Connect Queue Monitor has found that the number of queued Auto Connects does not exceed the threshold defined in the monitor definition. P1 is the current count of the Auto Connect Queue. P2 is the time the monitor performed the heartbeat.
System Action:
None.
User Action:
None.
Reason:
The Auto Connect Queue Monitor has found that the number of queued Auto Connects exceeds the threshold defined in the monitor definition. P1 is the current count of the Auto Connect Queue. P2 is the time the monitor performed the heartbeat.
System Action:
The Monitor is set to a degraded state under ResourceView and an alert is sent to the Alert Monitor.
User Action:
Issue the display command to check the Auto Connect Queue.
Reason:
No records were found for this list.
System Action:
None.
User Action:
None.
Reason:
You performed an action that is in conflict with another action.
System Action:
The action that caused the conflict is highlighted.
User Action:
Review your actions, and correct the error.
Reason:
There are no BSC Lines which match the BSC Lines defined in the monitor definition.
System Action:
None.
User Action:
None.
Reason:
The BSC Line specified by P1 has been successfully stopped by the user specified by P2.
System Action:
The BSC Line is closed.
User Action:
None.
Reason:
The BSC Line specified by P1 has been successfully started by the user specified by P2.
System Action:
The BSC Line is started.
User Action:
None.
Reason:
The BSC Line specified by P1 has failed to stop as it was not running at the time the command was issued.
System Action:
None.
User Action:
None.
Reason:
The BSC Line Monitor has automatically restarted line P1 as the monitor field Automatic Restart? is set to YES. The restart has completed successfully.
System Action:
None.
User Action:
None.
Reason:
The BSC Line Monitor has attempted to automatically restart line P1 as the monitor field Automatic Restart? is set to YES. The restart has failed with the error P2.
System Action:
None.
User Action:
Investigate the cause of the failure. Enter CMMSG at the command prompt for additional message help for the error P2.
Reason:
The BSC Line Monitor has issued a heartbeat to the CONNECT:Mailbox STC and has not received a response.
System Action:
None.
User Action:
None.
Reason:
The BSC Line Monitor has found there are no BSC lines in a status of CLOSED. P1 is the current number of BSC Lines. P2 is the time the monitor performed the heartbeat.
System Action:
None.
User Action:
None.
Reason:
The BSC Line Monitor has found P1 BSC Lines and P2 have a status of CLOSED. P3 is the time the monitor performed the heartbeat.
System Action:
The monitor is set to a degraded state under ResourceView and an alert is sent to the Alert Monitor.
User Action:
Issue the display command to check which BSC Lines are in a closed status.
Reason:
The BSC Line Monitor has not found BSC lines that match the BSC lines defined in the monitor. P1 is the time the monitor performed the heartbeat.
System Action:
None.
User Action:
Check the monitor definition as it may be incorrect.
Reason:
THE CONNECT:Direct API procedure was invoked without the required keyword(s) identified by P1.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Supply the required keyword parameter(s).
Reason:
THE CONNECT:Direct API procedure was invoked with an invalid value, identified by P1 for the keyword parameter identified by P2
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Correct the invalid keyword parameter.
Reason:
A command was issued for a CDMGR resource of type P1 , but the command is not supported by a resource of that type.
System Action:
The request is rejected.
User Action:
None
Reason:
The SOLVE-CONNECT:Direct interface was called, but the subsystem which enables the interface is not active.
System Action:
The request is rejected with a return code of 8.
User Action:
Enable the interface using SUBSYS START as per the installation instructions.
Reason:
Service procedure P1 was invoked with an invalid value for the keyword, P2 , of P3 .
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
A signon attempt to CONNECT:Direct was cancelled at the user's request.
System Action:
Signon is terminated.
User Action:
None.
Reason:
The CONNECT:Direct interface was called, but the R15 response from DMCHLAPI ( P1 ) was not the expected value. The returned and expected values are both shown in hexadecimal format. The expected value ( P2 ) is:
- X'00000014' (decimal 20) for SIGNOFF
- X'00000000' (decimal 0) for all other commands
System Action:
The request is rejected with a return code of 12.
User Action:
This message may be issued when the CONNECT:Direct region is inactive or not functioning normally. Check to see if there are such problems, and resolve them.
If the CONNECT:Direct region is functioning as expected, this message may indicate a problem in the CONNECT:Direct definitions in the this region. Review the $RF CDAPI parameter group, and check that the specified values are correct.
The use of the CONNECT:Direct programming interface, DMCHLAPI, is described in the CONNECT:Direct for MVS Installation and Administration Guide, in the chapter, Using the Programming Interface. Associated return codes are listed in the section, DMCHLAPI Return Codes.
See the above reference for a technical explanation of the return code. If the cause of the problem is not apparent, contact Technical Support.
Reason:
The SOLVE-CONNECT:Direct interface was called with a command (variable), but the command is null (that is, zero length).
System Action:
The request is rejected with a return code of 8.
User Action:
Contact your local support representative.
Reason:
The SOLVE-CONNECT:Direct interface is called with CONNECT:Direct output specifications (OUTSPECS), which default to NNNNNNN. These specifications may be overridden by specifying a 7-character string as the second parameter when the SOLVE- CONNECT:Direct interface is called. A second parameter was specified, but it was neither null nor 7-characters long.
System Action:
The request is rejected with a return code of 8.
User Action:
Contact your local support representative.
Reason:
The CONNECT:Direct interface was called. The subsystem which enables the interface is active, but the CONNECT:Direct API failed to load when the SOLVE region initializes. The load module name is P1 , and R0 and R15 from the LOAD instruction are P2 and P3 respectively.
System Action:
The request is rejected with a return code of 8.
User Action:
Ensure that the module name is correct (DMCHLAPI).
If it is correct, use the R0 and R15 return codes to determine the cause of the error.
A common error is 806, which indicates that the module could not be found in the load library list (that is, the list of libraries in the STEPLIB). Ensure that the CONNECT:Direct load library (for example, $CD.V2101.LINKLIB) is included in either the STEPLIB or the system link list.
Notes: - All libraries included in the STEPLIB must be APF authorized.
- If the STEPLIB is changed, you must restart this region.
- The CONNECT:Direct API program, DMCHLAPI, may require other load modules which are usually present in the same CONNECT:Direct load library.
- The API program is loaded as a result of the SUBSYS DEFINE command when this region initializes. To reload the program, the region must be terminated and restarted.
Reason:
This message displays the result of a CONNECT:Direct command issued through the CONNECT:Direct API
P1 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
THE CONNECT:Direct Command Interface procedure was invoked without the required keyword(s) identified by P1.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Supply the required keyword parameter(s). If the missing keyword is either USERID or PASSWORD go to option A.C.P and check the CDAPI parameter group. Ensure that the USERID and PASSWORD are specified and action (F6) the group to cause these values to be set.
Reason:
The CONNECT:Direct command interface procedure was invoked for a CDMGR but was unable to ascertain the values for the NETMAP and MSGFIL datasets. The file names which could not be derived are identified by P1 , while P2 identifies the CONNECT:Direct manager.
The reason for the failure could be because the INQUIRE INITPARMS command issued to CONNECT:Direct was unsuccessful or because the $RFXPRMS exit was not modified to provide the required file names.
Including the file names of the managed CONNECT:Direct region in the $RFXPRMS exit will bypass the need for the command API to issue the INQUIRE INITPARMS command to obtain these file names.
Note: For CONNECT:Direct Version 1.8, the $RFZPRMS exit must be customized because this version of CONNECT:Direct does not support the INQUIRE INITPARMS command.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Update the $RFXPRMS exit to include the file names of the NETMAP and MSGFIL datasets for the managed CONNNECT:Direct region.
If the version of CONNECT:Direct is later than V1.8, the file names can be dynamically extracted by the INQUIRE INITPARMS command. In this case, check that the user ID specified in the CDAPI parameter group is defined to CONNECT:Direct and has the necessary authority. Also check that the CMD clist is available in the CONNECT:Direct OPLIST dataset.
Reason:
The CONNECT:Direct Command Interface procedure has not got exclusive control of the CONNECT:Direct API and iswaitig for a previous request to complete. P1 is the NCLID of the command interface.
System Action:
The procedure will wait for 30 seconds at a time to get exclusive control of the CONNECT:Direct API, issuing this message each time until successful.
User Action:
Wait for exclusive control to be gained or flush the procedure.
Reason:
The CONNECT:Direct Command Interface procedure has attempted to perform function P1 against the subsystem P2 and received the unexpected result
P3.
System Action:
The procedure will terminate, the request is rejected.
User Action:
Investigate the cause of the error and rectify.
Reason:
The CONNECT:Direct Command Interface procedure has attempted to use the SUBSYS identified by P1 and received an error indicating that the SUBSYS had abended. A restart of the SUBSYS also abended.
System Action:
The procedure will terminate, the request is rejected.
User Action:
Investigate the cause of the error and rectify.
Reason:
The CONNECT:Direct Command Interface procedure has attempted to perform the function identified by P1 against the DMPRINT dataset and received return code P2 and feedback P3
System Action:
The procedure terminates.
User Action:
Investigate the cause of the error and rectify.
Reason:
This message indicates that the The CONNECT:Direct Command Interface has successfully terminated and returned all responses received from CONNECT:Direct.
System Action:
The procedure terminates.
User Action:
None
Reason:
The CONNECT:Direct Command Interface procedure has attempted to allocate/unallocate the dataset identified by P1 and received return code P2 and feedback P3 with error message P4 .
System Action:
The procedure terminates.
User Action:
Investigate the cause of the error and rectify.
Reason:
The CONNECT:Direct Command Interface procedure issued a command and received a non-zero return code P1 (greater than 4) and message P2 from the CONNECT:Direct API.
System Action:
Any contents of DMPRINT are returned along with this message.
User Action:
None.
Reason:
The CONNECT:Direct Command Interface procedure issued a command and received return code 4 from CONNECT:Direct. The returned message text is in P1.
System Action:
Any contents of DMPRINT are returned along with this message.
User Action:
None.
Reason:
The CONNECT:Direct Command Interface procedure was invoked and found that one of the required DDNAMES, DMPRINT or DMPUBLIB as identified by
P1 has not been allocated.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Go to option A.C.P and check the CDAPI parameter group. Ensure that the appropriate file(s) are specified and action (F6) the group to cause the files to be allocated.
Reason:
The CONNECT:Direct Command Interface procedure attempted a signon and failed. P1 is the user ID. If available, P2 is the return code from the CONNECT:Direct Command Interface.
Any additional messages returned by CONNECT:Direct are written to the activity log. These messages are prefixed with the message ID RFCDCMD22.
System Action:
The request fails. Any related error messages are written to the activity log.
User Action:
Determine the cause of the failure. Correct it, and retry.
Following are some possible causes:
Reason:
The CONNECT:Direct Command API work file DDNAME: DMPRINT has been allocated to a temporary file.
System Action:
Processing continues.
User Action:
None.
Reason:
An internal error has occurred.
The CONNECT:Direct Command API work file DDNAME: DMPRINT cannot be allocated. P1 is the error text.
System Action:
The request is rejected. The interface procedure ends with return code 16.
The CONNECT:Direct Command API responses is disabled.
User Action:
Contact Technical Support with the full text of this message.
Reason:
A signon or signoff request to the CONNECT:Direct Command Interface has failed. P2 is a message returned by the interface. P1 is the name of the CDMGR resource. A companion message (RFCDCMD12) is written to the related CDMON transient log.
System Action:
The request fails.
User Action:
Determine the cause of the failure. Correct it, and retry.
Following are some possible causes:
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process was successfully submitted.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process was submitted but has failed. The completion code, P2 , and the CONNECT:Direct message ID, P3 , are shown.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
This message may indicate that a CONNECT:Direct transmission has failed and that manual intervention is required to restart or resubmit the process. The following may be useful in problem diagnosis:
- CONNECT:Direct completion code and message ID - CONNECT:Direct job output - System log
Reason:
This message provides additional information about a CONNECT:Direct process that was identifed by a previous message that indicates the success or failure of the process.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The message also includes the following:
- CONNECT:Direct user ID, P2 , that submitted the process
- CONNECT:Direct node, P3 , from where the process is submitted
- CONNECT:Direct sending node, P4
- CONNECT:Direct receiving node, P5
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process has started.
Note: This message is generated only if the CONNECT:Direct region is version 2.2 or higher.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as...
name is missing #number#
number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a COPY step within a CONNECT:Direct process has started.
Note: This message is generated only if the CONNECT:Direct region is version 2.2 or higher.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as...
name is missing #number#
number is missing name(0)
The step name, P2 , is also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a COPY step within a CONNECT:Direct process has sucessfully completed.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The step name, P2 , is also shown if available.
This message is followed by the following messages which provide additional details:
- RFCDEV08, which provides information about the file sent (if appropriate)
- RFCDEV09, which provides information about the file received (if appropriate)
These messages may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a COPY step within a CONNECT:Direct process has failed. The completion code, P3 , and the CONNECT:Direct message ID, P4 , are shown.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The step name, P2 , is also shown if available.
This message is followed by the following messages, which provide additional details:
- RFCDEV08, which provides information about the file sent (if appropriate)
- RFCDEV09, which provides information about the file received (if appropriate)
These messages may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has failed and that manual intervention is required to restart or resubmit the process. The following information is useful in problem diagnosis:
- CONNECT:Direct completion code and message ID
- CONNECT:Direct job output
- System log
Reason:
This message follows message RFCDEV06 or RFCDEV07, following the completion of a COPY step within a process. The message contains information about the sent dataset as follows:
- Dataset name, P1
- Dataset type, P2
- Number of bytes sent successfully, P3
- Number of records sent successfully, P4
- Number of blocks sent successfully, P5
- Number of members sent successfully, P6
System Action:
None
User Action:
None
Reason:
This message follows message RFCDEV06 or RFCDEV07, following the completion of a COPY step within a process. The message contains information about the dataset that was received as follows:
- Dataset name, P1
- Dataset type, P2
- Number of bytes received, P3
- Number of records received, P4
- Number of blocks received, P5
- Number of members received, P6
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process has moved to a different process queue, P2 , which is one of the following:
- EXEC, where the process will now execute
- HOLD, where the process is held pending release
- TIMER, where the process is waiting for the scheduled time
- WAIT, where the process is waiting for the CONNECT:Direct nodes to make contact
Note: This message is generated only if the CONNECT:Direct region is version 2.2 or higher.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as...
name is missing #number#
number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process was sucessfully completed.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as...
name is missing #number#
number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process has terminated due to a failure. The completion code, P2 , and the CONNECT:Direct message ID, P3 , are shown.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as...
name is missing #number#
number is missing name(0)
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
This message may indicate that a CONNECT:Direct transmission has failed and that manual intervention is required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completeion code and message ID
- CONNECT:Direct job output
- System log
Reason:
A notification has been received from CONNECT:Direct, indicating that a RUN JOB step within a CONNECT:Direct process has started.
Note: This message is generated only if the CONNECT:Direct region is version 2.2 or higher.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The step name, P2 , is also shown if it is available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a RUN JOB step within a CONNECT:Direct process has sucessfully completed.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The job name and number, P2 , and step name, P3 , are also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a RUN JOB step within a CONNECT:Direct process has failed. The completion code, P4 , and the CONNECT:Direct message ID, P5 , are shown.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The job name and number, P2 , and step name, P3 , are also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has failed and that manual intervention is required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completion code and message ID
- CONNECT:Direct job output
- System log
Reason:
A notification has been received from CONNECT:Direct, indicating that a RUN TASK step within a CONNECT:Direct process has started.
Note: This message is generated only if the CONNECT:Direct region is version 2.2 or higher.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The step name, P2 , is also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct indicating that a RUN TASK step within a CONNECT:Direct process has completed successfully.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The task name, P2 , and step name, P3 , are also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a RUN TASK step within a CONNECT:Direct process has failed. The completion code, P4 , and the CONNECT:Direct message ID, P5 , are shown.
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
The task name, P2 , and step name, P3 , are also shown if available.
This message may be followed by RFCDEV03, which provides additional identification details.
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has failed and that manual intervention is required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completion code and message ID
- CONNECT:Direct job output
- System log
Reason:
NetMaster for File Transfer includes a CONNECT:Direct statistics exit that sends CONNECT:Direct events to this region using the program-to-program interface (PPI). This message indicates that the statistics exit was unable to send P1 messages due to PPI errors, such as queue full.
System Action:
None.
User Action:
Check the CONNECT:Direct log for messages that start with RFCX. These messages are written by the statistics exit when it is unable to send events to the PPI.
Help for messages with RFCX-prefixed IDs are available in the NetMaster for File Transfer region. Refer to the specific RFCX message number for an explanation and remedial action.
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct region has started. The time, P1, and date, P2, when the region was started is shown with the dataset name and member for the CONNECT:Direct initialization parameters.
System Action:
None.
User Action:
None.
Reason:
A notification has been received from CONNECT:Direct, indicating that CONNECT:Direct shutdown has started. The following information is shown:
- Time, P1 , and date, P2 , when shutdown started
- User ID, P3 , and node, P4 , of the requestor
- Type of shutdown requested, P5
- Completion code, P6 , and CONNECT:Direct message ID, P7 , that resulted from the request
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating the completion of the CONNECT:Direct shutdown. The time, P1 , and date, P2 , when shutdown was complete is shown.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct log swap has occured. The time, P1 , and date, P2 , when the log swap started is shown along with the log dataset name, P3 .
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process was flushed. The CONNECT:Direct user ID, P2 , and node, P3 , that caused this event is shown along with the completion code, P4, and CONNECT:Direct message ID, P5 .
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has not completed and that manual intervention may be required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completion code and message ID - CONNECT:Direct job output - System log
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct process was suspended. The CONNECT:Direct user ID, P2 , and node, P3 , that caused this event is shown along with the completion code, P4 , and CONNECT:Direct message ID, P5 .
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has not completed and that manual intervention may be required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completion code and message ID
- CONNECT:Direct job output
- System log
Reason:
A notification has been received from CONNECT:Direct, indicating that a CONNECT:Direct task was suspended. The CONNECT:Direct user ID, P2 , and node, P3 , that caused this event is shown along with the completion code, P4, and CONNECT:Direct message ID, P5 .
The process is identified by the process name and number, P1 , and is usually shown as name(number) . If neither of these is supplied in the CONNECT:Direct event, the process is identified as UNKNOWN . However, if only part of the information is not supplied, then:
If the... P1 is shown as... name is missing #number# number is missing name(0)
System Action:
None
User Action:
This message indicates that a CONNECT:Direct transmission has not completed and that manual intervention may be required to restart or resubmit the process. The following information is useful for problem diagnosis:
- CONNECT:Direct completion code and message ID
- CONNECT:Direct job output
- System log
Reason:
NetMaster for File Transfer received a CONNECT:Direct "CT" Copy Termination statistic record for which no corresponding START EVENT had been processed. However, there was a START EVENT for the same transfer with a swapped PNODE/SNODE (known CONNECT:Direct problem). Transfer details are rebuilt. P1 is the transfer key of the START EVENT:
Primary Node - (16 Characters)
Process Number - (08 Characters)
Process Name - (08 Characters)
Secondary Node - (16 Characters)
Step Name - (08 Characters)
The rebuilt START EVENT will have its PNODE/SNODE swapped to match the Copy Termination transfer key.
System Action:
The error is corrected, processing continues.
User Action:
None.
Reason:
NetMaster for File Transfer received a CONNECT:Direct "CT" Copy Termination statistic record for which no corresponding START EVENT had been processed. Transfer details are built from the Copy Termination statistic record.
System Action:
Processing continues.
User Action:
None.
Note: No START EVENT would have been raised for this transfer. The transfer start date and time are not available, and are set as the current system time.
Reason:
NetMaster for File Transfer received a CONNECT:Direct "CT" Copy Termination statistic record and was waiting on other related statistic records to complete the END/FAILURE event. These expected CONNECT:Direct statistic records where not received within the expected time. The END/FAILURE event is raised with the available data. P1 is the transfer key of the END/FAILURE event: Primary Node - (16 Characters)
Process Number - (08 Characters)
Process Name - (08 Characters)
Secondary Node - (16 Characters)
Step Name - (08 Characters)
System Action:
The END/FAILURE event is raised. Some of the CONNECT:Direct WO message records may not have been captured. However, the END/FAILURE event key fields are complete.
User Action:
None.
Reason:
NetMaster for File Transfer received a CONNECT:Direct Statistic Exit "ALLOC" record for a process step which is currently active. P1 is the PNODE P2 is the SNODE P3 is the PROCESS NUMBER P4 is the PROCESS NAME P5 is the PROCESS STEP NAME
System Action:
The duplicate record is ignored and processing continues.
User Action:
Contact Technical Support and provide the following diagnostic information:
- Full text of this message - CONNECT:DIRECT message log
Reason:
The CA Netmaster FTM statistics exit NMCDSTEX for CDMGR P1 is not active.
System Action:
CONNECT:Direct File Transfer Manager P1 is waiting for CONNECT:Direct statistic exit message RFCX01 indicating that the exit has started.
User Action:
Check the Resource Monitor P1 CDMGR Extended Display. If the message RFCDEV70 NM STATS EXIT START PENDING is not reset in a short period, one of the following problems may exist:
Check the CONNECT:Direct job log for related errors.
Reason:
The CA NetMaster FTM statistics exit NMCDSTEX for CDMGR P1 is active but has not sent any events.
System Action:
CONNECT:Direct File Transfer Manager P1 is waiting for a notification event from the exit.
User Action:
Check the Resource Monitor P1 CDMGR Extended Display. If the message RFCDEV71 NM STATS EXIT NOTIFICATION PENDING is not reset in a short period, issue a CHK line command against the P1 CDMGR. If the Extended Display message persists, one of the following problems may exist:
SSI STATUS
If the problem cannot be resolved, contact Technical Support.
Reason:
A health check request response from the CA NetMaster FTM statistics exit NMCDSTEX for CDMGR P1 has not been received.
System Action:
CONNECT:Direct File Transfer Manager P1 is waiting for a response from the exit.
User Action:
Check the Resource Monitor P1 CDMGR Extended Display. If the message RFCDEV72 NM STATS EXIT RESPONSE PENDING is not reset in a short period, issue a CHK line command against the P1 CDMGR. If the Extended Display message persists, one of the following problems may exist:
SSI STATUS
If the problem cannot be resolved, contact Technical Support.
Reason:
The CA NetMaster FTM CDMGR P1 is active with CONNECT:Direct Event Receiver disabled.
System Action:
None.
User Action:
This is an informational message only. It informs you that CDMGR P1 is active and that the CONNECT:Direct Event Receiver is disabled.
This is not an issue when CONNECT:Direct transfer events are not required. If this is not the case, you must update Enable CONNECT:Direct Event Receiver in Customizer Parameter Group: CDAPI. Set the CONNECT:Direct Interface to YES and press F6 (Action) to apply the change.
Reason:
CA NetMaster FTM received a CONNECT:Direct Statistic Exit "HEALTH CHECK" response. This is the expected response to a HEALTH CHECK request.
System Action:
None.
User Action:
None.
Reason:
CA NetMaster FTM CONNECT:Direct Statistic Exit trace has been stopped.
System Action:
CONNECT:Direct Statistic Exit trace terminates.
User Action:
None.
Reason:
CA NetMaster FTM CONNECT:Direct Statistic Exit trace has been started.
System Action:
CONNECT:Direct Statistic Exit trace is active. Trace messages RFCX93 are written to the System Log.
User Action:
None.
Reason:
A pending notification or an event record from the CA NetMaster FTM CONNECT:Direct Statistic Exit was received.
System Action:
The processing of CONNECT:Direct file transfer events starts or resumes.
User Action:
This message may be issued during the CONNECT:Direct region startup indicating that the CONNECT:Direct Statistic Exit event flow started.
If this message was issued after recovering from a loss of communication with the CA NetMaster FTM statistics exit NMCDSTEX, some file transfer events may have been lost.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has failed because a mandatory operand either was omitted or has a null value. The operand in error, P1, is identified.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The message displays the bytes SENT/RECEIVED and READ/WRITTEN for a C:D Transfer. The information presented is used to derive the compression percentage value but incomplete or invalid data was detected.
System Action:
Processing continues with the compression percentage set to 'INC.'
User Action:
Contact your local support representative.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has failed because a CONNECT:Direct event record was received but the procedure does not support it. The record type is shown in character, P1 , and hexadecimal, P2 .
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has failed due to a data error in the event received from CONNECT:Direct. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occured
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- CONNECT:Direct statistics record type, P6
- Statement text where the error occured, P7
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is then ignored.
If file transfer logging is active, it is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has detected that there is currently no active event receiver procedure. The event procedure, P1, will be started.
System Action:
The required event receiver procedure is started.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Direct statistics exit could not process an ALLOCATION event. This may result in the lost of a file transfer START event.
The reason code, P4 , is set as follows:
- 90 indicates that the required TCQE pointer was null.
- 91 indicates that the TCQE could not be validated.
- 92 indicates that the source file information could not be obtained.
- 93 indicates that the target file information could not be obtained.
- 94 indicates that the required TCA pointer was null.
- 95 indicates that the TCA could not be validated.
System Action:
The event is discarded.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message - CONNECT:DIRECT message log
Reason:
The message displays a file transfer event trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None
User Action:
Contact your local support representative.
Reason:
The NetMaster for File Transfer CONNECT:Direct event message format procedure has encountered a recoverable error. Check previous messages for the cause of the error.
System Action:
Event processing continues. However, some events may have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant activity log messages
- CONNECT:DIRECT message log
Reason:
The file transfer event receiver procedure was invoked without the required keyword, P1 .
System Action:
The request is rejected. The interface procedure ends with return code 8.
User Action:
Supply the required keywords. If the missing keyword is ID, enter the
/PARMS shortcut and select the file transfer product API parameter group (for example, CDAPI or CMAPI). Check that the Event Receiver ID is specified, then press F6 (Action) to reset the value.
Note: The ID must be the same as the ID specified in the related product exit (for example, NMCDSTEX for CONNECT:Direct or NMCMLGEX for CONNECT:Mailbox).
If the missing keyword is PRD, contact Technical Support.
Reason:
The events receiver failed when it issued an EPS request. The failure is identified by the following:
- Type of EPS request, P1 (for example, CONNECT)
- Return code, P2 (&RETCODE)
- ERROR NUMBER, P3 (&ERRNO)
- Reason, P4 (for example, EPS UNAVAILABLE)
If possible, recovery is attempted as indicated by the next message (see also RFCDEVR08, RFCDEVR09, or RFCDEVR10).
System Action:
The file transfer events receiver attempts recovery.
User Action:
If the message is not followed by a recovery message, it is likely that the error is related to data corruption. In this instance, the event is discarded and processing continues.
If the problem cannot be resolved, contact Technical Support.
Reason:
The file transfer event receiver received an event which it does not recognize, and the event is ignored. The record received has a hexadecimal value of P1 at offset 2.
System Action:
The file transfer event is ignored.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer event receiver failed due to an MDO error. The failure is identified by the following:
- The statement type, ASSIGN
- The MDO return code, P1 (&ZMDORC)
- The MDO feedback code, P2 (&ZDMOFDBK)
- The map name, P3 (&ZMDOMAP)
- The full map component name, P4 (&ZMDONAME)
- The map component tag value, P5 (&ZMDOTAG)
- The ASN.1 type of the component, P6 (&ZMDOTYPE)
This failure indicates one of the following causes:
- An invalid record has been received.
- There is a mismatch between the ASN.1 map and the record.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer event receiver failed due to an MDO error. It indicates that an invalid record has been received. The failure is identified by the following:
- The statement type, ASSIGN OPT=NAMES PRESENT_IN
- The MDO return code, P1 (&ZMDORC)
- The MDO feedback code, P2 (&ZDMOFDBK)
- The number of component names returned, P3 (&SYS.VARCNT)
The failure occurs because of one of the following causes:
- The return code is non-zero.
- The number of component names is less than 4.
System Action:
The record is ignored.
User Action:
Contact Technical Support.
Reason:
The file transfer event receiver received an event which it identifies as a valid event type. The specific event type ( P1 ), however, is not supported.
This failure indicates one of the following causes:
- An invalid record has been received.
- There is a mismatch between the ASN.1 map and the data.
System Action:
The file transfer event is ignored.
User Action:
Contact Technical Support.
Reason:
The file transfer event receiver procedure is now ready to receive file transfer events via the EPS Services. The associated EPS receiver ID is
P1 .
System Action:
The region is ready for file transfer events processing. If required the product specific events handler will be started when the first event is received (message RFCDEVR07).
User Action:
None.
Reason:
A file transfer event was received from product P1 via the EPS receiver ID P3 . However, the P1 events handler procedure P2 is not currently active. The procedure is started.
System Action:
The P1 events procedure P2 is started.
User Action:
None.
Reason:
This message follows message RFCDEVR01. The recovery is attempted after an EPS request failure (see RFCDEVR01).
System Action:
The system attempts to reconnect to EPS.
User Action:
See message RFCDEVR01 for information about the error causing the retry.
If the problem cannot be resolved, contact Technical Support.
Reason:
This message follows message RFCDEVR01. The required EPS services are currently unavailable. File transfer events monitoring will resume as soon as EPS services are restored.
System Action:
Waiting on EPS to become available.
User Action:
Ensure that an SSI region is currently active with its event processor enabled.
Enter the /PARMS shortcut, and check the SSI parameter group. Ensure that the Sub- System Interface ID field contains the correct ID.
Reason:
This message follows message RFCDEVR01. An unrecoverable error occurred during an EPS request (see message RFCDEVR01). File transfer events monitoring has stopped.
System Action:
The file transfer events receiver is terminated.
User Action:
Contact Technical Support.
Reason:
The file transfer events receiver procedure was invoked with an invalid parameter P1 for keyword(s) P2 .
System Action:
The request is rejected. The interface procedure ends with return code 8.
User Action:
Contact Technical Support.
Reason:
A request to start a file transfer events receiver procedure for EPS Receiver ID P2 was initiated. EPS Receiver ID P2 is currently serviced by procedure ID P1 .
System Action:
Procedure ID P1 will be shared.
User Action:
None.
Reason:
A request to start a file transfer events receiver procedure for the P3 product was initiated. The cleanup process identifies an existing procedure, P1 , which is no longer needed. The P1 procedure is terminated.
System Action:
The P1 procedure is terminated.
User Action:
None.
Reason:
A request to terminate a file transfer events receiver procedure for the P2 product was initiated. The cleanup process identified the P1 procedure as no longer required and terminates the procedure.
System Action:
The P1 procedure is terminated.
User Action:
None.
Reason:
File transfer events processing for the P2 product was disabled.
System Action:
The procedure with ID P1 stopped file transfer events processing for the
P2 file transfer product.
User Action:
None.
Reason:
The message displays a file transfer events receiver trace record.
P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The $RFCDFTL procedure was invoked without the required keywords, P1.
System Action:
The request is ignored.
User Action:
Contact Technical Support.
Reason:
An EPS request cannot complete due to an SSI failure. The monitoring of file transfer events has been suspended.
System Action:
The processing of file transfer events is suspended but will resume as soon as the SSI becomes available.
User Action:
Check the activity log for the associated RFCDEVRxx messages. The RFCDEVRxx messages gives the reason for the SSI failure.
Note: If you are viewing the file transfer log, you can jump directly to the relevant section of the activity log by placing the cursor on the RFCDFTL02 message and pressing F4 (ActLog).
If possible, correct the problem and restart the SSI; otherwise, contact Technical Support.
Reason:
The SSI is now operational, and the flow of file transfer events has resumed.
System Action:
The region resumes the processing of file transfer events.
User Action:
None.
Reason:
The C:D EVENTS connection has failed or is not available. The monitoring of CONNECT:Direct events is suspended. There will be an attempt to reestablish the connection.
System Action:
The processing of CONNECT:Direct events is suspended but will resume as soon as the EVENTS connection is reestablished.
User Action:
Check the transient log for the associated RMIPLN0x messages. The messages give the reason for the connection failure. If possible, correct the problem; otherwise, contact Technical Support.
Reason:
The NetMaster Agent C:D events connection is now operational and the processing of CONNECT:Direct events has resumed.
System Action:
The processing of CONNECT:Direct file transfer events is resumed.
User Action:
None.
Reason:
The NetMaster Agent has been terminated, the monitoring of CONNECT:DIRECT events has stopped.
System Action:
The processing of CONNECT:Direct events has been terminated.
User Action:
No action required if the CDMGR was terminated by the user. Otherwise, check the transient log for associated error messages. If possible, correct the problem; otherwise, contact Technical Support.
Reason:
The status of the SSI policy monitor has changed to ACTIVE.
System Action:
None.
User Action:
None.
Reason:
The SSI policy monitoring is currently not active.
System Action:
The status of the SSI policy monitoring will be checked periodically.
User Action:
If you require the SSI policy monitoring, check the activity log for the associated RFSDMONxx message(s). Review the help for these messages.
If possible, correct the problem and restart the SSI region. Otherwise, contact Technical Support.
Reason:
The P2 Customizer Parameter Group is set to NO - P1 events are not processed.
System Action:
The P2 flow is disabled.
User Action:
None.
Reason:
The P2 Customizer Parameter Group is set to YES - P1 events are processed.
System Action:
The P2 Event flow is enabled.
User Action:
None.
Reason:
This message displays a CA NetMaster FTM CONNECT:Direct Statistics exit heartbeat trace record.
System Action
None.
User Action
Contact Technical Support.
Reason:
The CONNECT:Direct (STC/JOB) P1 is not active.
System Action
None.
User Action
Activate the CDMGR resource, if applicable
Reason:
The CONNECT:Direct (STC/JOB) P1 is active:
P2 is the CONNECT:Direct Address Space ID.
P3 is the CONNECT:Direct Start time and date.
System Action:
None.
User Action:
None.
Reason:
The CONNECT:Direct (STC/JOB) P1 is active:
P2 is the CONNECT:Direct Address Space ID.
P3 is the CONNECT:Direct Start time and date.
System Action:
None.
User Action:
None.
Reason:
The CONNECT:Direct (STC/JOB) P1 is active.
P2 is the CONNECT:Direct EXCP count.
System Action:
None.
User Action:
None.
Reason:
The P1 CA NetMaster FTM CONNECT:Direct Statistics exit responded to a poll request.
System Action:
None.
User Action:
None.
Reason:
CDMGR P1 has an entry in $RFXPRMS (the CDMGR Configurable exit). $RFXPRMS is used when CONNECT:Direct is configured with no MCS user ID.
System Action:
Heartbeat to the CA NetMaster FTM CONNECT:Direct Statistics exit is not executed because it requires MCS support.
User Action:
None.
Reason:
An EPS request cannot complete due to an SSI failure. The monitoring of file transfer events is suspended.
System Action:
The processing of file transfer events is suspended but will resume when the SSI is available.
User Action:
Check the activity log for the associated RFCDEVRxx messages. The RFCDEVRxx messages provides the reason for the SSI failure.
Note: If you are viewing the file transfer log, you can jump to the relevant section of the activity log by placing the cursor on the RFCDHBT07 message and pressing F4 (ActLog).
If possible, correct the problem and restart the SSI; otherwise, contact Technical Support.
Reason:
The CONNECT:Direct Statistics Exit heartbeat procedure is called by the process RFCDHCK1.
The missing or invalid parameter is P1.
Process RFCDHCK1 requires the following parameters:
DISPLAY=xxx TIMEOUT=ss
where xxx is YES when the process is specified in the CDMGR template Display and Heartbeat Details.
where xxx is NO when the process is specified in the CDMGR template Status Monitor Message Details (for MSG: RFCX01).
where ss is the heartbeat poll response timeout in seconds. Must be a positive number.
System Action:
The parameter is assigned the following default:
DISPLAY=YES
TIMEOUT=10
The processing continues.
User Action:
Specify or correct the required parameters.
Reason:
The CA NetMaster FTM CDMGR P1 is active with CONNECT:Direct Event Receiver disabled.
System Action:
None.
User Action:
If you want to receive CONNECT:Direct transfer events, update Enable CONNECT:Direct Event Receiver in the Customizer Parameter Group, CDAPI. Set the CONNECT:Direct Interface to YES and press F6 (Action) to apply the change.
Reason:
The P1 CDMGR resource cannot be contacted using the CONNECT:Direct Command Interface. P2 is the error description.
System Action:
Heartbeat to the CONNECT:Direct statistics exit is not executed because it requires the CONNECT:Direct Command Interface.
User Action:
Determine the cause of the failure. Correct it, and retry.
Following are some possible causes:
Reason:
The heartbeat value in the resource definition was less than the minimum global value. The heartbeat value is increased automatically to P1 .
System Action:
The heartbeat value is increased automatically to the minimum value.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure has failed because a mandatory operand either was omitted or has a null value. The operand in error, P1 , is identified.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 (&ZMDORC)
- MDO feedback code, P2 (&ZDMOFDBK)
- Map name, P3 (&ZMDOMAP)
- Full map component name, P4 (&ZMDONAME)
- Map component tag value, P5 (&ZMDOTAG)
- ASN.1 type of the component, P6 (&ZMDOTYPE)
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure failed to open the CONNECT:Direct message file (DMMSGFIL). The file has not been opened previously (by using UDBCTL OPEN). The attempt to open it has failed. The failure reason, P1 , identifies another message that provides additional explanation.
System Action:
The request is rejected.
User Action:
The most likely cause of this error is that the DMMSGFIL dataset was not allocated correctly. Use the SHOW ALLOCATE command to determine if the dataset is allocated, and if not, use the ALLOCATE command to allocate the dataset, ensuring that the DD name is DMMSGFIL.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure failed to open the CONNECT:Direct message file (DMMSGFIL) for processing in NCL. The open has failed and is identified by the:
- Current file ID, P1
- File return code, P2 , which is the value of &FILERC
- System message, P3 , if any (normally only relevant if the return code is 16)
System Action:
The request is rejected.
User Action:
Use the file return code and message to diagnose the problem.
File return codes are listed in the NCL Reference. See the &FILE verb and &FILERC system variable. If a system message is included (MSG=), see the Help for that message to help you resolve the problem.
If the problem cannot be resolved, contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure failed to read a message record from the CONNECT:Direct message file (DMMSGFIL). The failure is identified by the following:
- Current file ID, P1
- Key of the record, P2 (this is the CONNECT:Direct message ID)
- File return code, P3 , which is the value of &FILERC
- VSAM feedback code, P4 , in hexadecimal format (normally only relevant if the return code is 8)
- System message, P5 , if any (normally only relevant if the return code is 16)
System Action:
The request is rejected.
User Action:
Use the file return code, feedback code, and message to diagnose the problem.
File return codes are listed in the NCL Reference. See the &FILE verb and &FILERC system variable.
If a system message is included (MSG=), see the Help for that message to help you resolve the problem. If the VSAM feedback code is included (FDBK=), use that to refer to your VSAM reference manual and follow the problem diagnosis.
If the problem cannot be resolved, contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Direct message format procedure has failed because the requested message ID, P1 , was not found in the CONNECT:Direct message file (DMMSGFIL).
System Action:
The request is rejected.
User Action:
Reissue the request with a correct message ID.
Reason:
The selection list service procedure $RFCDMSL was called with an option which it does not support.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
Invalid parameters were passed to the $RFCDMSL procedure.
System Action:
The procedure terminates.
User Action:
Contact your local support representative.
Reason:
An attempt to open the VFS database failed with the FILERC, P1 , which can be 0 or 12. If FILERC is 0, the file has been opened but cannot be written to. If FILERC is 12, the user does not have authority to access the database.
System Action:
None
User Action:
Contact your security administrator for assistance.
Reason:
An attempt to save a CONNECT Model with a name P1 failed because a record with this name already exists.
System Action:
The save fails.
User Action:
Choose a different name for the Model or set the 'Replace?' field to YES.
Reason:
An attempt to perform the function P1 with key P3 on the VFS file failed with the Return Code P2 , the Feedback code P4 (if FILERC=8), and message P5 (if FILERC=16).
System Action:
The request is rejected. This message is also logged.
User Action:
Contact your system administrator for assistance.
Reason:
The Model Name P1 was saved to the VFS file.
System Action:
None
User Action:
None
Reason:
No Models have previously been saved for this panel.
System Action:
None
User Action:
None
Reason:
An attempt to retrieve a CONNECT Model with a name P1 failed because a record with this name was not found. This occurs if another system user has deleted the record.
System Action:
Model selection fails.
User Action:
Choose another Model.
Reason:
'CON' command parameters stored in Model Name P1 were loaded into panel fields.
System Action:
None
User Action:
None
Reason:
An attempt was made to issue a CONNECT:Mailbox Manager CON command from a task which does not have access to a terminal window. The CON command is only supported for environments with a terminal window.
System Action:
The request for a CONNECT:Mailbox Auto Connect is rejected.
User Action:
If you want to issue an Auto Connect from an Automation Services process, use the SYSCMD macro to issue the CONNECT:Mailbox $$CONNECT command directly through the system modify (F) command.
Reason:
A CONNECT:Mailbox Manager modify command P1 was issued. However no output was received.
System Action:
The $$CONNECT command may not have been effective. Examine the system log to determine if the command was effective.
User Action:
Contact your local support representative.
Reason:
An attempt was made to issue a CON command for a CONNECT:Mailbox manager P1 . The command can not function unless the manager has ACTIVE status since the command depends on issuing a MODIFY system command for the CONNECT:Mailbox started task.
System Action:
The request is rejected.
User Action:
Activate the CONNECT:Mailbox resource if you want to issue the command.
Reason:
Validation for field P1 has detected one or more characters P2 which are not permitted in this field.
System Action:
The field in error is highlighted.
User Action:
Correct the entry and retry.
Reason:
Validation has detected that a pre-requisite field P2 is blank.
System Action:
The validated field is highlighted.
User Action:
Clear the field P1 or enter data in P2 .
Reason:
Validation for field P1 has detected that a mutually exclusive field
P2 is not blank, or has an incompatible value (e.g. BSC values for Batch Separator for an SNA connect).
System Action:
Field P1 is highlighted.
User Action:
Clear one of the fields or correct the incompatible values.
Reason:
Validation for field P1 has detected that this field is not blank, which it should be if the field P2 has the value P3 .
System Action:
Field P1 is highlighted.
User Action:
Clear P1 or change the value in P2 .
Reason:
Information retained for the user, P1 , to sign on to CDMGR, P2 , has been cleared. The next time the user signs on to this CDMGR, the user will be prompted for user ID and password.
System Action:
None.
User Action:
None.
Reason:
The $RFCMD procedure was invoked with an invalid value, P2 , for the keyword, P1 .
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
The $RFCMD procedure was invoked with keywords, P1 and P2 , which are either contradictory or mutually exclusive. For example, CDMGR= and NAME= may both have been specified, where only one is required to identify a CONNECT:Direct region.
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
An attempt was made to issue a CONNECT:Mailbox Manager DIR command from a task which does not have access to a terminal window. The DIR command is only supported for environments with a terminal window.
System Action:
The request for CONNECT:Mailbox directory information is rejected.
User Action:
If you want directory information from an Automation Services process, use the SYSCMD macro to issue the CONNECT:Mailbox $$DIR command directly through the system modify (F) command.
Reason:
A CONNECT:Mailbox Manager DIR command was requested for the Mailbox Details as entered but no batches were found.
System Action:
The request for CONNECT:Mailbox directory information is rejected.
User Action:
Enter another Mailbox ID and/or User Batch ID.
Reason:
An attempt was made to issue a DIR command for a CONNECT:Mailbox manager P1 . The command can not function unless the manager has ACTIVE status since the command depends on issuing a MODIFY system command for the CONNECT:Mailbox started task.
System Action:
The request is rejected.
User Action:
Activate the CONNECT:Mailbox resource if you want to issue the command.
Reason:
One or more requests to change status flags has been actioned. The number of confirmatory CMB167I messages received from CONNECT:Mailbox was P1 . Note that in some cases (e.g. locked batches) the flag will not be changed even though message CMB167I is issued.
System Action:
The Mailbox Batch List is alwaus refreshed after a status flag change.
User Action:
None.
Reason:
A CONNECT:Mailbox Manager DIR command was requested for the Mailbox P2 . When processing output from the $$DIR command, an error condition P1 was encountered. This error occurs if the data from CONNECT:Mailbox has changed format.
System Action:
The request for CONNECT:Mailbox directory information is terminated with batch data collected so far displayed.
User Action:
Contact your local support representative.
Reason:
A CONNECT:Mailbox Manager modify command P1 was issued. However not all of the expected output was received. This could be caused by a timeout whilst waiting for command output.
System Action:
If the command P1 is a $$DIR command, then the directory information collected so far is displayed. If this message is in response to a line command against a batch, the line command may not have been effective.
User Action:
Examine the log and the system log to check the command and the command output. If the problem is a timeout, change the Command Response timeouts which are controlled by the values specified in the Console Specifications (System Command Controls) Customizer Parameters (/PARMS - TUNING - $RM CONSOLES Console Specifications). If the problem occurs after increasing the timeouts, contact Technical Support.
Reason:
The keyword parameter, P1 , was specified with the invalid value, P2 .
System Action:
The request is rejected, and processing terminates.
User Action:
Contact your local support representative.
Reason:
A required keyword parameter was not specified. The keyword was P1 .
System Action:
The request is rejected, and processing terminates.
User Action:
Contact your local support representative.
Reason:
The command, P1 , is not supported by CONNECT:Direct for P2 .
System Action:
Request is rejected.
User Action:
Contact your local support representative.
Reason:
There was no CONNECT:Direct command response text specified for this CHECK request.
System Action:
Request is rejected.
User Action:
Contact your local support representative.
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer has started.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the User Batch ID.
This message is followed by RFCMEV02, which provides additional connection details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer has started. This message follows message RFCMEV01.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the direction of the batch transfer (SENDING TO/RECEIVING FROM).
P4 is either LINE (for Remote Connect BSC) or RMT (for other).
P5 is the BSC Line Name (for Remote Connect BSC) or Remote Name (for other).
P6 is the List Name (AUTO CONNECT only).
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer successfully completed.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the User Batch ID.
This message is followed by RFCMEV04, which provides additional connection and transfer details.
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer successfully completed. This message follows message RFCMEV03.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the direction of the batch transfer (SENT/RECEIVED).
P4 is 1) For AUTO CONNECT: The number of records transmitted. 2) For REMOTE CONNECT: The number of records and bytes transmitted.
P5 is the Remote Name.
P6 is the List Name (AUTO CONNECT only).
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer has failed.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the User Batch ID.
This message is followed by RFCMEV06/08, which provides additional connection and error details
System Action:
None
User Action:
None
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer has failed. This message follows message RFCMEV05.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the CONNECT FAILURE CODE (enter CMFC at the prompt line to display failure codes and their description).
P4 is the direction of the batch transfer (SENDING TO/RECEIVING FROM).
P5 is the Remote Name.
P6 is the List Name (AUTO CONNECT only).
System Action:
None
User Action:
None
Reason:
NetMaster for File Transfer received a CONNECT:Mailbox batch termination log record for which no corresponding START EVENT had been processed.
System Action:
Processing continues.
User Action:
None.
Reason:
A notification has been received from CONNECT:Mailbox, indicating that a batch transfer has failed. This message follows message RFCMEV06.
P1 indicates the connection type. (A/C) is for AUTO CONNECT and (R/C) is for REMOTE CONNECT.
P2 is the batch transfer ID shown as Batch ID(Batch Number) .
P3 is the CONNECT FAILURE REASON (enter CMFC command at the prompt line to display failure codes and their description).
System Action:
None
User Action:
None
Reason:
The NetMaster for File Transfer CONNECT:Mailbox event handler procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox event handler procedure has encountered a recoverable error. Check previous messages for the cause of the error.
System Action:
Event processing continues. However, some events may have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant activity log messages
- CONNECT:Mailbox message log
Reason:
The NetMaster for File Transfer CONNECT:Mailbox event handler procedure has failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox event handler procedure has failed due to a data error in the event received from CONNECT:Mailbox. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- CONNECT:Mailbox log record type, P6
- Statement text where the error occurred, P7
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is then ignored.
If file transfer logging is active, it is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The message displays a file transfer event trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None
User Action:
Contact your local support representative.
Reason:
The heartbeat value in the resource definition was less than the minimum global value. The heartbeat value is increased automatically to P1 .
System Action:
The heartbeat value is increased automatically to the minimum value.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox Message Information procedure failed to open the CONNECT:Mailbox ISPF VSAM Administration file. The most likely cause of this error is that the data set was not allocated at region initialization. P1 identifies the DD name for the file.
System Action:
The request for message information is rejected.
User Action:
If you want message information, enter a data set name in the $RF CMAPI parameter group (/PARMS) and press F6 (Action) to action the changes immediately.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox Message Information procedure has failed because the requested item P1 , value P2 was not found in the CONNECT:Mailbox ISPF VSAM Administration file.
System Action:
The request is rejected.
User Action:
Reissue the request with a correct message ID or failure code. If the ID or code is correct, check that the latest messages have been loaded into the CONNECT:Mailbox ISPF VSAM Administration file.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox Message Information procedure failed to read a message record from the CONNECT:Mailbox ISPF VSAM Administration file. The failure is identified by:
- Current file ID, P1
- Key of the record, P2 (bytes 11-18 = CONNECT:Mailbox message ID)
- File return code, P3 , which is the value of &FILERC
- VSAM feedback code, P4 , in hexadecimal format (normally only relevant if the return code is 8)
- System message, P5 , if any (normally only relevant if the return code is 16)
System Action:
The request is rejected.
User Action:
Use the file return code, feedback code, and message to diagnose the problem.
See the NCL Reference manual for details of the &FILE verb and &FILERC system variable.
If a system message is included (MSG=), see the Help for that message to help you resolve the problem. If the VSAM feedback code is included (FDBK=), refer to your VSAM reference manual and follow the problem diagnosis.
If the problem cannot be resolved, contact Technical Support.
Reason:
The region was unable to register for unsolicited messages from a CONNECT:Mailbox started task. P1 is the reason for the failure. Messages from that task will not appear in the file transfer log.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
You performed an action that issue the P1 command but received no response.
System Action:
The request is rejected.
User Action:
Ensure that the CONNECT:Mailbox region is still active. If it is active, other tasks may be degrading the response time and you can retry later.
Reason:
While the CONNECT:Mailbox region is active, you cannot deallocate its VSAM Control File (VCF) or VSAM Pointer File (VPF).
System Action:
The request is rejected.
User Action:
None.
Reason:
You canceled your request to deallocate the selected VSAM batch file from its CONNECT:Mailbox region.
System Action:
The request to deallocate the file is not processed.
User Action:
None.
Reason:
The P1 action has completed.
System Action:
None.
User Action:
None.
Reason:
You exit the VSAM File Statistics panel without completing the assisted file reorganization process for the P1 files.
System Action:
The region removes your exclusive online control of the files.
User Action:
You might need to complete the reorganization manually offline.
Reason:
You tried to allocate a VSAM batch file that has not completed reorganization, and the action is successful. The action forces the completion of the suspended reorganization.
System Action:
The region removes your exclusive online control of the file.
User Action:
None.
Reason:
You allocated a CONNECT:Mailbox VSAM batch file successfully after its reorgnization was suspended after the copy task. The allocation task completes the reorganization process.
System Action:
The region removes your exclusive online control of the file.
User Action:
None.
Reason:
You entered AR beside a CONNECT:Mailbox VSAM batch file, but another user, P1 , is already performing that action on the file and has exclusive online control of that file. No action is possible until that control is released.
System Action:
The request is rejected.
User Action:
None.
Reason:
You entered AR beside a CONNECT:Mailbox VSAM batch file, but the file attributes cannot be accessed. The reason may be:
- The dataset cannot be found.
- The file reorganization has been left in an incomplete state from a previous action.
System Action:
The request is rejected.
User Action:
Check the activity log for the RFCMV5S01 message. The message contains the SYSPRINT output from the IDCAMS program, which provides details of the failure.
Also, review the results of a previous assisted reorganization of the file.
You might need to perform the reorganization manually by using batch jobs.
Reason:
This message contains an IDCAMS message, P2 , generated during the processing of the P1 file.
System Action:
None.
User Action:
None.
Reason:
You tried to execute a task that requires the completion of a previous task. That previous task has not been completed.
System Action:
The request is rejected.
User Action:
Complete any previous tasks such that their status is Done.
Reason:
You cannot redo a task that completed successfully (status Done).
System Action:
Te request is rejected.
User Action:
None.
Reason:
You did not provide input to a task that requires it.
System Action:
The task is not performed.
User Action:
Perform the task again providing the correct input.
Reason:
You canceled a task that requires input.
System Action:
Default input is reapplied to the task.
User Action:
None.
Reason:
Automatic execution of the assisted CONNECT:Mailbox VSAM batch file reorganization tasks is taking place.
System Action:
The processing continues.
User Action:
If desired, you can stop the execution by pressing F6.
Reason:
You pressed F6 (StopExec) to stop the automatic execution of the assisted CONNECT:Mailbox VSAM batch file reorganization tasks.
System Action:
Procesesing continues to complete the task in progress.
User Action:
If desired, you can restart automatic execution by pressing F6 (AutoExec).
Reason:
You entered AR beside a CONNECT:Mailbox VSAM batch file that encountered an error during a previous execution of the same action. Automatic execution of the file reorganization tasks is not possible until the error is cleared.
System Action:
The task list is displayed.
User Action:
Step 1. Enter B beside the task in error to review its output to determine the cause of the failure.
Step 2. Enter R beside the task to clear the error.
Step 3. If input needs to be corrected, enter E beside the task and correct it, then press F6 (Action) to action the task.
Step 4. To continue with automatic execution, press F6 (AutoExec).
Reason:
You entered B beside an assisted CONNECT:Mailbox VSAM batch file reorganization task, but there is nothing to display. Typically, you can browse tasks that have executed or tasks that have default input.
System Action:
None.
User Action:
None.
Reason:
You entered R beside a task that does not need to be redone. You can redo a task in error.
System Action:
The request is rejected.
User Action:
None.
Reason:
The file was deallocated outside of the control of the Assisted REORG Facility. No output is available.
System Action:
None.
User Action:
None.
Reason:
The assisted CONNECT:Mailbox VSAM batch file reorganization process was suspended before completion. The next task is P1 with a P2 status.
System Action:
Processing continues at the VSAM File Statistics panel, and the file remains under your exclusive control.
User Action:
You can resume the reorganization process by entering AR (Assisted REORG) beside the file. You can also try to release control of the file by entering A (Allocate) beside it.
Reason:
You have reorganized the selected file.
System Action:
Exclusive control of the file is released.
User Action:
If you want to delete the backup file, enter E beside the last task.
Reason:
This message contains an IDCAMS message, P2 , generated during the assisted reorganization of the P1 file.
System Action:
None.
User Action:
None.
Reason:
You canceled the requested action.
System Action:
None.
User Action:
None.
Reason:
An error was encountered during automatic execution of the file reorganization tasks.
System Action:
The task list is displayed.
User Action:
Step 1. Enter B beside the task in error to review its output to determine the cause of the failure.
Step 2. Enter R beside the task to clear the error.
Step 3. If input needs to be corrected, enter E beside the task and correct it, then press F6 (Action) to action the task.
Step 4. To continue with automatic execution, press F6 (AutoExec).
Reason:
You used the FILE command to save the changed input for the dataset creation task. The task status is now Pending, and the task executes immediately when you next enter E beside it.
Note: The saved input is available to the current session only.
System Action:
None.
User Action:
Enter E beside the task to create the new dataset.
Reason:
You used the FILE command to accept the default input for the dataset creation task. The task status is now Pending, and the task executes immediately when you next enter E beside it.
System Action:
None.
User Action:
Enter E beside the task to create the new dataset.
Reason:
You must specify a dataset name in each of the hightlighted NEWNAME fields.
System Action:
The fields in error are highlighted.
User Action:
Specify a valid dataset name in each of the highlighted NEWNAME fields.
Reason:
You cannot specify the current dataset names in the NEWNAME fields.
System Action:
The fields in error are highlighted.
User Action:
Correct the names in the highlighted fields.
Reason:
The highlighted fields contain invalid VSAM dataset names.
System Action:
The fields in error are highlighted.
User Action:
Ensure that the highlighted fields contain a valid VSAM dataset name.
Reason:
You specified the same dataset name in more than one NEWNAME fields.
System Action:
The affected fields are highlighted.
User Action:
Ensure that the dataset names in the NEWNAME fields are different from each other.
Reason:
You specified a dataset name that already exists in the system.
System Action:
The field in error is highlighted.
User Action:
Ensure that the dataset name does not exist in the system.
Reason:
This message contains an IDCAMS message, P2 , generated during the processing of the P1 file.
System Action:
None.
User Action:
None.
Reason:
A required parameter was not available when this procedure was invoked.
System Action:
The procedure is terminated.
User Action:
Review the definition of the specified resource, and try again.
Reason:
The CONNECT:Mailbox VSAM File Server cannot be identified. You might have acted on a CMMGR class resource definition that does not have a VSAM File Server STC class resource definition as its parent.
System Action:
The action is not performed.
User Action:
Ensure that you have the VSAM File Server STC definition as a parent of the CONECT:Mailbox CMMGR definition.
If the Server definition is not in the knowledge base, define it based on the CMSVR template.
To relate the resources, proceed as follows:
Step 1. From any panel, enter D.R.R.CMMGR to list the CONNECT:Mailbox managers.
Step 2. Ensure that the managers belong to the correct system image, and enter R beside the manager to list any existing relationships.
Step 3. Press F11, and select the STC resource class.
Step 4. Make the appropriate VSAM File Server as a parent of the manager.
Reason:
The heartbeat procedure for TCP/IP connections has commenced processing. The message identifies the idle time setting before an alert is issued ( P1 ) and the idle time setting after which the connection will be dropped ( P2 ).
System Action:
None
User Action:
None
Reason:
The heartbeat procedure for TCP/IP connections has been invoked without the Idle Time to Alert parameter, which is required.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource, and specify the missing parameter.
Reason:
This is an informational message issued by the TCP/IP connections monitor for each connection found.
P1 identifies the host at the other end of the connection.
P2 is the connection ID.
P3 is the actual idle time.
P4 is the connection status.
P5 is optional. It contains ALERT if the idle time exceeds the Idle Time to Alert value in the monitor resource definition. It contains DROPPED if the idle time exceeds the Idle Time to Drop value in the monitor resource definition and the connection was dropped.
System Action:
None
User Action:
None
Reason:
The TCP/IP connections of a file transfer resource were checked, and none were found to exceed the idle time limits specified in the connections monitor resource.
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the number of connections checked.
P4 is the time.
System Action:
None
User Action:
None
Reason:
A file transfer resource has a number of TCP/IP connections ( P3 ) that have exceeded the Idle Time limit value specified in the definition for the connections monitor. Of these, P4 connections have been dropped automatically because they also exceeded the specified Idle Time to Drop value.
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the number of connections that have exceeded the idle time limit.
P4 is the number of connections that have been terminated.
P5 is the time.
System Action:
None
User Action:
None
Reason:
The TCP/IP interface is currently P1. The monitoring of this resource requires the status of the TCP/IP interface to be ACTIVE.
System Action:
Heartbeat processing does not take place.
User Action:
Display the current TCP/IP services status by issuing a SHOW TCPIP command. Message N3AF05 shows the current TCP/IP INTERFACE status.
If the TCP/IP INTERFACE status is INACTIVE - Issue a TCPIP START command. Wait for message N3B201 and then enter a CHK command against this resource.
If the TCP/IP INTERFACE status is QUIESCING or STOPPING - wait for the STATUS to change to INACTIVE and proceed as above.
If the TCP/IP INTERFACE status is STARTING - Wait for message N3B201 and then enter a CHK command against this resource.
Reason:
The TCP/IP connections monitor was unable to ascertain the TCP/IP port number used by the file transfer resource manager, P1 .
System Action:
Monitoring fails.
User Action:
This only applies when TCPaccess is being used.
For a CONNECT:Direct resource, the port number is either obtained automatically from CONNECT:Direct or provided in user exit $RFXPRMS. One possible problem is that an old version of $RFXPRMS is executed.
For a FTP resource, the port number must be specified in the resource definition.
Reason:
Monitoring of TCP/IP connections is not available for CONNECT:Direct for
P1 .
System Action:
Request is rejected.
User Action:
Delete the CDMON resource as it serves no purpose.
Reason:
The file transfer application requires an active listener port to receive requests for connection. The required listener port was not found or was not in a LISTEN state.
P1 identifies the owning file transfer resource.
P2 displays the name of the monitor resource.
P3 is the time.
System Action:
None
User Action:
Perform one or more the following to investigate the problem:
- Check the transient log of the monitor resource for additional details.
- If the port number of the file transfer application is specified on the Monitor Details panel of the resource definition, check its accuracy.
- Check the current state of the file transfer application, P1 .
- Check the current state of the TCP/IP region.
Reason:
The message displays a TCP/IP connections monitor trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A display command was received for a connections monitor, but the requestor is not in 3270 full-screen mode.
System Action:
The display command is rejected.
User Action:
Enter the display command from a 3270 session.
Reason:
The field name P1 is not available for performing an NDB custom search.
System Action:
Field highlighted in error.
User Action:
Enter a valid field name or place a '?' in the field to get a list of valid field names. You can also enter a field prefix followed by a ? for a list of fields with that prefix.
Reason:
Selection of fields from the list was cancelled.
System Action:
None
User Action:
None
Reason:
No fields were selected from the Fields Selection List. The target file cannot be created.
System Action:
The request is terminated.
User Action:
Redo your request and select one or more fields.
Reason:
An error occurred during a GET function on the vartable P1 for key P2 . The received error code is P3 .
System Action:
The request is terminated and the procedure is ended.
User Action:
Contact your system administrator.
Reason:
A user cancelled the request to extract file transfer events from the EVNTDB database.
System Action:
The request to extract file transfer events is not processed.
User Action:
None.
Reason:
Your request to extract file transfer events starts the EVNTDB extract process as a background task that runs with your authority. Progress messages with the prefix RFLO82* are written to the activity log.
System Action:
The process is submitted to your background region.
User Action:
Check the activity log for progress. To access the list of available logs, enter the =H.L panel path.
Reason:
The NDB Search did not find any record(s) that match(es) the Extract Criteria.
System Action:
None
User Action:
Change your criteria and retry.
Reason:
A syntax error was detected during execution of an NDB SCAN statement.
System Action:
None
User Action:
Review the scan and sort expression and retry the command.
Reason:
The NetMaster for File Transfer statistics exit, NMCDSTEX, is active.
P1 shows the module name and version number. P2 identifies the ID from which CONNECT:Direct events can be received.
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer statistics exit, NMCDSTEX, has requested the services of the event delivery facility, but the request was rejected because of one of the following:
- The required SSI is not active.
- The SSI is active but is running without the event delivery facility.
System Action:
Statistics records will be forwarded to the NetMaster for File Transfer region as soon as the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The NetMaster for File Transfer statistics exit, NMCDSTEX, has requested the services of the event delivery facility, but the request was rejected because the SSI region is not currently active.
System Action:
Statistics records will be forwarded to the NetMaster for File Transfer region as soon as the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The NetMaster for File Transfer statistics exit, NMCDSTEX, requested the services of the event delivery facility, but the request was rejected because the SSI is shutting down.
System Action:
The statistics record is not forwarded to the region. As a result, not all CONNECT:Direct events are in the file transfer log.
User Action:
Ensure that the SSI region is restarted.
Reason:
The NetMaster for File Transfer statistics exit, NMCDSTEX, issued a $NMXEVNT request to forward a CONNECT:Direct event to the event receiver. The request was rejected. The values of the R0 and R15 return codes from the $NMXEVNT request are P1 and P2 respectively.
System Action:
The event record is not forwarded to the region.
User Action:
Note the value of R0 and R15, and contact Technical Support.
Reason:
This message is the first of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Direct statistics exit, NMCDSTEX. The complete set of messages is:
RFCX06 ABEND AT +nnnn IN xxxxxxxx xxxx LEVEL xxxxxx
RFCX07 RECEIVED R1=xxxxxxxx RECORD ADDR=xxxxxxxx RECORD TYPE=xx RFCX08 PSW=xxxxxxxx xxxxxxxx INT=xxxxxxxx
RFCX09 R0-R3 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFCX09 R4- R7 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFCX09 R8-R11 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFCX09 R12-R15 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Message RFCX06 identifies the abend offset, module, version, and level.
Message RFCX07 identifies the parameters passed by CONNECT:Direct:
RECEIVED R1 is the value in R1 when the exit was called.
RECORD ADDR is the value of the first full word addressed by R1. If R1 was invalid, this is shown as UNKNOWN.
RECORD TYPE is the CONNECT:Direct statistics record type. If either R1 or the record address was invalid, this is shown as ??.
Message RFCX08 identifies the failing PSW and program interruption information.
Message(s) RFCX09 identify the general purpose registers at the time of the abend.
System Action:
The statistics record is ignored, and processing continues.
User Action:
Contact Technical Support. Ensure that you have the following information available:
- The entire group of messages (RFCX06 to RFCX09) - The version and maintenance level of CONNECT:Direct
Reason:
This message is one of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Direct statistics exit, NMCDSTEX.
For more information, see the help for message RFCX06.
System Action:
See RFCX06.
User Action:
See RFCX06.
Reason:
This message is one of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Direct statistics exit, NMCDSTEX.
For more information, see the help for message RFCX06.
System Action:
See RFCX06.
User Action:
See RFCX06.
Reason:
This message is the last of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Direct statistics exit, NMCDSTEX.
For more information, see the help for message RFCX06.
System Action:
See RFCX06.
User Action:
See RFCX06.
Reason:
The CONNECT:Direct statistics exit, NMCDSTEX, was unable to obtain or free working storage. P1 is the failing request, and P2 is the value of the R15 code.
System Action:
The request cannot be processed.
User Action:
Use the R15 code to determine the cause of the error.
Reason:
The CONNECT:Direct statistics exit, NMCDSTEX, tried to load a load module, but the loading operation failed. The load module name is P1, and the values of the R0 and R15 return codes from the LOAD or BLDL instruction are P2 and P3 respectively.
System Action:
The load module is not loaded and is excluded from further processing, the result of which depends on which module has failed to load:
Module NMCDSTX No statistics records are forwarded to the region. As a result, its log file is incomplete.
Other Modules Other modules relate to your own exits. The result of not executing these modules depends on your implementation.
User Action:
Use the R0 and R15 return codes to determine the cause of the error.
A common error is R15=4 (accompanying an 806 system completion code), which indicates that the module could not be found in the load library list (that is, the list of libraries that are specified in the CONNECT:Direct STEPLIB).
Ensure that the Management Services LPALOAD load library is either included in the CONNECT:Direct STEPLIB or included in the system link list.
Notes: - All libraries included in the STEPLIB must be APF authorized. - The CONNECT:Direct region must be recycled to restart the statistics exit.
Reason:
The forwarding of CONNECT:Direct statistics event has resumed. This message indicates a recovery from a previous error condition (for example, the required SSI region was successfully restarted).
System Action:
CONNECT:Direct statistics events are now sent to the event receiver.
User Action:
None.
Reason:
The statistics exit, NMCDSTEX, has requested the services of the event delivery facility, but the request was rejected because the event delivery facility could not obtain storage (R0=7 and R15=28 returned from $NMXEVNT).
System Action:
The CONNECT:Direct statistic event is not sent to the event receiver.
User Action:
Contact Technical Support.
Reason:
This is a diagnostic trace message.
The statistics exit, NMCDSTEX, was called by CONNECT:Direct.
P1 is the Trace Type ( A for Alert trace, T for solicited trace).
P2 is the CONNECT:Direct statistics record type.
P3 is the number of statistics records received by NMCDSTEX.
P4 is the number of statistics records received by NM000FCX.
P5 is the expected number of statistics records that should have been received by NM000FCX.
P6 is the current Exit Process Status byte.
P7 / R8 is the last EPS return code (R15/R0).
System Action:
None.
User Action:
For trace type A , contact Technical Support. Ensure that you have the following information available:
- The entire group of messages (RFCXxx)
- The version and maintenance level of CONNECT:Direct
Reason:
The CA NetMaster FTM statistics exit NMCDSTEX P1 trace status has changed. P2 is the current trace status.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The statistics exit, NMCDSTEX, was called by CONNECT:Direct. The exit has successfully loaded another load module ( P1 ), and its entry point address is shown ( P2 ).
This is a diagnostic trace message.
System Action:
None.
User Action:
None.
Reason:
The statistics exit, NMCDSTEX, was called by CONNECT:Direct. The exit has called the PPI to send data to the this region, and the PPI return code is shown ( P1 ).
This is a diagnostic trace message.
System Action:
None.
User Action:
None.
Reason:
The statistics exit, NMCDSTEX, was called by CONNECT:Direct. The statistics record type is shown ( P1 ). The exit processing ( P2 ) is either IGN, if the record is ignored by the exit, or SES, if the record is to be forwarded to this region. Identification data from the record is shown ( P3 ), which depends on the record type.
This is a diagnostic trace message.
System Action:
None.
User Action:
None.
Reason:
The statistics exit, NMCDSTEX, was unable to retrieve the basic START event data. The problem was in accessing the internal CONNECT:Direct data structure via the Task Control Area (TCA).
System Action:
The event is discarded.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- CONNECT:DIRECT message log
Reason:
The statistics exit, NMCDSTEX, was unable to retrieve the basic START event data. The problem was in validating the internal CONNECT:Direct data structure through the Task Control Area (TCA).
System Action:
The event is discarded.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- CONNECT:DIRECT message log
Reason:
The $RFDATFU procedure issues this message when the debugging option is enabled (&GLBL$RFDATDU=YES).
P1 identifies the phase the procedure is in, and P2 is the supporting text.
System Action:
None.
User Action:
None.
Reason:
An initialization error occurred when processing the ReportCenter or Neugent data feed.
System Action:
The processing terminates.
User Action:
If the error persists, contact Technical Support.
Reason:
You tried to inactivate a NetMaster P1 data feed when no data feed processing was active.
System Action:
The attempted action is not performed.
User Action:
None.
Reason:
The ReportCenter or Neugent data feed is active. The NCL ID of the procedure is P1 .
System Action:
None.
User Action:
None.
Reason:
You tried to start an active ReportCenter or Neugent data feed.
System Action:
The attempted action is not performed.
User Action:
None.
Reason:
You tried to inactivate an inactive NetMaster P1 data feed.
System Action:
The attempted action is not performed.
User Action:
None.
Reason:
The Neugent or ReportCenter data feed has terminated.
System Action:
None.
User Action:
None.
Reason:
The P1 data feed has become active.
System Action:
P1 data feed is active.
User Action:
None.
Reason:
The P1 data feed has become inactive.
System Action:
P1 data feed is inactive.
User Action:
None.
Reason:
The P1 data feed has terminated because of a mapping failure.
P1 is either the REPORTER or the NEUGENT data feed.
P2 is the MDO diagnostic information.
System Action:
The data feed is terminated.
User Action:
Restart the data feed. If the problem persists, contact Technical Support and provide a copy of this message to aid resolution.
Reason:
The file transfer event is missing a source or target address, taskname or product field. The event is not sent to ReportCenter for statistical analysis.
System Action:
None.
User Action:
Check the historical File Transfer record (/FTHIST) and if the problem persists, contact Technical Support.
Reason:
P1 is a required keyword parameter, but it was not passed by the calling process.
System Action:
The procedure sets a return code of 8 and returns processing to the caller.
User Action:
Contact your local Support Center.
Reason:
An invalid keyword value was passed. The keyword is P1 , and the invalid value is P2 .
System Action:
The request is rejected.
User Action:
Contact your local Support Center.
Reason:
A report was submitted for printing in background mode. The request number is P1 .
System Action:
The report is being printed by the Print Services Manager.
User Action:
None.
Reason:
No Records were found for the specified reporting period.
System Action:
The processing terminates.
User Action:
None.
Reason:
The P1 file transfer events EVNTDB NDB has not been started.
System Action:
The processing terminates.
User Action:
Check the Initialization log for the $RF EVENTLOG parameter group, and determine why P1 has not been started.
Access the log as follows:
Step 1. Enter the /PARMS shortcut to list the parameter groups.
Step 2. Enter S beside the EVENTLOG parameter group to display its settings.
Step 3. Press F5 to display the activities logged for the parameter group.
Reason:
An NDB error was encountered during exception report processing.
P1 is an NDB response (or error) code.
P2 is the line number that locates the error in the procedure.
P3 is the NDB command that is being processed when the error occurred.
P4 shows the operands used in the P3 command.
System Action:
The processing terminates.
User Action:
For information about the NDB codes, enter the /NDBERR shortcut at a ===> prompt to display the Browse NDB Error Codes panel. Determine the reason for the error, and take appropriate action.
Reason:
All the file transfer END events required by the exception report filter were found in the specified reporting period.
System Action:
The processing terminates normally.
User Action:
None.
Reason:
The EVNTDB file transfer events database is not available due to maintenance operation, P1 . No exception report processing is possible.
System Action:
The processing terminates.
User Action:
Retry later.
Reason:
Not all the file transfer END events required by the exception report filter were found in the specified reporting period.
System Action:
The processing completes normally.
The following output variables are available at completion:
&$RMMCHKFTOT contains the number of criteria lines in the filter.
&$RMMCHKCRnnn contains the identifier for the nnnth criteria line in the filter. The syntax is the concatenation of the following with > as the delimiter:
- Source Data or Target Data or Transfer ID
- Type
- Number
- Source System/Node
- Target System/Node
- Minimum File Size
- Maximum File Size
For example, SOLVE.SOFT.CD%>TGT>10>>>>> is the criteria for 10 received datasets with names beginning with SOLVE.SOFT.CD.
&$RMMCHKEXnnn contains the number of transfers expected for the nnnth criteria line.
&$RMMCHKFNnnn contains the number of transfers found for the nnnth criteria line.
&$RMMCHKPREQ# contains the print request number if you requested a printed report.
User Action:
None.
Reason:
Not all the file transfer END events required by the exception report filter were found in the specified reporting period.
System Action:
The processing completes normally.
The following output variables are available at completion:
&$RMMCHKFTOT contains the number of criteria lines in the filter.
&$RMMCHKCRnnn contains the identifier for the nnnth criteria line in the filter. The syntax is the concatenation of the following with > as the delimiter:
- Source Data or Target Data or Transfer ID - Type - Number - Source System/Node - Target System/Node - Minimum File Size - Maximum File Size
For example, SOLVE.SOFT.CD%>TGT>10>>>>> is the criteria for 10 received datasets with names beginning with SOLVE.SOFT.CD.
&$RMMCHKEXnnn contains the number of transfers expected for the nnnth criteria line.
&$RMMCHKFNnnn contains the number of transfers found for the nnnth criteria line.
&$RMMCHKPREQ# contains the print request number if you requested a printed report.
Some information, however, is lost because the required value of nnn exceeds 999. This can happen if you included a control (CTL) file in the reporting filter.
User Action:
To view all exceptions, use the online reporting function from the Exception Reporting Menu. To access the menu from any panel, enter
H.ER . Select the required type of filters, and enter E beside the required filter to generate the report.
Reason:
An invalid value has been given for keyword P1 .
System Action:
The request is rejected and the procedure is terminated.
User Action:
Contact your system administrator.
Reason:
The NDB Search did not find any record(s) that match(es) the Extract Criteria.
System Action:
None
User Action:
Change your criteria and retry.
Reason:
The Exit Key has been entered on the Fields Selection List but no fields have been selected. The target file cannot be created without fields.
System Action:
The request is terminated.
User Action:
Redo your request and select one or more fields.
Reason:
An error occurred during a GET function on the vartable P1 for key P2 . The received error code is P3.
System Action:
The request is terminated and the procedure is ended.
User Action:
Contact your system administrator.
Reason:
The user has cancelled the Extract Operation.
System Action:
The Extract file is not created.
User Action:
None
Reason:
An error occurred for the P1 action on NDB P2 . The NDB error code is
P3 and the NDB information code is P4 .
System Action:
The request is terminated and the procedure is ended.
User Action:
Contact your system administrator.
Reason:
The user has cancelled the Search Operation.
System Action:
The Extract file is not created.
User Action:
None
Reason:
Your request to extract file transfer events starts the EVNTDB extract process as a background task that runs with your authority. Progress messages with the prefix RFLO82* are written to the activity log.
System Action:
The process is submitted to your background region.
User Action:
Check the activity log for progress. To access the list of available logs, enter the =H.L panel path.
Reason:
A user cancelled the request to extract file transfer events from the EVNTDB database.
System Action:
The request to extract file transfer events is not processed.
User Action:
None.
Reason:
A request to present a field list failed because an error was encountered accessing a vartable. The request was P1 , the identifier of the vartable was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a field list failed because an error was encountered allocating a vartable. The request was P1 , the identifier of the vartable was P3 and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
An error occurred for the P1 action on NDB P2 . The NDB error code is
P3 and the NDB information code is P4 .
System Action:
The request is terminated and the procedure is ended.
User Action:
Contact your system administrator.
Reason:
You have specified invalid dates.
System Action:
The validation fails.
User Action:
Correct the dates in the highlighted fields.
Reason:
You have specified an invalid date-time combination.
System Action:
The validation fails.
User Action:
Correct the date and time in the highlighted fields.
Reason:
To generate the file transfer exception report, you must specify the period over which you want to report.
System Action:
The validation fails.
User Action:
Specify the date range and optionally, the time range, in the From and To fields.
Alternatively, you can specify a value in the Within the last field.
Reason:
The From and To fields are mutually exclusive with the Within the last field.
System Action:
The validation fails.
User Action:
Specify value in either the From and To fields or the Within the last field, but not both.
Reason:
The P1 fields require valid value.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
An invalid parameter P1 with a value of P2 was passed to $RFFT00L.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The File Transfer Monitor cannot support the LOCATE command due to the complex nature of its key structures and the ability to SORT the list on up to three fields. The FIND command should be used to locate the required information.
System Action:
The request is rejected.
User Action:
Use the FIND command as an alternative.
Reason:
This is an informational message issued by the File Transfer Monitor indicating that some change has occurred for the transfer identified by P2 , which is not in the current window. P1 is either ABOVE or BELOW and indicates the direction in which the change is to be found.
System Action:
None
User Action:
If you want to see the change which has occurred, scroll the list in the indicated direction.
Reason:
The Specified Profile element P1 has been set to the displayed value
P2 .
System Action:
None
User Action:
The File Transfer Monitor will use the new value for its displays.
Reason:
An invalid parameter with value P2 was supplied for the command P1 .
P3 may contain information about the correct values.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry.
Reason:
An attempt by the File Transfer Monitor to allocate its internal tables has failed, probably due to insufficient storage.
System Action:
The Monitor terminates.
User Action:
Contact your support representative.
Reason:
The requested filter was not found. The File Transfer Monitor Filter has been reset.
System Action:
None
User Action:
Define a new File Transfer Monitor Filter.
Reason:
The Specified Profile Element P1 was not changed from its previous value P2 and a redisplay was not done.
System Action:
None
User Action:
None
Reason:
The selected file transfer no longer resides in the internal file transfer table. ENDED or FAILED transfers only remain current for a short time before being removed from the table.
System Action:
The request is rejected. The display is updated and the transfer in question is removed.
User Action:
If information about the transfer in question is required, it may be obtained from the File Transfer Event Database through the Reporting Menu.
Reason:
The request P1 may only be issued against an active transfer.
System Action:
The request is rejected.
User Action:
None
Reason:
Real Time Monitoring is not available for the File Transfer product
P1 .
System Action:
The request is rejected.
User Action:
None
Reason:
A request was made to either START or STOP Real Time Monitoring of a file transfer. If the request was to START Monitoring, then P1 will be
ALREADY , if the request was to STOP Monitoring then P1 will be NOT .
System Action:
The request is rejected.
User Action:
None
Reason:
The TERMINATE command is not available for the File Transfer product
P1 .
System Action:
The request is rejected.
User Action:
None
Reason:
The request requires access to a file transfer manager named P1. The file transfer manager P1 does not exist in the P2 database.
System Action:
The request is rejected.
User Action:
Define a file transfer manager resource.
Reason:
Status monitoring is not available for BSC batch transmissions as CONNECT:Mailbox does not currently provide transmission block/byte count for BSC line activity.
System Action:
The request is rejected.
User Action:
None
Reason:
The P1 file transfer was terminated by the user, P2 .
System Action:
The TCP/IP connection is dropped, and the file transfer is terminated.
User Action:
None.
Reason:
You entered T beside a file transfer to terminate it. However, the associated TCP/IP FTP data connection no longer exists because, for example, the connection failed.
System Action:
The request is aborted.
User Action:
None. The status of the transfer will be updated when the FTP control connection times out.
Reason:
In-progress status monitoring is not available for CA-XCOM file transfers that are executed immediately. Currently, the CA-XCOM application does not provide a command interface to transfers of the
EXECUTE type.
System Action:
The request is rejected.
User Action:
None.
Reason:
The P1 file transfer was terminated by the user, P2 .
System Action:
The file transfer is terminated.
User Action:
None.
Reason:
The T (Terminate) command failed to terminate the P1 file transfer. P2 provides the reason.
System Action:
The CA-XCOM application indicates that it cannot terminate the P1 transfer. If the transfer is active, it will continue.
User Action:
Review the activity log and the CA-XCOM log to deterimine the cause, and correct the problem as required.
Reason:
The TERMINATE command is not supported for CA-XCOM transfers that are executed immediately.
System Action:
The request is rejected.
User Action:
None.
Reason:
In-progress status monitoring is not available for GENAPI file transfers.
System Action:
The request is rejected.
User Action:
None.
Reason:
The TERMINATE command is not supported for GENAPI transfers.
System Action:
The request is rejected.
User Action:
None.
Reason:
In-progress status monitoring is not available for IBM z/OS Communications Server FTP Client/Sever transfers.
System Action:
The request is rejected.
User Action:
None.
Reason:
The process $RFFTALT was called with invalid parmaters.
System Action:
The request is rejected and the process stops.
User Action:
Contact Technical Support.
Reason:
The command P1 is invalid and not supported.
System Action:
The request is rejected.
User Action:
Enter a valid command and retry.
Reason:
The update of a message definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to browse the FTLogs Logs or perform Log Administration but no VSAM log data files are available.
By default, three FTLogs Log VSAM files are defined at NetMaster installation time and allocated and opened at region startup.
FTLogs Logs are VSAM datasets named ?dsnqual.FTLOG01, FTLOG02, FTLOG03 They should be allocated to the region as DD's FTLOG01, FTLOG02, FTLOG03 and a UDBCTL OPEN performed with the same names as the FILEIDs.
Up to 7 files, FTLOG01 - FTLOG03, may be used.
System Action:
Activity Log browse or administration functions are not available.
User Action:
Ensure that at least one FT log VSAM file is correctly allocated and opened.
Use SH VSAM=FTLOG* to check that correctly defined VSAM datasets are allocated as DDNAMEs FTLOG01 and so on.
A UDBCTL OPEN.. should have been performed for each file - recommended parameters are DEFER, LSR, SIS
Refer to the Common Services documentation for more information.
Reason:
The message displays a file transfer event monitor trace record.
P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
No File Transfer Ruleset is loaded in the region so Reactive File Transfer Monitoring cannot proceed.
System Action:
Monitoring by File Transfer Rules is not available.
User Action:
If monitoring by File Transfer Rules is desired, a File Transfer Ruleset must be loaded as follows:
1. Enter the /PARMS shortcut to display the list of parameter groups.
2. Beside the AUTOIDS parameter group, enter U .
3. In the Active Ruleset for File Transfer field, name the File Transfer Ruleset to be loaded.
4. Press F6 (Action) to load the Ruleset.
Reason:
The File Transfer Monitor procedure has encountered an internal system error. P1 is the reason for the failure.
System Action:
Processing continues.
User Action:
Contact Technical Support.
Reason:
A normalised file transfer event cannot be delivered as, there is no active event receiver.
System Action:
The normalised file transfer event is discarded.
User Action:
The FILE TRANSFER EVENT LOGGER ($RFLO81Z) procedure may have terminated.
From an OCS window issue the following command:
SHOW NCL=ALL PROC=$RFLO81Z
Print the activity log from before the time of the first occurrence of message RFFTMON03 till the time just after the above SHOW COMMAND.
Contact Technical Support with this diagnostic data.
Reason:
The number of concurrent file transfer rule alerts in the File Transfer Rules management table has reached the supported limit of P1.
System Action:
File transfer rule alerts are still raised; however, the oldest alerts may not be updated or cleared.
User Action:
This condition can occur when a large number of alerts is raised because too many file transfer events meet the criteria set by one or more file transfer rules. Review the following criteria:
Review the active file transfer rule set, and specify less generic filters.
Close active file transfer rule alerts, and consider setting Alert Autoclear to YES.
Reduce the time-out period.
Reason:
The number of active file transfers in the Active File Transfer Monitor table has reached the supported limit of P1.
System Action:
The oldest file transfers are removed from the Active File Transfer Monitor table (and display) to accommodate newer transfers.
User Action:
Review the FTMONITOR (File Transfer Monitor) Customizer parameter group. Consider reducing the Transfer Visibility values. For example, if you are expecting a large number of file transfer failures in a relatively short period of time, you can reduce the Failed Transfer Visibility from 30 minutes (the default) to 5 minutes.
Reason:
This message displays an FTP transfer event trace record. P1 is the trace ID and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The CA NetMaster FTP event handler procedure failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
The NMFTP Monitor cannot be contacted. The associated error code is P1 and the reason is P2.
The FTP event handler procedure requires an active EPS connection to the NMFTP Monitor (NMFTPMON) for the monitoring of FTP transfer events.
Use the error code P1 to determine why the NMFTP Monitor cannot be contacted:
Indicates that the NMFTP Monitor (NMFTPMON) is not responding to an EPS poll.
Indicates that the SSI (to which this region is connected) is not available or does not provide EPS event support.
Indicates that an internal error has occurred.
System Action:
Processing continues, but FTP events from IBM FTP servers and clients are not available until the problem is corrected.
User Action:
Take appropriate action based on the error code:
Contact your local support representative with a copy of the activity log.
Reason:
The CA NetMaster FTP event handler procedure $RFFTPEN failed. A backup copy has been restarted; its NCL ID is P1. Some FTP file transfer events may have been lost.
System Action:
Processing continues; however, some FTP events from IBM FTP Servers/Client may have been lost.
User Action:
Check the activity log to determine the reason for the initial $RFFTPEN procedure failure.
Contact Technical Support with the diagnostic data obtained from the activity log.
Reason:
The CA NetMaster NMFTP Monitor was previously unavailable and is now operational.
System Action:
The FTP events processing from IBM FTP Servers/Clients resumes.
User Action:
Check for the earliest RFFTPEN02 message in the activity log. This message was issued when the NMFTP Monitor (NMFTPSSI) could not be contacted and gives the associated error code and text. Any IBM FTP Servers/Clients file transfer events from the time of first RFFTPEN02 message until now are lost.
Reason:
An error occurred whilst retrieving the transfer details. The reason is one of the following:
1- REQUEST NOT FOUND The SHOW XMIT command returned the N43C14 or N43D14 message (TRANSMISSION REQUEST DOES NOT EXIST). The command was retried unsuccessfully.
2- INTREAD FAILED WITH xx An INTREAD has failed. xx is the INTREAD failure code.
System Action:
The file transfer event is incomplete. Normal processing continues.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer FTS message handler is ready and is waiting for FTS messages from the FTS region that is managed by FTSMGR,
P1 . The name of the link is P2 .
System Action:
The NetMaster for File Transfer region waits for FTS messages.
User Action:
None.
Reason:
The NetMaster for File Transfer FTS message handler has lost contact with the FTS region, P1 , due to a link failure. Recovery of the link, P2 , is being attempted. The retry count indicates the current number of consecutive attempts. This message will be followed by message RFFTSM02 or RFFTSM03.
System Action:
The system attempts to restart the link.
User Action:
None.
Reason:
The NetMaster for File Transfer FTS message handler is attempting to re-contact the FTS region, P1 , over the link, P2 , following the failure, P3 . Retry count indicates the current number of consecutive attempts.
System Action:
The system will attempt to re-contact the FTS region.
User Action:
None.
Reason:
The NetMaster for File Transfer FTS message handler for the FTS region,
P1 , has failed. The reason for the failure is P2 .
System Action:
The message handler procedure terminates.
User Action:
Proceed as follows according to the reason for the failure:
Reason Action
RETRY LIMIT EXCEEDED Check the status of the link to the FTS region and correct any problems. This message follows messages RFFTSM01 and RFFTSM02.
SIGNON CMD TIMEOUT Check that the BSYS background user of this region has been defined on the FTS region.
The BSYS user ID is of the form xxxxBSYS . To determine the ID for this region, issue SHOW USERS to list the logon users.
xxxxxx CMD TIMEOUT Check the current status of the FTS region and correct any problems.
All other reasons Contact Technical Support.
Reason:
The NetMaster for File Transfer FTS message handler detects that there are currently no receivers for events from the FTS region that is managed by FTSMGR, P1 . The event procedure, P2 , will be started.
System Action:
The required event receiver procedure is started.
User Action:
None.
Reason:
The FTS transmission request, P2 (to or from the FTS region, P3 ), has started. However, the transmission start event could not be generated because the required file names could not be obtained.
System Action:
The generation of the transmission start event is deferred, waiting for message N44x07.
User Action:
If the request specifies DDNAME, check that the BSYS background user of this region is defined to the origin and destination FTS regions. The ID is of the form xxxxBSYS . To determine the ID for this region, issue
SHOW USERS to list the logon users.
If the problem is not because of the above causes, contact Technical Support.
Reason:
The FTS request, P3 ,has completed. However, the expected completion message, P2 , was not received.
System Action:
If the missing FTS message is N44x01 or N44x03, then the transmission end event cannot be generated because the required request name and destination/origin names are unavailable.
If the missing FTS message is N44x07, then the transmission end event is generated. However, the source and/or the target file names cannot be obtained.
User Action:
If the request specifies DDNAME, check that the BSYS background user of this region is defined to the origin and destination FTS regions. The ID is of the form xxxxBSYS . To determine the ID for this region, issue SHOW USERS to list the logon users.
If the problem is not because of the above causes, contact Technical Support.
Reason:
A copy of the NetMaster for File Transfer FTS message handler procedure for the FTS region, P1 , was started. However, this procedure is already running.
System Action:
The procedure start is ignored.
User Action:
None.
Reason:
The P1 NCL procedure could not be loaded on the P2 FTS region. This procedure is required for the FTS file transfer monitoring.
System Action:
The FTS message handler is terminated.
User Action:
Check that the P1 NCL procedure has been installed on the required FTS region. This NCL procedure is distributed with the NetMaster for File Transfer product.
If the problem is not because of the above, contact Technical Support.
Reason:
The FTS agent NCL procedure P1 successfully initialized on the FTS region P2.
System Action:
None.
User Action:
None.
Reason:
The current FTS transmission status indicates an active FTS transmission for which no prior notification has been received. The request name is P1 , the direction is P2 , and the name of the link to the FTS region is P3 .
System Action:
The missing start event is generated.
User Action:
None
Reason:
The command P1 could not be routed via P2 . P2 is not currently active.
System Action:
The command is rejected. Recovery of the INMC link P2 will be attempted.
User Action:
Wait for the automatic INMC link recovery. If the recovery fails use the SHOW LINKS command to determine the status of the link P2.
Reason:
An error has occurred during the signon process to P1. A signon retry will be attempted.
System Action:
The current Signon process is aborted. The cause of the error has been logged in the FTSMGR P1 Transient Log. Signon retry will be attempted.
User Action:
Check the FTSMGR P1 Transient Log for error message(s) to determine the reason for the signon failure. Correct if required and wait for the signon retry.
Reason:
The NetMaster for File Transfer FTS message handler procedure has failed due to a possible data error. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Error condition raised, P3 - Verb operand that has detected the error, P4 , if applicable
- Statement text where the error occurred, P5
System Action:
Message monitoring continues. However, an incomplete File Transfer event may have been generated. If file transfer logging is active, this message is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- A copy of the activity log
Reason:
Recursive errors have been detected in the File Transfer FTS message handler procedure. This message follows messages RFFTSM13 which describe the errors. This message is followed by several NM304xx diagnostic messages.
System Action:
The File Transfer FTS message handler procedure is terminated. If file transfer logging is active, this message is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of the preceding RFFTSM13 messages - Full text of the related NM304xx messages - A copy of the activity log
Reason:
This message displays a file transfer FTS message and events handler trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
This is a diagnostic trace message.
The CA NetMaster FTM FTP post processing exit (NM000FPX) was called by the IBM Communication Server FTP post processing user exit (FTPOSTPR) and the TRACE is currently active.
The FTP event processing selection is identified as follows:
selected-The FTP event is selected for processing by CA NetMaster FTM.
not selected-The FTP event is not selected for processing by CA NetMaster FTM.
System Action:
If P3 = selected, the FTP Event is forwarded to the CA NetMaster FTM region receiving events with a receiver ID of P4.
If P3 = not selected, the FTP Event is not forwarded.
User Action:
Contact Technical Support.
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) was called by the IBM Communication Server FTP post processing user exit (FTPOSTPR) without the required parameter list.
System Action:
The FTP Event processing is aborted.
User Action:
If you provided the IBM Communication Server FTP post processing user exit (FTPOSTPR), check the exit source code to ensure that the CA NetMaster FTP post processing exit (NM000FPX) was called with register one (R1) pointing to the FTP exit parameter list.
If you are using the IBM Communication Server FTP post processing user exit (FTPOSTPR) distributed with CA NetMaster FTM, contact Technical Support.
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) requested the services of the event delivery facility, but the request was rejected because of one of the following:
System Action:
FTP event records are forwarded to the CA NetMaster FTM region when the SSI region (with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) requested the services of the event delivery facility, but the request was rejected because the SSI region is not active.
System Action:
FTP event records are forwarded to the CA NetMaster FTM region when the SSI region (with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The CA NetMaster FTM statistics exit, NMCDSTEX, requested the services of the event delivery facility, but the request was rejected because the SSI is shutting down.
System Action:
The statistics record is not forwarded to the region.
User Action:
Ensure that the SSI region is restarted.
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) issued a $NMXEVNT request to forward an FTP event to the event receiver. The request was rejected. The values of the R0 and R15 return codes from the $NMXEVNT request are P1 and P2, respectively.
System Action:
The event record is not forwarded to the CA NetMaster region.
User Action:
Note the value of R0 and R15, and contact Technical Support.
Reason:
This message is the first of a group of messages that are issued when an abend occurs in the CA NetMaster FTM FTP post processing exit NM000FPX. The following is the complete set of messages:
RFFX06 ABEND at +nnnn in xxxxxxxx xxxx Level xxxxxx RFFX07 R1 at entry: xxxxxxxx, Event add: xxxxxxxx, RcvID: xxxxxxxx, Cmd: xxxx RFFX08 PSW=xxxxxxxx xxxxxxxx Interrupt-Code: xx RFFX09 R0 - R3: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx RFFX09 R4 - R7: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx RFFX09 R8 -R11: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx RFFX09 R12-R15: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Message RFFX06 identifies the abend offset, module, version, and level.
Message RFFX07 identifies the following:
Message RFFX08 identifies the failing PSW and program interruption information.
Messages RFFX09 identify the general purpose registers at the time of the abend.
System Action:
The FTP event record is ignored and processing continues.
User Action:
Contact Technical Support. Ensure that you have the following information available:
Reason:
This message is one of a group of messages issued when an abend occurs in the CA NetMaster FTM FTP post processing exit NM000FPX.
For more information, see the help for message RFFX06.
System Action:
See RFFX06.
User Action:
See RFFX06.
Reason:
This message is one of a group of messages issued when an abend occurs in the CA NetMaster FTM FTP post processing exit NM000FPX.
For more information, see the help for message RFFX06.
System Action:
See RFFX06.
User Action:
See RFFX06.
Reason:
This message is one of a group of messages issued when an abend occurs in the CA NetMaster FTM FTP post processing exit NM000FPX.
For more information, see the help for message RFFX06.
System Action:
See RFFX06.
User Action:
See RFFX06.
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) was called by the IBM Communication Server FTP post processing user exit (FTPOSTPR), which is executing on an unsupported version of the IBM Communication Server.
System Action:
The FTP event is ignored.
User Action:
Do one of the following:
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) requested the services of the event delivery facility, but the request is rejected because the event delivery facility cannot obtain storage (R0=7 and R15=28 returned from $NMXEVNT).
System Action:
The FTP event is not sent to the CA NetMaster FTM region.
User Action:
Contact Technical Support.
Reason:
The CA NetMaster FTM FTP post processing exit (NM000FPX) cannot obtain or free working storage. P1 is the failing request and P2 is the value of the R15 code.
System Action:
The request cannot be processed.
User Action:
Use the R15 code to determine the cause of the error.
Reason:
This is a diagnostic trace message.
The Generic Data Transfer API, NM000FGX, was called with TRACE OPTION ON. The Generic Event record was identified as follows:
P1 is the Transfer ID.
P2 is the Generic Event Type. The valid types are:
S for Transfer Start event
E for Transfer End event
F for Transfer Failure event
P3 is the receiver ID from which Generic Events can be received.
P4 is Generic Event Status and is set to one of the following:
COMPLETE indicates that the Generic Event record was validated and will be forwarded to the NetMaster File Transfer region(s).
INCOMPLETE indicates that an error has occurred. The reason is described by P5 (the return code).
P5 is the return code and is set as follows:
|
RC IN Hex |
Reason |
System Action |
User Action |
|---|---|---|---|
|
0 |
Normal Completion |
(1) |
None |
|
4 |
Transfer ID is missing |
(1) |
(1) |
|
8 |
Transfer ID is invalid |
(1) |
(1) |
|
C |
Event Type is invalid |
(1) |
(1) |
|
10 |
Parameter List Address (R1) is null |
(2) |
(1) |
|
18 |
Event Address is null |
(2) |
(1) |
|
20 |
No active SOLVE SSI with XEVNT support |
(2) |
(2) |
|
24 |
The SOLVE SSI REGION is not active |
(2) |
(2) |
|
28 |
The SOLVE SSI is in shutdown |
(2) |
(3) |
|
2C |
Unable to send EVENT |
(2) |
(3) |
|
40 |
NM000FGX Abended |
(2) |
(1) (3) |
|
44 |
Unable to obtain storage |
(2) |
(3) |
System Action:
For Return Code System Action notes:
(1) The Generic Event is forwarded.
(2) The Generic Event is not forwarded.
User Action:
For Return Code User Action notes:
(1) Check and correct the Generic Event record contents and format.
(2) Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
(3) Check system log for associated RFGEnn message(s).
Reason:
The Generic Data Transfer API, NM000FGX, requested the services of the event delivery facility, but the request was rejected because the SSI is shutting down.
System Action:
The Generic Event record is not forwarded to this region. This data transfer event is lost.
User Action:
To enable this region to receive Generic Events again, ensure that the SSI region is restarted.
Reason:
The Generic Data Transfer API, NM000FGX, issued a $NMXEVNT request to forward a Generic Event to the event receiver. The request was rejected. The values of the R0 and R15 return codes from the $NMXEVNT request are P1 and P2 respectively.
System Action:
The Generic Event is not forwarded to this region.
User Action:
Note the value of R0 and R15, and contact Technical Support.
Reason:
This message is the first of a group of messages that are issued when an abend occurs in the Generic Data Transfer API, NM000FGX. The complete set of messages is:
RFGE06 ABEND AT +nnnn IN xxxxxxxx xxxx LEVEL xxxxxx
RFGE07 R1 at entry=xxxxxxxx, Event add=xxxxxxxx, RcvID=xxxxxxxx, XfrID:xxxxxxxxx--xxxxx, Type:x
RFGE08 PSW=xxxxxxxx xxxxxxxx INT=xxxxxxxx
RFGE09 R0-R3 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFGE09 R4-R7 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFGE09 R8-R11 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFGE09 R12-R15 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Message RFGE06 identifies the abend offset, module, version, and level.
Message RFGE07 identifies the parameters passed by the caller:
R1 at entry is the value in R1 when the API was called.
Event add is the address of the Generic Event record.
RcvID is the receiver ID from which Generic Events can be received. If either R1 or the event address was invalid, this is shown as ????????.
Xfrid is the first 16 characters of the Transfer ID. If either R1 or the event address was invalid, this is shown as ????????????????.
Type is the Generic Event type. If either R1 or the event address was invalid, this is shown as ?.
Message RFGE08 identifies the failing PSW and program interruption information.
Messages RFGE09 identify the general purpose registers at the time of the abend.
System Action:
The Generic Event is ignored, and processing continues.
User Action:
Check and correct the calling module.
If the problem is not in the calling module, then Contact Technical Support. Ensure that you have the following information available:
- The entire group of messages (RFGE06 to RFGE09)
- The assembly listing of the caller module.
Reason:
This message is one of a group of messages that are issued when an abend occurs in the Generic Data Transfer API, NM000FGX.
R1 at entry is the value in R1 when the API was called.
Event add is the address of the Generic Event record.
RcvID is the receiver ID from which Generic Events can be received. If either R1 or the event address was invalid this is shown as ????????.
Xfrid is the first 16 characters of the Transfer ID. If either R1 or the event address was invalid, this is shown as ????????????????.
Type is the Generic Event type. If either R1 or the event address was invalid, this is shown as ?.
For more information, see the help for message RFGE06.
System Action:
See RFGE06.
User Action:
See RFGE06.
Reason:
This message is one of a group of messages that are issued when an abend occurs in the Generic Data Transfer API, NM000FGX.
For more information, see the help for message RFGE06.
System Action:
See RFGE06.
User Action:
See RFGE06.
Reason:
This message is the last of a group of messages that are issued when an abend occurs in the Generic Data Transfer API, NM000FGX.
For more information, see the help for message RFGE06.
System Action:
See RFGE06.
User Action:
See RFGE06.
Reason:
The Generic Data Transfer API, NM000FGX, requested the services of the event delivery facility, but the request was rejected because the event delivery facility could not obtain storage (R0=7 and R15=28 returned from $NMXEVNT).
System Action:
The Generic Event is not sent to the event receiver.
User Action:
Contact Technical Support.
Reason:
The Generic Data Transfer API, NM000FGX, was unable to obtain or free up working storage. P1 is the failing request, and P2 is a code that indicates the reason of the failure.
System Action:
The request cannot be processed.
User Action:
Use the R15 code to determine the cause of the error.
Reason:
A Generic Data Transfer API file transfer has started:
- P1 identifies the transfer as Unique transfer ID.
- P2 is the initiator user Id and P3 is the initiator node.
This message is followed by RFGEEV02 which provides additional details.
System Action:
None.
User Action:
None.
Reason:
A Generic Data transfer API file transfer has started:
- P1 identifies the transfer as the transfer ID.
- P2 is source node and P3 is the target node.
This message follows message RFGEEV01.
System Action:
None.
User Action:
None.
Reason:
A Generic Data Transfer API file transfer has completed successfully:
- P1 identifies the transfer as a Unique transfer ID.
- P2 is source node and P3 is the target node.
System Action:
None.
User Action:
None.
Reason:
A notification has been received from Generic Data Transfer API, indicating a failed file transfer:
- P1 identifies the transfer as a Unique transfer ID.
- P2 is source node and P3 is the target node.
This message is followed by RFGEEV11 which provides error details.
System Action:
None.
User Action:
None.
Reason:
A non-orderly GENAPI shutdown notification was received from P1 .
System Action:
A file transfer failure event will be raised for each currently active GENAPI transfer (if any).
User Action:
If desired, restart the GENAPI application.
Reason:
The region received a file transfer completion event for the P1 file transfer but never received the corresponding START event.
System Action:
The region will create a dummy START event for this file transfer. Processing continues.
Important! The created START event uses data from the END event. The start time, the user name, and the transfer rate might be incorrect.
User Action:
None.
Reason:
A Generic Data Transfer API file transfer failed, but no error message was received from the Generic Event API region.
System Action:
None.
User Action:
Review the system log and check the User Product region to determine the cause of the failure.
Reason:
A non-orderly GENAPI shutdown notification was received from P1 .
System Action:
A file Transfer FAILURE event is raised.
User Action:
You may want to review the reasons for the GENAPI termination.
Reason:
A notification has been received from the GENAPI, indicating a failed file transfer:
- P1 identifies the transfer as a Unique transfer ID.
- P2 is error text.
This message follows message RFGEEV05.
System Action:
None.
User Action:
None.
Reason:
This is a warning message and notifies you that P1 of the Start Event pool allocated in the GE API parameter group is being used. This may be because END or FAILURE Events are not being passed for all START Events.
System Action:
Event processing continues.
User Action:
Monitor these messages and associated alerts, if the problems persists ensure that Start Events have corresponding End or Failure Events. You can issue FTMGEST at the command prompt to view detail of START Events yet to be processed by the Generic Data Transfer API Event Manager.
Reason:
The START Event Pool is 100% used. The event is lost. P1 provides detail of the event.
System Action:
Event processing continues.
User Action:
Ensure that GENAPI is passing END or FAILURE events for all processed START events. Use the FTMGEST command to view details of all current START events yet to be processed by the GENAPI Event Manager.
Reason:
The Generic Data Transfer API Event Manager procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The Generic Data Transfer API Event Manager did not receive a Start Event for a transfer and no Start Date was specified in the End Event. The End Event is generated with the Start Date being equal to the end time.
System Action:
The event is processed.
User Action:
Correct the data passed by the Generic Data Transfer API from your data transfer application.
Reason:
The Generic Data Transfer API Event Manager did not receive a Start Event for a transfer and no Start Date was specified in the End Event. The End Event is generated with the Start Date equal to the end time.
System Action:
The event is processed.
User Action:
Correct the data passed by the Generic Data Transfer API from your data transfer application.
Reason:
The Generic Data Transfer API Event Manager procedure has encountered a recoverable error. Check previous messages for the cause of the error.
System Action:
Event processing continues. However, some events may have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant activity log messages
- Generic Application log messages
Reason:
The Generic Data Transfer API Event Manager procedure has failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP - Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The Generic Data Transfer API Event Manager procedure has failed due to a data error in the event received from you data transfer application. The error is indentified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- Statement text where the error occurred, P6
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is then ignored.
If file transfer logging is active, it is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The message displays a file transfer event trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The Generic Data Transfer API Event Manager could not process an event. This results in the loss of the event.
P1 describes the field in error.
System Action:
The event is discarded.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Generic Application message log
Reason:
The Generic Data Transfer API Event Manager could not process an event.
P1 describes the field in error.
MDO information follows the message.
System Action:
The event is discarded.
User Action:
Correct the Event Type information passed by the Generic Data Transfer API from your data transfer application.
If the problem cannot be rectified contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Generic Application message log
Reason:
The Generic Data Transfer API Event Manager cannot process a value received from your data transfer application.
P1 describes the field in error.
MDO information follows the message.
System Action:
The event is processed.
User Action:
Correct the data passed by the Generic Data Transfer API from your data transfer application.
If the problem cannot be rectified, contact Technical Support with the following diagnostic information:
- Full text of this message
- Generic Application message log
Reason:
No Generic Data Transfer Application API Event data is available.
System Action:
None.
User Action:
None.
Reason:
There is no active transfer event data available for product P1 .
System Action:
None.
User Action:
None.
Reason:
The delete of ACTIVE Transfer P1 failed. The transfer is no longer active.
System Action:
Delete processing fails.
User Action:
Press F6 (Refresh) to ensure that the selected transfer is available.
If the problem persists, contact Technical Support.
Reason:
The delete of ACTIVE Transfer P1 was successful.
System Action:
None.
User Action:
None.
Reason:
The delete of all Event Data for Product ID P1 is successful.
System Action:
None.
User Action:
None.
Reason:
The Generic Data Transfer API FTMGEST Command Display Procedure failed due to an MDO error. The failure is identified by the following:
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support with the following diagnostic information:
We recommend that you obtain the information immediately as follows:
Note: If you use a 3270 terminal emulator and print the diagnostics using the cut and paste procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The Generic Data Transfer API Event Manager procedure is not active or is no longer profiled to accept ACTIVE Transfer deletion requests.
System Action:
Delete processing is aborted.
User Action:
Contact Technical Support.
Reason:
A list of CDMON Templates was presented for generation of Monitor resources, but the list was exited without any being selected.
System Action:
No Monitor resources are generated.
User Action:
If Monitor resources are to be generated, select the template(s) on which these resources will be modelled by entering s beside them.
Reason:
The field P1 is required and must not be null.
System Action:
Field is set in error.
User Action:
Specify a value for P1 .
Reason:
The file P2 could not be allocated or unallocated or the process timed out. P1 indicated if the action was to allocate the file P2 or to unallocate it.
System Action:
Processing terminates.
User Action:
Check the activity log for messages that may indicate why the process timed out. Retry by actioning the parameter group.
Reason:
This region includes the capability to send data to ReportCenter, but this function is not yet activated. Until it is, the Send Event Rate Data to ReportCenter field must remain set to NO.
This message occurs if the REPORTDATA or REPORTCENTER parameter group is present In this region but has never been updated.
The ReportCenter data feed will remain dormant until either of these groups is updated and actioned.
System Action:
None.
User Action:
If you have not or do not want to implement the ReportCenter feature, leave this field set to NO.
If you want to enable this region to send data to ReportCenter, you must update and action the REPORTDATA or the REPORTCENTER parameter group, whichever is present In this region.
Implement the ReportCenter control region and the ReportCenter Java Task first to ensure that there is an application to receive the data feed.
Note: For more information on ReportCenter implementation, see the ReportCenter Guide.
If you do not implement ReportCenter, you can still see example reports at the following URL:
http://?your-host-and-port/public/reports/reportexpo.esp
?your-host-and-port is the IP address of this system and the port number of your WebCenter web interface port
Example: http://192.168.66.44:8744/public/reports/reportexpo.esp
Reason:
The field P1 is required if the field P2 is specified.
System Action:
The field is set in error.
User Action:
Specify a value for P1 , or blank out the value for P2 .
Reason:
When customizing a parameter group that allows for multiple occurrences of an item, you entered a value, P1, in a field; however, the value is in use by another field of the same type. This is invalid because values must be unique.
For example, when defining the file transfer logs, you can enter details for up to seven log files. The file IDs and the data set names must be unique. This message is issued if a file ID or a data set name that matches an existing entry is entered.
System Action:
Field is set in error.
User Action:
Specify a unique value.
Reason:
The field P1 is required and must not be null.
System Action:
Field is set in error.
User Action:
Specify a value for P1 .
Reason:
The file transfer log file with ID P1 was not allocated because the key length of the file was invalid. The key length of the file was P2 , but it should have a length of 22.
System Action:
The log file is not available for use.
User Action:
Review the $RF FTLOGS parameter group. Ensure that the correct dataset name is specified.
If the name is incorrect, change it to the correct dataset name.
If the name is correct, this indicates that the VSAM cluster was not defined correctly. Use Access Method Services to delete and redefine the cluster, ensuring that a key length of 22 is specified.
When you have corrected the problem, action the $RF FTLOGS parameter group.
Reason:
There was an error during the allocation of file FTSCHD in ICS Parameter Group FTSCHD. The key length shown in P1 is incorrect.
System Action:
None.
User Action:
The correct key length should be 46. Ensure that file FTSCHD has been allocated with a key length of 46.
Reason:
There was an error during the allocation of file FTSCHD in ICS parameter group FTSCHD.
System Action:
None.
User Action:
Refer to previous messages in the log to correct this error.
Reason:
The $RF FTLOGS parameter group has specified that file transfer logging is not required.
System Action:
If file transfer logging is currently enabled, the existing file transfer log procedure is flushed. The file transfer log files are not unallocated and may still be viewed.
User Action:
File transfer logging may be reactivated by updating the $RF FTLOGS parameter group to specify that logging is now required and then activating the updated group.
Reason:
The specified file ID, P1 , is invalid. File IDs for file transfer logs must be of the following form:
- A fixed prefix (FTLOG)
- A two digit numeric suffix (01 through 10)
The file ID must be in the range P2 through P3 .
System Action:
Field is set in error.
User Action:
Correct the file ID to conform to the required format.
Reason:
No file transfer log files were allocated because of errors. Logging cannot be enabled until at least one file transfer log file is available for logging.
System Action:
File transfer logging is disabled.
User Action:
From the Customizer : Parameter Groups panel (/PARMS), enter L beside the FTLOGS parameter group to view the messages relating to this group. Use the messages to determine the reason for the error. Correct the situation, then action the group to reactivate the logging function. File it when its parameters are set successfully.
Reason:
One or more, but not all, file transfer log files were successfully allocated, and logging has started. Additional messages are written to the initialization log.
System Action:
File transfer logging continues with those logs that were successfully allocated.
User Action:
From the Customizer : Parameter Groups panel (/PARMS), enter L beside the FTLOGS parameter group to view the messages relating to this group. Use the messages to determine the reason for the error. Correct the situation, then action the group to reactivate the logging function. File it when its parameters are set successfully.
Reason:
There was an error during the delete of a record from file FTSCHD in ICS Parameter Group FTSCHD. The File Return Code is shown in P1 and the VSAM Feedback Code is shown in P2.
System Action:
None.
User Action:
Investigate the VSAM Feedback Code and take the appropriate action.
Reason:
When disabling schedule logging in ICS parameter group FTSCHD the number of records specified by P1 were deleted from file FTSCHD.
System Action:
None.
User Action:
None.
Reason:
The event receiver identified by P1 has status indicated by P2 .
System Action:
None.
User Action:
None.
Reason:
The region is unable to activate the FTP event receiver at this time because it is not connected to an SSI region. The SSI region is required for FTP event delivery.
System Action:
Activation of the FTPCNTL parameter group fails.
User Action:
Check the SSI parameter group. Ensure that a value has been specified in the Sub- System Interface ID field and that the specified SSI is set up to provide EndPoint Servies (EPS). Activate the SSI parameter group, then reactivate the FTPCNTL parameter group.
Reason:
An attempt to activate the FTP event receiver has failed. More information can be found in the activity log.
System Action:
None.
User Action:
Check the activity log for further information.
Reason:
An attempt to activate the FTP event receiver has been initially unsuccessful.
System Action:
Activation will be retried at regular intervals until it succeeds.
User Action:
This situation may occur if the SSI region is unavailable at the time the receiver is activated. Check that the SSI region is available.
Reason:
This region includes the capability to send data to ReportCenter. The procedure to collect file transfer event rate data and forward it to the ReportCenter database has been started.
System Action:
File Transfer reporting data collection will commence.
User Action:
If this is the very first start of this region, ensure that either the REPORTDATA or REPORTCENTER parameter group has also been correctly updated and actioned. If this is not the case, update and action the group immediately.
This region will include the REPORTCENTER group if it has been set up to be the ReportCenter Control Region, otherwise it will include the REPORTDATA group. These groups provide the underlying infrastructure to send data to ReportCenter. The REPORT* group on this region must have been successfully actioned before any data can be sent.
The EVENTLOG group controls the generation of file transfer report data at an application level, but is not concerned with its transportation.
Reason:
The procedure to collect file transfer data and forward it to the ReportCenter database has been stopped.
System Action:
File transfer data collection for ReportCenter is disabled. No reporting data will be produced until data collection is restarted.
User Action:
To ensure continuity of report data, if you are using the ReportCenter file transfer reports, data collection should run continually.
Data collection should generally only be stopped for environmental reasons, such as the ReportCenter database being unavailable for a prolonged period of time.
For short time periods, collected data will be accumulated for sending to the database when full service resumes.
To start file transfer data collection for ReportCenter, set the "Send Event Rate Data to ReportCenter?" field in the EVENTLOG parameter group to YES, and action the group. Ensure that the REPORTCENTER or REPORTDATA group has also been correctly updated and actioned.
Reason:
This region does not include the ReportCenter component. The procedure to collect the file transfer data and forward it to the ReportCenter database has been stopped.
System Action:
None. ReportCenter functions are not available from this region.
User Action:
If you do not want to use ReportCenter, this message may be disregarded.
If you want to enable ReportCenter in this region, redo the region setup to include the ReportCenter component. This adds PROD=REPORTER to the region's U28 input parameter member.
After starting the region, you need to:
Note: For details, see the ReportCenter Guide.
Start file transfer data collection for ReportCenter. Set the Send Event Rate Data to ReportCenter? field in the EVENTLOG parameter group to YES, and action the group.
Reason:
The data set, P1 , is not defined with the properties of a P2 data set.
System Action:
Validation fails.
User Action:
Redefine the data set, or specify another data set in the input field provided. For information about the attributes of the EVNTDB and EVNTARC data sets, see the Installation and Setup Instructions.
Reason:
A generation dataset was specified for the EVNTARC dataset, but the dataset attributes are incomplete.
System Action:
Field in error is highlighted.
User Action:
Supply the required attributes.
Reason:
The value, P1 , is not a valid measure for dataset space. Valid values are CYL and TRK.
System Action:
None
User Action:
Enter one of the following values in the Space Type field:
- CYL to request that the space be allocated in cylinders.
- TRK to request that the space be allocated in tracks.
Reason:
The value, P1 , is not a valid dataset space allocation amount. The value must be numeric.
System Action:
None
User Action:
Enter a number for the space allocation amount.
Reason:
Enter either model DSCB name or SMS data class for GDG to model the new generation dataset. You cannot use model DSCBs with SMS-managed generation datasets.
System Action:
None.
User Action:
Specify either the model DSCB name or the SMS data class for GDG to model the new generation dataset, but not both.
Reason:
The automatic password option of the CDAPI parameter group requires the CONNECT:Direct user to be defined to UAMS. If the option is set to YES the system will attempt to automatically add the user to the UAMS file. If the attempt is unsuccessful this message is displayed.&P1&is the message returned by the &SECCALL ADD function.
System Action:
Message displayed. Processing allowed to continue.
User Action:
Determine why the ADD failed (the user may already be defined) and if required, correct the problem and manually add the user.
Reason:
The option is not available because the security exit is not installed.
System Action:
Message displayed. Processing is allowed to continue.
User Action:
If required, install the security exit.
Reason:
The EVENTLOG is currently in a failed state and requires the use of
P1 that contains the event records unloaded during a failure. The EVNTSEQ dataset specified is different from the dataset used for the unload of the event records.
System Action:
Message displayed. Processing is allowed to continue.
User Action:
Specify the required dataset for this field if the unloaded event records are to be used for recovery. A null value for this field will discard any previously unloaded records.
Reason:
The dataset P1 will be allocated at system initialization since a DMPRINT is in use by another dataset.
System Action:
Message displayed. Processing allowed to continue.
User Action:
None
Reason:
The parameters necessary for REORG UNLOAD are invalid. The required parameters are:
Enable Event Logging ......... NO (required)
EVNTDB Database Name ......... P1 (EVNTDB to be reorganized)
EVNTSEQ Reorg Dataset ........ sequential dataset (work dataset for REORG)
System Action:
Error message displayed. Validation is allowed to continue.
User Action:
Correct the parameters and press PF6 to initiate the REORG UNLOAD.
Reason:
The parameters necessary for REORG RELOAD are invalid. The required parameters are:
Enable Event Logging ......... YES (required)
EVNTDB Database Name ......... VSAM dataset name (must have space to at LEAST contain all the unloaded records )
EVNTSEQ Reorg Dataset ........ P1 (must be the same dataset used in the UNLOAD step)
System Action:
Error message displayed. Validation is allowed to continue.
User Action:
Correct the parameters and press F6 (Action) to initiate the REORG RELOAD.
Reason:
The parameters provided will skip REORG processing and instead attempt to format and use a new EVNTDB. The required parameters are:
Enable Event Logging ......... YES
EVNTDB Database Name ......... VSAM dataset (newly defined VSAM dataset) EVNTSEQ Reorg Dataset ........ (null value - no work dataset)
System Action:
Warning message displayed. Validation is allowed to continue.
User Action:
If reorganization is to be ignored, press F6 (Action) to start logging using the new EVNTDB, and to release the lock.
Reason:
No EVNTSEQ Reorg dataset was provided. Automatic reorganization is not possible with this setting.
System Action:
Warning message displayed. Processing continues.
User Action:
If automatic reorganization is required, provide a valid dataset for EVNTSEQ and press F6 (Action) to implement the change.
Reason:
The EVNTDB Logger failed to respond and indicate its current status.
System Action:
Processing continues.
User Action:
Check the log for possible initialization errors and take corrective action if necessary.
Reason:
An invalid field separator character was specified. The valid characters are:
` ! * - + | \ : ; < > ? / ,
The literal delimiter character TAB is also valid and internally represented as EBCDIC X'05'. If nothing is specified, the separator defaults to a comma (,).
System Action:
Processing continues.
User Action:
Specify a valid character separator.
Reason:
An attempt to action the Event Log parameter group failed because automatic reorganization of the EVNTDB is in progress.
System Action:
Request rejected.
User Action:
Check log to monitor the progress of the reorganization. Retry the action after successful completion of the reorganization process.
Reason:
The FTPCNTL parameter group disabled data space monitoring.
System Action:
Data space monitoring is disabled.
User Action:
None.
Reason:
The specified time period cannot be less than 30 seconds.
System Action:
Validation fails.
User Action:
Specify a valid time period.
Reason:
The field contains an invalid value. The only valid values are a number between 10 and 9999.
System Action:
Field is set in error.
User Action:
Specify a number between 10 and 9999.
Reason:
The EVENT DB Database name cannot be changed while event logging is set to YES.
System Action:
Error message displayed.
User Action:
To change the EVNTDB Database Name:
1- Set the Enable Event Logging field to NO.
2- Change the name of the EVNTDB.
3- Set the Enable Event Logging field to YES.
Reason:
The FTPCNTL parameter group disabled TCPaccess FTP Server event receipt.
System Action:
TCPaccess FTP Server event receipt is disabled.
User Action:
None.
Reason:
The FTPCNTL parameter group disabled Non TCPaccess event receipt.
System Action:
Non TCPaccess event receipt is disabled.
User Action:
None.
Reason:
The CONNECT:Direct Command API work file DDNAME: DMPRINT has been allocated to a temporary file.
System Action:
Processing continues.
User Action:
None.
Reason:
The CONNECT:Direct Command API work file DDNAME: DMPRINT is already allocated and will be reused.
System Action:
Processing continues.
User Action:
None.
Reason:
An internal error has occurred.
The CONNECT:Direct Command API work file DDNAME: DMPRINT cannot be allocated. P1 is the error text.
System Action:
The CONNECT:Direct Command API responses are disabled.
User Action:
Contact Technical Support with the full text of this message.
Reason:
The CONNECT:Direct Command Interface procedure was invoked for a CDMGR but was unable to ascertain the values for the NETMAP and MSGFIL datasets. The file names which could not be derived are identified by P1 while P2 identifies the CONNECT:Direct manager.
The reason for the failure could be because the INQUIRE INITPARMS command issued to CONNECT:Direct was unsuccessful or because the $RFXPRMS exit was not modified to provide the required file names.
Including the CDMGR resource's file names in the $RFXPRMS exit will bypass the need for the command API to issue the INQUIRE INITPARMS command to obtain these file names.
NB. For V1.8 of CONNECT:Direct the $RFXPRMS exit MUST be modified as this release of CONNECT:Direct does not support the INQUIRE INITPARMS command.
System Action:
The request is rejected. The interface procedure ends with return code 16.
User Action:
Update the $RFXPRMS exit to include the file names of the NETMAP and MSGFIL datasets for the nominated CDMGR resource. If running a version of CONNECT:Direct later than V1.8 the file names should be able to be dynamically extracted by use of the INQUIRE INITPARMS command. In this case check that the userid defined in the CDAPI parameter group is defined to CONNECT:Direct and has the necessary authority. Also check that the CMD clist is available in the CONNECT:Direct OPLIST dataset.
Reason:
No file transfer log files are available. Logging of file transfer details terminates.
System Action:
The file transfer log procedure terminates.
User Action:
From the Customizer : Parameter Groups panel (/PARMS), enter L beside the $RF FTLOGS parameter group and review the displayed initialization log.
If the log indicates that errors have occurred, correct them.
If the log shows no errors, enter L beside a logged message and browse the displayed activity log for related messages. Correct any errors indicated by these messages.
Reason:
No file transfer log files are available. Logging of file transfer details terminates.
System Action:
The file transfer log procedure terminates.
User Action:
From the Customizer : Parameter Groups panel (/PARMS), enter L beside the $RF FTLOGS parameter group and review the displayed initialization log.
If the log indicates that errors have occurred, correct them.
If the log shows no errors, enter L beside a logged message and browse the displayed activity log for related messages. Correct any errors indicated by these messages.
Reason:
The executing process with the specified NCL ID has been flushed to enable a log swap to take place. If a user is associated with this process (for example, the user might be browsing the log), the user region will be terminated.
System Action:
The file transfer log swap commences when there are no users.
User Action:
None
Reason:
The user, P1 , was accessing a file transfer log file for which a log swap was required. For example, the user might be browsing the log. The user region was terminated to enable the log swap to take place.
System Action:
The file transfer log swap commences when there are no users for the log file.
User Action:
None
Reason:
The NetMaster for File Transfer log procedure has been started, but there is already an active file transfer log procedure. The current procedure, with NCL ID P1 , is flushed. The new log procedure has an NCL ID of P2 .
System Action:
The old file transfer log procedure terminates, and the new log procedure runs in its place. Additional messages are written to the activity log as a result of the old log procedure being flushed.
User Action:
No action is required. This message is for information and audit trail only.
Reason:
The NetMaster for File Transfer log procedure has received an event where the date is different to the previous event (or this is the first event since the procedure was started). The procedure swaps to the file indicated in the message. (File transfer events raised on different dates are logged to different log files.)
File transfer messages are now written to the log file with file ID= P1 .
System Action:
File transfer logging continues.
User Action:
No actions are required. The message is for information and audit trail only.
Reason:
The NetMaster for File Transfer log procedure has failed to write a message to the current file transfer log file. The current file will be swapped, and logging will continue.
The failure is identified by the following:
- Current file ID, P1
- File request, P2 , that indicates either OPEN or ADD, and the NCL &FILE operation that has failed
- Key of the record, P3 (only relevant if the file request is ADD)
- File return code, P4 , which is the &FILERC value
- VSAM feedback code, P5 , in hexadecimal format (normally only relevant if the return code is 8)
- System message, P6 , if any (normally only relevant if the return code is 16)
A full file is indicated by the following conditions:
- File request is ADD. - File return code is 8. - VSAM feedback code is 1C.
System Action:
File transfer logging continues.
User Action:
If the message indicates that the file is full, no action is required as the next log file will be used. If a secure copy of the file is needed, you should arrange to copy the file before it is reset during the normal cycling of log files.
Other errors indicate problems with the region or the particular file. If a system message is included (MSG=), see to the help for that message to help you resolve the problem. If the VSAM feedback code is included (FDBK=), use the request type and feedback code to reference your VSAM reference manual and follow the problem diagnosis.
If the problem cannot be resolved, contact Technical Support.
Reason:
The log procedure for CA NetMaster FTM received a local time offset change notification.
P1 is the direction of the local time offset move; it is forward or backward.
P2 is the previous local time offset (d.hhmm - day hours minutes)
P3 is the new local time offset (d.hhmm - day hours minutes)
Note: File Transfer Log lines always display the local system time. When a backward time change occurs, for example, for daylight saving, the local system time moves back; however, log records may already be written for this time interval.
System Action:
Logging continues.
User Action:
None.
Reason:
This message is issued when an FTSMON link monitor detects an inactive link to a monitored region or a link check is requested by message RFLINK05.
P1 is the link name.
P2 is the link status.
System Action:
The monitor procedure issues message RFLINK02, which causes the related FTSMGR and FTSMON resources to change status.
User Action:
None.
Reason:
An FTSMON link monitor resource is unable to communicate with its FTSMGR resource.
P1 is the FTSMGR name.
P2 is the FTSMON name.
P3 is the time.
System Action:
The extended display of the FTSMON and FTSMGR resources is set.
User Action:
The problem can be due to the following possible causes:
- No DEFLINK command has been issued from the FTSMGR region.
To correct the problem, issue a DEFLINK command from the FTSMGR region, for example:
DEFLINK MASK=* PREFIX=link-prefix
To enable the automatic execution of the command during the startup of the FTSMGR region, include the command in the NMREADY procedure for the region.
- The BSYS user of the NetMaster for File Transfer region is not defined to the FTSMGR region.
To correct the problem, define the user to the FTSMGR region.
To detemine the user ID, issue SHOW USERS from the NetMaster for File Transfer region to display the list of logon users.
After you corrected the problem, enter CHK beside the FTSMON resource.
Reason:
An FTSMON resource has detected that its monitored link is not active.
P1 is the FTSMGR name.
P2 is the FTSMON name.
P3 is the TIME.
P4 is the LINK name.
System Action:
The EXTENDED DISPLAY of the FTSMGR and FTSMON resources is set.
User Action:
Determine the cause of the link being inactive and rectify.
Reason:
An FTSMON resource has found its monitored link to be active.
P1 is the FTSMGR name.
P2 is the FTSMON name.
P3 is the TIME.
P4 is the LINK name.
System Action:
The EXTENDED DISPLAY of the FTSMON resource is set.
User Action:
None.
Reason:
An FTSMON resource whose monitored link was previously inactive has now detected that the link is active. This message is issued to cause the FTSMGR to reset any error display and other FTSMON resources to check their links.
P1 is the FTSMGR name.
P2 is the FTSMON name.
System Action:
The FTSMGR's EXTENDED DISPLAY is reset. All other FTSMON resources check their links and set errors as appropriate.
User Action:
None.
Reason:
The heartbeat value in the resource definition was less than the minimum global value. The heartbeat value is increased automatically to P1 .
System Action:
The heartbeat value is increased automatically to the minimum value.
User Action:
None.
Reason:
The message displays a file transfer events logger trace record.
P1 is the trace ID, and P2 is the trace text.
System Action:
None
User Action:
Contact your local support representative.
Reason:
An attempt was made to start the Event Logger, but it was already running.
System Action:
The existing Event Logger continues to operate.
User Action:
None
Reason:
The Event Logger encountered an error when trying to perform a P1 command on the EVNTDB database. The return code is P2 . The Event Logger may terminate or continue processing as indicated by its status.
System Action:
The Event Logger may terminate if it cannot continue processing.
User Action:
Check the activity log for further messages indicating why the NDB error occurred. To display the log, enter the =H.L panel path.
If the NDB is full, redefine it with more space. For information about the attributes of the distributed database, see the Installation and Setup Instructions.
Reason:
The event logger received a VSAM I/O error when trying to add a record to the EVNTDB database. This is a serious error resulting in the event logger terminating. The most likely reason for this error is that the EVNTDB database is full.
System Action:
The event logger cannot continue processing and has terminated. The EVNTDB database probably has a status of BAD-LOCKED .
User Action:
Check the activity log for further messages that indicate why the I/O error occurred. To access the log, enter the =H.L path.
If the NDB is full and is marked BAD-LOCKED , you must delete and redefine the NDB. However, before doing this, if you want to extract the data currently in the NDB, perform the following steps:
1. Issue the NDB START EVNTDB UNLOCK INPUT command to open the database as input-only. If you issue this command without the INPUT option, the region will attempt to reapply the last transaction, causing the NDB to remain BAD-LOCKED .
2. Type the name of your extract dataset into the field provided on the History Data menu ( =/FTHIST ), and select option EX to start the extract process.
3. Go to the activity log ( =H.L ) for progress messages on the extract process.
4. When the extract process has finished, deallocate the EVNTDB database by issuing the following commands:
- NDB STOP EVNTDB to stop the database - UDBCTL CLOSE=EVNTDB to close the file - DEALLOC DD=EVNTDB to deallocate the file
5. After the EVNTDB database has been deallocated, submit your batch job to delete and redefine the dataset (optionally giving it more space). For information about the attributes of the distributed database, see the Installation and Setup Instructions .
6. Upon successful completion of the batch job, go to the list of parameter groups ( =/PARMS ), and enter U (Update) beside the EVENTLOG parameter group. You might want to decrease the number of days records are to be stored within the database.
7. Press F6 (Action) to action the parameters. This reinitializes the event logging environment, and the event logger should restart with no problems.
8. Press F3 (File) to save your current parameter settings and exit, or F12 (Cancel) if you do not wish to save the changes you have made.
Reason:
The event logger tried to add a record to the EVNTDB database and discovered that the database was locked. This is a serious error, and the event logger has terminated. The most likely reason for this error is that the EVNTDB database has become full.
System Action:
The event logger cannot continue processing and has terminated. The EVNTDB database is in a status of LOCKED or BAD-LOCKED.
User Action:
Check the activity log for further messages that indicate why the I/O error occurred. To access the log, enter the =H.L path.
It is uncommon for the NDB to have the LOCKED status. However, if this occurs, issue an NDB START EVNTDB UNLOCK command and then action the EVENTLOG parameter group. To access the list of parameter groups, enter the =/PARMS path.
If the NDB is full and has the BAD-LOCKED status, the only solution is to delete and redefine the NDB. However, before doing this, if you wish to extract the data currently in the NDB, perform the following steps:
1. Issue the NDB START EVNTDB UNLOCK INPUT command to open the database as input-only. If you issue this command without the INPUT option, the region will attempt to reapply the last transaction, causing the NDB to remain BAD-LOCKED .
2. Type the name of your extract dataset into the field provided on the History Data menu ( =/FTHIST ), and select option EX to start the extract process.
3. Go to the activity log ( =H.L ) for progress messages on the extract process.
4. When the extract process has finished, deallocate the EVNTDB database by issuing the following commands:
- NDB STOP EVNTDB to stop the database - UDBCTL CLOSE=EVNTDB to close the file - DEALLOC DD=EVNTDB to deallocate the file
5. After the EVNTDB database has been deallocated, submit your batch job to delete and redefine the dataset (optionally giving it more space). For information about the attributes of the distributed database, see the Installation and Setup Instructions .
6. Upon successful completion of the batch job, go to the list of parameter groups ( =/PARMS ), and enter U (Update) beside the EVENTLOG parameter group. You might want to decrease the number of days worth of records to be stored within the database.
7. Press F6 (Action) to action the parameters. This reinitializes thet event logging environment, and the event logger should restart with no problems.
8. Press F3 (File) to save your current parameter settings and exit, or F12 (Cancel) if you do not wish to save the changes you have made.
Reason:
The Event Logger tried to add a record to a full EVNTDB database and failed. The EVNTDB database reorganization process is initialized.
System Action:
Event logging is paused while the reorganization is in process.
User Action:
None
Reason:
During initialization of the Event Logger, an NDB error occured while executing an NDB command P1 . The line number in error is P2 .
System Action:
The Event Logger terminates.
User Action:
Check the activity log for further messages indicating why the NDB error occurred.
If the NDB is full, redefine it with more space. For information about the attributes of the distributed database, see the Installation and Setup Instructions.
Reason:
The Event logger initialization has completed. P1 may indicate (SUSPEND) which means that no records are being written to the EVNTDB due to errors during startup.
System Action:
Event Logger continues processing.If P1 indicates (SUSPEND) , then no records are being written to the EVNTDB.
User Action:
Check the initialization log to determine the cause of the failure if any.
Reason:
Event Logger has stopped due to P1 .
System Action:
Processing terminated.
User Action:
Review the activity log if the termination was due to an error.
Reason:
The Event Logger encountered an error when trying to gather information about the EVNTDB database. The return code is P1 . The Event Logger continues processing.
System Action:
NONE.
User Action:
Check the activity log for further messages indicating why the NDB error occurred. To display the log, enter the =H.L panel path.
Reason:
The Event Logger encountered an error when processing event data. The keyed field exceeded the maximum key length. The field data is truncated to the key length.
P1 is the field name.
P2 is the key length.
P3 is the field data.
System Action:
Message is logged and processing continues.
User Action:
Contact Technical Support and provide message details and the name of the File Transfer Product that you are monitoring.
Reason:
An NDB error has prevented records from being written to EVNTDB and has caused the logger to suspend logging.
System Action:
Logger remains active but no records are written to the EVNTDB.
User Action:
Check the initialization log to determine the cause of the failure.
Reason:
The EVNTDB has been recovered and the logger has resumed writing records to the NDB.
System Action:
Logging continues.
User Action:
None.
Reason:
An error was encountered when attempting to access a file. P1 is the operation being performed, P2 is the ID of the file, P3 is the return code, and P4 is the message set by the FILE verb.
System Action:
Event logging continues, however, File Transfer SCHEDULES logging may be interrupted.
User Action:
Contact your local support representative.
Reason:
File Transfer Schedule P1 has completed. Schedule details could not be logged as the required records could not be located in file P2 .
System Action:
Event logging continues, however, File Transfer SCHEDULES logging for schedule P1 is terminated.
User Action:
Contact your local support representative.
Reason:
While logging a file transfer event, a Source/Target Data filename's first P1 characters were truncated and the last 255 characters retained in the log record. The succeeding message RFLO8116 shows the complete filename.
System Action:
Event logging continues.
User Action:
Contact your local support representative.
Reason:
This message follows RFLO8115 message, which displays the complete Source/Target filename P2 .
System Action:
None.
User Action:
None.
Reason:
An Event Log process has started. The process extracts records from the EVNTDB event logging database and writes them in comma-delimited format to a sequential dataset. P1 indicates the type of process. If it is ARCHIVE, the records are deleted from the database.
System Action:
The indicated Event Log process starts to extract EVNTDB records.
User Action:
None
Reason:
An Event Log process has finished. The process extracts records from the EVNTDB event logging database and writes them in comma-delimited format to a sequential dataset. P1 indicates the type of process. If it is ARCHIVE, the records are deleted from the database.
System Action:
The indicated Event Log process finishes.
User Action:
None
Reason:
An error occurred during an EVNTDB P1 operation. The action being performed was P2 . The Dataset Services interface return code was P3 , and the feedback code was P4 . The dataset in use at the time of the error is shown in a following message.
System Action:
Processing terminated.
User Action:
Check the activity log for further messages to determine the cause of the error. See the Network Control Language Reference for the meaning of the Dataset Services interface feedback codes. The online Help for the N16Cxx messages (where xx is P4 ) provides possible user actions.
Reason:
An error occurred when a P1 command is being performed on the EVNTDB event logging database. The NDB return code is P2 .
System Action:
The process is placed in the displayed status, P3 .
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
The ARCHIVE or EXTRACT procedure is starting to write to the P1 dataset. The DD name of the dataset is P2 .
System Action:
The process continues.
User Action:
None
Reason:
The Event Log ARCHIVE process is commencing the DELETE step of its processing.
System Action:
The Event Log process continues running.
User Action:
None
Reason:
The call to the procedure failed because the keyword, P1 , has an invalid value, P2 .
System Action:
The request is rejected.
User Action:
Contact your local System Administrator.
Reason:
The Event Log process did not find any records that can be extracted or archived, as indicated by P1 .
System Action:
The Event Log process terminates.
User Action:
None
Reason:
The ARCHIVE or EXTRACT process has written P1 records to the P2 dataset. The DD name of the dataset is P3 .
System Action:
The process continues.
User Action:
None
Reason:
An error occurred when dataset P1 is being formatted as an NDB.
System Action:
Event logging and reporting is not made available.
User Action:
Determine why the NDB error occurred. Contact your System Administrator for further assistance.
Reason:
Your request to extract file transfer events starts the EVNTDB extract process as a background task that runs with your authority. Progress messages with the prefix RFLO82* are written to the activity log.
System Action:
The process is submitted to your background region.
User Action:
Check the activity log for progress. To access the log, enter the H.L path.
Reason:
The Event Log archive process has deleted P1 records from the EVNTDB database.
System Action:
The Event Log archive process continues running.
User Action:
None.
Reason:
Processing has finished.
P1 is the function that has been performed, either ARCHIVE or EXTRACT.
P2 is the name of the dataset.
P3 is the DD name of the dataset.
System Action:
None.
User Action:
None.
Reason:
The EVNTDB reorganization process could not continue as no sequential dataset has been defined for the reorganization.
System Action:
Reorganization processing terminates.
User Action:
Define a sequential dataset with a record length of 4096, a block size of 23445, and a record format of VB. Then add the dataset name to the EVNTSEQ Reorg Dataset field on the Event Logging Initialization Parameters panel.
To restart a failed REORG:
1. Go to the Event Logging Customizer panel (=/PARMS, Update $RF EVENTLOG).
2. Review the dataset allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB.
3. Set the Enable Event Logging field to NO .
4. Press PF6 to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a newly defined VSAM dataset. It is necessary for a new dataset name to be provided, and when appropriate increase the space allocation.
6. Set the Enable Event Logging field to YES .
7. Press PF6 to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the customizer log.
Reason:
The EVNTDB reorganization process has started.
System Action:
Reorganization processing continues.
User Action:
None.
Reason:
The EVNTDB reorganization process is beginning step 1, copying all records from the EVNTDB NDB to the sequential dataset indicated by P1.
System Action:
Reorganization processing continues.
User Action:
None.
Reason:
The EVNTDB reorganization process is beginning step 2, copying all records from the sequential dataset indicated by P1 , to the EVNTDB NDB.
System Action:
Reorganization processing continues.
User Action:
None.
Reason:
This is an IDCAMS message produced by the EVNTDB reorganization process.
System Action:
Reorganization processing continues.
User Action:
None.
Reason:
The EVNTDB reorganization process has successfully finished.
System Action:
Reorganization processing has finished. NetMaster for File Transfer event logging should resume normally if the reorganization was successful.
User Action:
None.
Reason:
The EVNTDB reorganization process has failed.
System Action:
Reorganization terminates.
User Action:
Check the activity log for message ID RFLO8219, which contains the SYSPRINT output from IDCAMS, to determine the cause of the failure.
To restart a failed REORG:
1. Go to the Event Logging Customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB. For information about the data set attributes, see the Installation and Setup Instructions.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events. For information about the data set attributes, see the Installation and Setup Instructions.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
EVNTDB is not available due to database maintenance. No further action is possible.
System Action:
Request is rejected.
User Action:
Retry later.
Reason:
An NDB START command for the EVNTDB completed without errors.
System Action:
None
User Action:
None
Reason:
An NDB START command for the EVNTDB failed with RC= P1 .
System Action:
Processing terminates and the EVNTDB logger is not restarted.
User Action:
To restart a failed REORG:
1. Go to Event Logging customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
The EVNTDB could not be processed because an NDB START command has not been issued or has failed.
System Action:
Processing terminates.
User Action:
Check the initialization log to determine the appropriate action.
To restart a failed REORG:
1. Go to Event Logging customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
An NDB STOP command for the EVNTDB failed with RC= P1 .
System Action:
Processing terminates, and the EVNTDB logger is not restarted.
User Action:
To restart a failed REORG:
1. Go to Event Logging customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
The EVNTDB reorganization initialization has started.
System Action:
None
User Action:
None
Reason:
An NDB PURGE command for the EVNTDB failed with RC= P1 .
System Action:
Processing terminates, and the EVNTDB logger is not restarted.
User Action:
To restart a failed REORG:
1. Go to Event Logging customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
Event Logging was not started due to errors during P1 processing.
System Action:
Error messages are written to the initialization log, and the process is terminated.
User Action:
Check the cause of the error from the log entries and determine the appropriate action.
To restart a failed REORG:
1. Go to Event Logging customizer panel (=/PARMS), and update $RF EVENTLOG.
2. Review the data set allocation for EVNTSEQ to determine if it has enough space to hold all records from EVNTDB. For information about the data set attributes, see the Installation and Setup Instructions.
3. Set the Enable Event Logging field to NO .
4. Press F6 (Action) to unload the data from EVNTDB to EVNTSEQ.
5. Set the EVNTDB Database Name field to a VSAM data set that has enough space to contain all the unloaded records and start logging new events. For information about the data set attributes, see the Installation and Setup Instructions.
6. Set the Enable Event Logging field to YES .
7. Press F6 (Action) to reload the data from EVNTSEQ to EVNTDB and restart event logging.
8. Review the initialization log.
Reason:
The EVNTDB REORG P1 step completed without errors.
System Action:
Reorganization processing continues.
User Action:
None
Reason:
The EVENT LOG archive/extract process has failed.
System Action:
Processing terminates.
User Action:
Check the EVNTDB Initialization Log for details of the failure and determine the appropriate action.
Reason:
The EVNTDB Logger failed to respond and indicate its current status.
System Action:
Processing continues.
User Action:
Check the log for possible initialization errors and take corrective action if necessary.
Reason:
During initialization it was determined that a reorganization had been performed in the last 24 hours. This indicates that the EVNTDB may not have enough space, and repeated reorganizations will have no effect.
System Action:
Reorganization aborted.
User Action:
Review the initialization log to determine the time of the last reorganization and determine the current usage of the EVNTDB using IDCAMS. If necessary allocate more space for the EVNTDB.
Reason:
Processing has failed.
P1 is the function that has been performed, either ARCHIVE or EXTRACT.
P2 is the name of the dataset.
P3 is the DD name of the dataset.
System Action:
Processing terminated.
User Action:
See message RFLO8203 or the succeeding N16Cxx messages for possible user actions.
Reason:
During EVNTDB START or automatic REORG, it was determined that the current dataset is no longer usable. An attempt was made to backup and rename the current EVNTDB but the new name is already in use. The backup dataset name would have the format:
&ZDNSQLCL.&ZJOBNAME.EVNTDB.annnv
where:
&ZDNSQLCL = value of the local dataset qualifier as set in the DSNQLCL JCL parameter &ZJOBNAME = jobname of the NetMaster region a = is an alphabetic character from A to J and is indexed by the last digit of the current year + 1 nnn = current Julian day v = version number from 0 to 9
System Action:
Processing terminates with the logger processing in SUSPEND mode.
User Action:
Specify a new EVNTDB dataset in the EVENTLOG parameter panel.
Reason:
The VSAM DATA and INDEX component names of the current EVNTDB could not be determined from an IDCAMS LISTCAT.
System Action:
Processing terminates with the logger processing in SUSPEND mode.
User Action:
Specify a new EVNTDB dataset in the EVENTLOG parameter panel.
Reason:
This is an IDCAMS message produced during renaming of the EVNTDB.
System Action:
Processing continues.
User Action:
None.
Reason:
During EVNTDB START or automatic REORG, it was determined that the current dataset is no longer usable. An attempt to define a new EVNTDB dataset failed.
System Action:
Processing terminates with the logger processing in SUSPEND mode with no records being logged.
User Action:
Review the initialization log to determine the cause of the failure or specify a new EVNTDB dataset form the EVENTLOG parameter display panel.
Reason:
The EVNTDB dataset has been RENAMED or RESTORED to P1 .
System Action:
Processing continues.
User Action:
None.
Reason:
The EVNTDB is being resized. The new size is determined by the product of the average record length and the total number of records rounded up the the next megabyte.
System Action:
Processing continues with records being cached during resizing.
User Action:
None.
Reason:
The EVNTARC archive data set cannot be created because the specified SMS Data Class P1 does not exist or does not contain the required attributes to create the data set.
System Action:
Processing of event records terminates.
User Action:
Consult the storage administrator to determine the SMS Data Class to use or specify override values for the data set attributes in the customizer panels (/PARMS) for the EVENTLOG parameter group. When using an SMS Data Class, the following values must be specified:
- AVGREC
- AVG VALUE
- SPACE PRIMARY
- SPACE SECONDARY
For more information about defining an SMS Data Class, see z/OS DFSMS: Using the Interactive Storage Management Facility.
Reason:
Initialization for event logging is incomplete because the supplied data set is not compatible with the current release of the product.
System Action:
Logging continues without an event log data set.
File transfer events are not logged.
User Action:
Ensure that you are using the Event Log data set defined by the region Setup JCL (member S01LCALC).
Reason:
An attempt was made to start the EVNDTB Monitor, but it is already running.
System Action:
Processing terminates.
User Action:
None
Reason:
An attempt to query the status of the EVNTDB failed bacause it is not allocated or the Event Logger was disabled.
System Action:
Processing terminates.
User Action:
Review the initialization log to determine why logging has been stopped.
Reason:
Automatic EVNTDB reorganization processing has failed.
System Action:
Process terminates and re-scheduled at the next monitoring cycle.
User Action:
Review the EVENTLOG Initialization log to determine the cause of the failure.
Reason:
The EVNTDB P1 component currently has a space of utilization of P2 .
System Action:
The EVNTDB Monitor continues processing.
User Action:
None
Reason:
The EVNTDB Monitor determined that no significant space was reclaimed after an Automatic REORG was performed. The DU( P1 ) and IU( P2 ) values display the Data and Index utilization respectively after completion of a REORG.
System Action:
Processing continues. In the next monitoring cycle, EVNTDB Monitor will not attempt to do an automatic REORG until the utilization falls below P3 percent
User Action:
Review space utilization. If necessary, reallocate the EVNTDB with more space or schedule an ARCHIVE to delete old records.
Reason:
The EVNTDB Monitor failed to initialize since it was not enabled.
System Action:
Processing terminates.
User Action:
ENABLE logging from the EVENTLOG Initialization Parameters. If the situation persists, call your local support.
Reason:
EVNTDB Automatic Reorg has determined that the last executiion did not alleviate the EVNTDB full condition. A new reorganization will not be scheduled.
System Action:
Processing terminates and logging remains inactive.
User Action:
Schedule an archive to delete old records or allocate more space to the EVNTDB.
Reason:
You selected an Event Logging and Reporting option, but the feature has not been configured.
System Action:
The selected option is not processed.
User Action:
Review the EVENTLOG parameter group. Ensure that logging is enabled. To list the parameter groups, enter the /PARMS shortcut.
Reason:
The event logging database (EVNTDB NDB) is in a status of P1 and is not available for reporting.
System Action:
The selected report is not processed.
User Action:
In the EVENTLOG parameter group, ensure that the value of Enable Event
Logging is YES and action the group to make the EVNTDB database available for reporting. To list the groups, enter the /PARMS shortcut.
If the database is still not available, check the activity log for further error messages. To display the log, enter the =H.L panel path.
Reason:
There were no File Transfer event records in the EVNTDB for the selected Schedule or File Filter Entry.
System Action:
None.
User Action:
None.
Reason:
EVNTDB is not available due to database maintenance. No further action is possible.
System Action:
Request is rejected.
User Action:
Retry later.
Reason:
An error occurred getting a record from the NDB while building the list. The NDB return code was P1 .
System Action:
Selection List terminates.
User Action:
To determine the appropriate action, check the following:
- EVENTLOG in the initialization log
- Return code
Reason:
A request to present an Events List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the variable table was P3 , and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present an Events List failed because an error was encountered accessing a variable table. The request was P1 , the identifier of the variable table was P3 , the feedback code was P2 , and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
An invalid value has been given for keyword P1 .
System Action:
The request is rejected and the procedure is terminated.
User Action:
Contact your system administrator.
Reason:
EVNTDB is not available due to database maintenance. No further action is possible.
System Action:
Request is rejected.
User Action:
Retry later.
Reason:
No records found for the selected entry.
System Action:
None
User Action:
None
Reason:
The Summary Reports Service Procedure received an error when trying to perform a P1 command on the EVNTDB database. The NDB response code is
P2 and the NDBERRI information is P3 .
System Action:
The report request is terminated.
User Action:
Contact your system administrator for assistance.
Reason:
The Summary Reports Service Procedure received an error when executing a call to the CAS Programming Interface ($CACALL). P1 is the purpose of the call, P2 is the name of the entity requested and P3 is the Feedback Code (Return Code). If P3 is 1 then entity P2 does not exist.
System Action:
The report request is terminated.
User Action:
Contact your system administrator for assistance.
Reason:
A request to present a Report List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the variable table was P3 , and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because an error was encountered accessing a variable table. The request was P1 , the identifier of the variable table was P3 , the feedback code was P2 , and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because there were no reports defined within the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection of a report from the Report List failed because the report was deleted by another user since the Report List was displayed. The name of the report selected was P1 .
System Action:
The selection of the report is rejected.
User Action:
None.
Reason:
An invalid value has been given for keyword P1 .
System Action:
The request is rejected and the procedure is terminated.
User Action:
Contact your system administrator.
Reason:
A heartbeat procedure for the file transfer resource listener port is initiated.
P1 is the SNMP host name.
P2 is the SNMP community name.
P3 is the port number which the listener should be on.
P4 is the number of retry attempts.
P5 is the interval, in seconds, between each retry.
System Action:
None.
User Action:
None.
Reason:
The file transfer resource listener port monitor is invoked without one of the necessary parameters. P1 identifies the missing parameter.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource, and specify the missing parameter.
Reason:
The file transfer resource listener port monitor has found the active listener port.
P1 identifies the owning file transfer resource.
P2 displays the name of the monitor resource.
P3 is the listener port
P4 is the time.
System Action:
None.
User Action:
None.
Reason:
The file transfer application requires an active listener port to receive requests for connection. The required listener port was not found or was not in a LISTEN state.
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the time.
System Action:
None.
User Action:
Perform one or more of the following to investigate the problem:
- Check the transient log of the monitor resource for additional details.
- If the port number of the file transfer application is specified on the Monitor Details panel of the resource definition, check its accuracy.
- Check the current state of the file transfer application, P1 .
- Check the current state of the TCP/IP region.
Reason:
The TCP/IP interface is currently P1 s. To verify the current status of the listener port, the status of the TCP/IP interface must be ACTIVE.
System Action:
Heartbeat processing does not take place.
User Action:
Display the current TCP/IP services status by issuing a SHOW TCPIP command. Message N3AF05 shows the current TCP/IP INTERFACE status.
If the TCP/IP INTERFACE status is INACTIVE - Issue a TCPIP START command. Wait for message N3B201 and then enter a CHK command against this resource.
If the TCP/IP INTERFACE status is QUIESCING or STOPPING - wait for the STATUS to change to INACTIVE and proceed as above.
If the TCP/IP INTERFACE status is STARTING - Wait for message N3B201 and then enter a CHK command against this resource.
Reason:
This is an informational message issued by the TCP/IP Listener monitor for each connection found until the Listener is found.
P1 identifies the local port.
P2 is the connection status.
P3 is the connection id.
System Action:
None
User Action:
None
Reason:
The action described in P1 could not be performed on the TCP/IP socket. The Feedback Code P2 , Error Number P3 and/or Vendor Error P4 are displayed for further diagnosis.
System Action:
The procedure terminates with a return code of 12.
User Action:
See the NCL Reference for suggested actions that pertain to feedback code ZFDBK.
Reason:
The encoding of data from EBCDIC to ASCII failed. Refer to the additional details found in P1 for further information.
System Action:
The procedure terminates with a return code of 12.
User Action:
Take actions as indicated by the additional details.
Reason:
The SOCKET action that failed is described in P1 . P2 through P6 contain the return, error, and feedback codes that can assist with problem diagnosis. A RECEIVE which times out (RC=4) could indicate that the user is not authorized to access SNMP, that SNMP is not active, or possibly the Community name is invalid.
System Action:
The procedure terminates with a return code of 12.
User Action:
See the NCL Reference for suggested user actions that pertain to feedback code ZFDBK.
Reason:
This message is the response to a D command against a file transfer listerner port monitor resource.
P1 identifies the owning file transfer resource.
P2 is the name of the file transfer listener port monitor resource.
P3 is the TCP/IP port number P1 uses for TCP/IP access.
P4 is the state of P3 . This is the tcpConnState value as described by the SNMP Working Group's RFC 1213.
System Action:
None.
User Action:
None.
Reason:
The response received form the listener contained an unexpected error status P1 . The error index was P2 .
System Action:
The procedure terminates with a return code of 12.
User Action:
Analyze the error status and error index codes to determine what corrective actions to perform.
Reason:
The TCP/IP connections monitor was unable to ascertain the TCP/IP port number used by file transfer resource manager, P1 .
System Action:
Monitoring fails.
User Action:
This only applies when TCPaccess Version 4.1 is being used.
For a CONNECT:Direct resource, the port number is either obtained automatically from CONNECT:Direct or provided in user exit $RFXPRMS. One possible problem is that an old version of $RFXPRMS is executed.
For an FTP resource, the port number must be specified in the resource definition.
Reason:
The response received from SNMP did not contain any data. However, no error status was returned.
System Action:
The procedure terminates with a return code of 12.
User Action:
This error condition indicates a problem with the SNMP services on the resource being monitored. Report the problem to your resource administrator.
Reason:
A heartbeat procedure for the file transfer resource listener port is initiated.
P1 is the name of the manager for the file transfer product
P2 is the TCP/IP software type
P3 is the TCP/IP software version (if available)
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure for the file transfer resource listener port has established that the P1 file transfer product is currently listening for connections on port P2 .
System Action:
None.
User Action:
None.
Reason:
The message displays a TCP/IP listener port monitor trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A display command was received for a listener monitor, but the requestor is not in 3270 full-screen mode.
System Action:
The display command is rejected.
User Action:
Enter the display command from a 3270 session.
Reason:
The data space is active. The FTP policy mode is P1 , and the name of the loaded ruleset is P2 .
System Action:
FTP policy rules are enforced.
User Action:
None.
Reason:
The data space is active, but no FTP policy ruleset is loaded. No FTP policies are in force.
System Action:
None.
User Action:
If you want to enforce FTP policies, select L on the FTP Policy Maintenance menu to load an FTP policy ruleset in the data space.
Reason:
The data space is not active, and FTP policy rules cannot be enforced.
System Action:
FTP policy rules are not enforced.
User Action:
To enforce any loaded policy rules, start the data space manager task (for example, S SOLVEDSP).
You can also monitor and control the data space manager from the status monitor by defining an STC class resource for the manager.
Reason:
The data space is in error, and FTP policy rules cannot be enforced.
System Action:
FTP policy rules are not enforced.
User Action:
It is likely that a wrong version of the Data Space Manager is active. To find out the version of the Data Space Manager, issue the following command from a Command Entry panel:
SYSCMD F manager-task,DISPLAY
The returned N6DQ41 message contains the version of the data space. Ensure that the version is at least 0410.
If you are using an old manager, replace it with the new version.
If you are using the correct manager, note the feedback code and contact Technical Support.
Reason:
The request cannot be processed when the data space is inactive.
System Action:
None.
User Action:
To perform this action, start the data space manager task first (for example, S SOLVEDSP).
Reason:
An error occurred when communicating with the Data Space Manager. The most likely cause is that you are using an old version of the manager.
P1 is the feedback code that identifies the error.
System Action:
The request is not processed.
User Action:
To find out the version of the Data Space Manager, issue the following command from a Command Entry panel:
SYSCMD F manager-task,DISPLAY
The returned N6DQ41 message contains the version of the data space. Ensure that the version is at least 0410.
If you are using an old manager, replace it with the new version.
If yoy are using the correct manager, note the feedback code and contact Technical Support.
Reason:
Sysname and Version specified is unknown to the system.
System Action:
The request is rejected.
User Action:
Use '?' to list a selection list of Sysname and Version known to system.
Reason:
The Event Logging Database, EVNTDB, is not in an ACTIVE state. Any reporting or extract functions that use the database are not available.
System Action:
The request is rejected.
User Action:
You can start the EVNTDB database by initializing event logging and reporting as follows:
1. Access the list of region parameter groups.
2. Enter U beside the EVENTLOG parameter group.
3. Press F6 (Action).
Reason:
The specified dataset is not valid. Either it does not exist, or it is not sequential with a variable blocked record format (RECFM=VB) and a logical record length of at least 502 (LRECL=502).
System Action:
The request is rejected.
User Action:
Specify a valid extract dataset, and retry.
Reason:
You selected the EX option, but no extract dataset name was provided either by the you or by the EVNTARC Archive Dataset field in the EVENTLOG parameter group.
System Action:
The request to extract file transfer events is not processed.
User Action:
Specify an extract dataset name in the field provided.
Reason:
The extract dataset entry contained a GDG relative number (for example, A.B(+1)). However, the dataset name was not a GDG base name.
System Action:
The request is rejected.
User Action:
Correct the GDG base name and retry.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact Technical Support.
Reason:
The SSI is active. The FTP policy mode is P1 , and the name of the loaded ruleset is P2 .
System Action:
FTP policy rules are enforced.
User Action:
None.
Reason:
The SSI is active, but no FTP policy ruleset is loaded. No FTP policies are in force.
System Action:
None.
User Action:
If you want to enforce FTP policies, select L on the FTP Policy Maintenance menu to load an FTP policy ruleset in the SSI.
Reason:
The SSI is not active, and FTP policy rules cannot be enforced.
System Action:
FTP policy rules are not enforced.
User Action:
To enforce any loaded policy rules, start the SOLVESSI task (for example, S SOLVESSI).
Reason:
The SSI is in error, and FTP policy rules cannot be enforced.
System Action:
FTP policy rules are not enforced.
User Action:
It is likely that a wrong version of the SSI is active.
If you are using an old SSI, replace it with the new version.
If you are using the correct SSI, contact Technical Support.
Reason:
The request cannot be processed when the SSI is inactive.
System Action:
None.
User Action:
To perform this action, start the data space manager task first (for example, S SOLVESSI).
Reason:
An error occurred when communicating with the SSI. The most likely cause is that you are using an old version of the manager.
P1 is the feedback code that identifies the error.
System Action:
The request is not processed.
User Action:
If you are using an old SSI, replace it with the new version.
If you are using the correct SSI, contact Technical Support.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact your local Support Center.
Reason:
Template definitions are special and cannot be accessed from this panel.
System Action:
The request is rejected.
User Action:
Access template definitions from the Template Definition Menu. To access that menu, enter the /RADMIN.T path.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, is active. P1 shows the module name and version number. P2 identifies the EPS ID from which CONNECT:Mailbox events can be received.
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, has requested the services of the event delivery facility, but the request was rejected because of one of the following:
- The required SSI is not active.
- The SSI is active but is running without the event delivery facility.
System Action:
Log records will be forwarded to the NetMaster for File Transfer region as soon as the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, has requested the services of the event delivery facility, but the request was rejected because the SSI region is not currently active.
System Action:
Log records will be forwarded to the NetMaster for File Transfer region as soon as the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES).
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, requested the services of the event delivery facility, but the request was rejected because the SSI is shutting down.
System Action:
The log record is not forwarded to this region. This file transfer event is lost.
User Action:
Ensure that the SSI region is restarted.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, issued a $NMXEVNT request to forward a CONNECT:Mailbox event to the event receiver. The request was rejected, the values of the R0 and R15 return codes from the $NMXEVNT request are P1 and P2 respectively.
System Action:
The event record is not forwarded to this region.
User Action:
Note the value of R0 and R15, and contact Technical Support.
Reason:
This message is the first of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX. The complete set of messages is:
RFMX06 ABEND AT +nnnn IN xxxxxxxx xxxx LEVEL xxxxxx
RFMX07 RECEIVED R1=xxxxxxxx RECORD ADDR=xxxxxxxx RECORD TYPE=xx RFMX08 PSW=xxxxxxxx xxxxxxxx INT=xxxxxxxx
RFMX09 R0-R3 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFMX09 R4- R7 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFMX09 R8-R11 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFMX09 R12-R15 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Message RFMX06 identifies the abend offset, module, version, and level.
Message RFMX07 identifies the parameters passed by CONNECT:Mailbox:
RECEIVED R1 is the value in R1 when the exit was called.
RECORD ADDR is the value of the first full word addressed by R1. If R1 was invalid, this is shown as UNKNOWN.
RECORD TYPE is the CONNECT:Mailbox log record type. If either R1 or the record address was invalid, this is shown as ??.
Message RFMX08 identifies the failing PSW and program interruption information.
Messages RFMX09 identify the general purpose registers at the time of the abend.
System Action:
The log record is ignored, and processing continues.
User Action:
Contact Technical Support. Ensure that you have the following information available:
- The entire group of messages (RFMX06 to RFMX09)
- The version and maintenance level of CONNECT:Mailbox
Reason:
This message is one of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX.
For more information, see the help for message RFMX06.
System Action:
See RFMX06.
User Action:
See RFMX06.
Reason:
This message is one of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX.
For more information, see the help for message RFMX06.
System Action:
See RFMX06.
User Action:
See RFMX06.
Reason:
This message is the last of a group of messages that are issued when an abend occurs in the NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX.
For more information, see the help for message RFMX06.
System Action:
See RFMX06.
User Action:
See RFMX06.
Reason:
The forwarding of CONNECT:Mailbox log events has resumed. This message indicates a recovery from a previous error condition (for example, the required SSI region was successfully restarted).
System Action:
CONNECT:Mailbox log events are now sent to the event receiver.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, requested the services of the event delivery facility. The request was rejected because the event delivery facility could not obtain storage (R0=7 and R15=28 returned from $NMXEVNT).
System Action:
The CONNECT:Mailbox log event is not sent to the event receiver.
User Action:
Contact Technical Support.
Reason:
This is a diagnostic trace message.
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, was called by CONNECT:Mailbox. The log record is identified as follows:
P1 is the log record EXIT type - usually 6.
P2 is the log record type (Key code) - usually A, B, or D.
P3 is NMCMLGEX action:
SES indicates that log record will be forwarded to this region IGN indicates that log record is ignored
P4 is the log record data (the first 55 characters only)
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer CONNECT:Mailbox log exit, NMCMLGEX, was called by CONNECT:Mailbox. The log record is not recognized as a valid CONNECT:Mailbox log exit record.
P1 is the log record EXIT type (the expected type is 6).
P2 is the log record type (Key code) (the expected values is A, B, or C).
System Action:
The event record is not forwarded to this region.
User Action:
Contact Technical Support. Ensure that you have available details of the version and maintenance level of CONNECT:Mailbox.
Reason:
The CONNECT:Mailbox log exit for NetMaster for File Transfer, NMCMLGEX, tried to load a load module, but the loading operation failed. The load module name is P1 and the values of the R0 and R15 return codes from the LOAD or BLDL instruction are P2 and P3 respectively.
System Action:
The load module is not loaded and is excluded from further processing, the result of which depends on which module has failed to load:
Module NMCMLGEX No events will be forwarded to the region.
Other Modules Other modules relate to your own exits. The result of not executing these modules depends on your implementation.
User Action:
Use the R0 and R15 return codes to determine the cause of the error.
A common error is R15=4 (accompanying an 806 system completion code), which indicates that the module could not be found in the load library list (that is, the list of libraries that are specified in the CONNECT:Mailbox STEPLIB).
Ensure that the Management Services LPALOAD load library is either included in the CONNECT:Mailbox STEPLIB or included in the system link list.
Notes: - All libraries included in the STEPLIB must be APF authorized. - The CONNECT:Mailbox region must be recycled to restart the log exit.
Reason:
The CONNECT:Mailbox log exit for NetMaster for File Transfer, NMCMLGEX, was unable to obtain or free working storage. P1 is the failing request and P2 is the value of the R15 code.
System Action:
The request cannot be processed.
User Action:
Use the R15 code to determine the cause of the error.
Reason:
No process(es) were found matching the search criteria requested.
System Action:
None.
User Action:
None.
Reason:
The process definition identified by P1 was changed successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was deleted successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was flushed successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was held successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was released successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The heartbeat procedure for a queue commences processing. The message identifies the queue type, P1 , the status to be checked, P2 , and the depth threshold, P3 .
System Action:
None
User Action:
None
Reason:
A queue monitor heartbeat procedure is invoked without one of the necessary parameters. P1 identifies the missing parameter.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource, and specify the missing parameter.
Reason:
A heartbeat procedure for a CONNECT:Direct monitor resource issued a command to solicit information from the CONNECT:Direct region and received either no response or a response which was not expected. The response received is in the resource transient log.
P1 identifies the owning CONNECT:Direct region.
P2 is the name of the monitor resource.
System Action:
None
User Action:
Check the transient log for the resource for the response, if any, that was received. The response may indicate a degradation within CONNECT:Direct that is causing it not to respond, in which case remedial action might be necessary.
Reason:
A CONNECT:Direct queue monitor has checked for processes in the queue that have the displayed status (if status is applicable).
This message displays the number of such processes found when the number does not exceed the defined threshold.
P1 identifies the owning CONNECT:Direct region.
P2 is the name of the monitor resource.
P3 identifies the type of queue.
P4 identifies the process status. (Not available for C:D for OS/400)
P5 is the number of CONNECT:Direct processes in the P3 queue that are in the P4 state (if applicable).
P6 shows the time when the information was obtained.
System Action:
None
User Action:
None
Reason:
A CONNECT:Direct queue monitor has checked for processes in the queue that have the displayed status (if status is applicable).
This message displays the number of such processes found when the number exceeds the defined threshold.
P1 identifies the owning CONNECT:Direct region.
P2 is the name of the monitor resource.
P3 identifies the type of queue.
P4 identifies the process status. (Not available for C:D for OS/400)
P5 is the number of CONNECT:Direct processes in the P3 queue that are in the P4 state (if applicable).
P6 shows the time when the information was obtained.
System Action:
None
User Action:
None
Reason:
QUEUE TYPE P1 is not supported by CONNECT:Direct for P1 .
System Action:
Request is rejected.
User Action:
Delete the CDMON resource as it serves no purpose.
Reason:
The heartbeat procedure for a CONNECT:Direct remote node monitor has commenced processing. The message identifies the remote node whose availability is to be checked ( P1 ).
System Action:
None
User Action:
None
Reason:
The heartbeat procedure for a remote node monitor has been invoked without the required remote node name.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the resource monitor definition, complete the Remote Node Name field.
Reason:
The remote node monitor has determined that the monitored remote node is available:
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the name of the remote node.
P4 is the time.
System Action:
None
User Action:
None
Reason:
The remote node monitor has determined that the monitored remote node is unavailable:
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the name of the remote node.
P4 is the time.
System Action:
None
User Action:
None
Reason:
The monitored remote node is unknown to the remote node monitor because of one of the following reasons:
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the name of the remote node.
P4 is the cause of the error.
P5 is the time.
System Action:
None
User Action:
For a CONNECT:Direct remote node, check the CONNECT:Direct network map.
For an FTP remote server node, check the Domain Name System (DNS) definition.
Reason:
A request to check the availability of the monitored remote node has timed out:
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
P3 is the name of the remote node.
System Action:
None
User Action:
None
Reason:
The TCP/IP interface is currently P1. The monitoring of this resource requires the status of the TCP/IP interface to be ACTIVE.
System Action:
Heartbeat processing does not take place.
User Action:
Display the current TCP/IP services status by issuing a SHOW TCPIP command. Message N3AF05 shows the current TCP/IP INTERFACE status.
If the TCP/IP INTERFACE status is INACTIVE - Issue a TCPIP START command. Wait for message N3B201 and then enter a CHK command against this resource.
If the TCP/IP INTERFACE status is QUIESCING or STOPPING - wait for the STATUS to change to INACTIVE and proceed as above.
If the TCP/IP INTERFACE status is STARTING - Wait for message N3B201 and then enter a CHK command against this resource.
Reason:
The monitoring of the remote FTP server P1 has failed due to a socket error, P3 . The feedback code is P2 .
System Action:
Heartbeat processing does not take place.
User Action:
See the NCL Reference for an explanation of the feedback and error codes and suggested user action.
Reason:
The heartbeat procedure for a remote node monitor has been invoked without the required remote node TCP/IP host name or address.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the monitor definition, complete the TCP/IP Host Name/Addr field.
Reason:
The heartbeat procedure for a remote node monitor has been invoked without the required remote node port number.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the monitor definition, complete the TCP/IP Port Number field.
Reason:
P1 is a text line returned as the result of an FTPMON remote node D (display) command. It describes the operation and remote node details. This message is usually followed by one or more RFREMNDxx message(s) that indicate the outcome of the command.
System Action:
None
User Action:
None
Reason:
You have issued a command against a resource from a remote system. The command is only valid against local resources.
System Action:
The command is rejected.
User Action:
Log on to the resource's local system and issue the command from there.
Reason:
You have issued a command against a resource of class P1. The command is not valid for this resource class.
System Action:
The command is rejected.
User Action:
None.
Reason:
The remote FTP Server address P3 specifies an IPv6 address. The monitoring of the remote FTP server failed because the current sockets API supports IPv4 addresses only.
P1 identifies the owning file transfer resource.
P2 is the name of the monitor resource.
System Action:
Heartbeat processing does not occur.
User Action:
Check the SOCKETS parameter group (/PARMS) and ensure that the TCP/IP Software Type specifies IBMV6.
Reason:
The message displays a file transfer schedule trace record.
P1 is the trace ID, P2 is the procedure ID and P3 is the trace text.
System Action:
None
User Action:
Contact your local support representative.
Reason:
A File Transfer Schedule has begun its pre-processing period.
System Action:
Monitoring for required file transfers begins. The actual state of the File Transfer Schedule resource is set to INACTIVE.
User Action:
None.
Reason:
A File Transfer Schedule's pre-processing period has terminated and the processing period begun.
System Action:
Monitoring for required file transfers continues. The actual state of the File Transfer Schedule resource is set to STARTING.
User Action:
None.
Reason:
A File Transfer Schedule has reached the point where the processing time left is equal to the Longest Transfer Duration.
System Action:
If not all required transfers have begun by this point the Schedule resource's actual state is set to DEGRADED.
User Action:
None.
Reason:
A File Transfer Schedule's processing period has ended and the post-processing period begun.
System Action:
If not all required transfers have ended by this point the Schedule resource's actual state is set to FAILED otherwise it will be set to ACTIVE.
User Action:
None.
Reason:
A File Transfer Schedule's post-processing period has ended.
System Action:
If not all required transfers have ended by this point the Schedule resource's actual state is set to FAILED otherwise it will be set to INACTIVE.
User Action:
None.
Reason:
This is the message issued by the display command to cause the transient log records for an active monitoring period to be displayed.
System Action:
Display active schedule's transient log records.
User Action:
None.
Reason:
A display command was issued against a File Transfer Schedule resource which is not currently monitoring for file transfers.
System Action:
The display command is rejected.
User Action:
None.
Reason:
An activate command was issued against a File Transfer Schedule resource which was not scheduled to monitor file transfers.
System Action:
The activate command is rejected.
User Action:
None.
Reason:
The file transfer schedule specifies a period (Longest Transfer) within which the monitored transfer is expected to complete. The schedule is now within that period from the end of processing, but all required files have not yet been detected. The indication is that the transfer might not complete in time.
System Action:
The actual state of the File Transfer Schedule resource is set to DEGRADED.
User Action:
None
Reason:
The file FTSCHD, which stores Schedule Details so that they are still available after a system outage, is full.
System Action:
Processing continues, however schedule related events will not be stored in the FTSCHD file.
User Action:
Either clear out the records in the file using the ICS Parameter Group FTSCHD (A.C.P), or unallocate the file FTSCHD, and then allocate the FTSCHD file with more space.
Reason:
There was an error reading the FTSCHD file. P1 is the file return code and P2 is the VSAM reason code. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
Processing continues, however schedule related events may not be recovered from the FTSCHD file.
User Action:
Contact your system administrator.
Reason:
There was an error deleting a record from the FTSCHD file. P1 is the file return code and P2 is the VSAM reason code. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
Processing continues, however schedule related events may not be deleted from the FTSCHD file.
User Action:
Contact your system administrator.
Reason:
There was an error writing to the FTSCHD file. P1 is the file return code and P2 is the VSAM reason code. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
Processing continues, however schedule related events may not be written to the FTSCHD file.
User Action:
Contact your system administrator.
Reason:
The schedule related events saved on the FTSCHD file have not been restored as the filters have been changed since the schedule was started.
System Action:
Processing continues, however schedule related events have not been recovered.
User Action:
No action required.
Reason:
There was an error reading the FTSCHD file. P1 is the file return code and P2 is the Sysmsg returned. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
Processing continues, however schedule related events may not be recovered from the FTSCHD file.
User Action:
Contact your system administrator.
Reason:
There was an error deleting a record from the FTSCHD file. P1 is the associated error message. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
Processing continues, however, schedule related events may not be deleted from the FTSCHD file.
User Action:
Contact your System Administrator.
Reason:
A System Image P1 is being loaded but the FTSCHD file contains records that are not related to this System Image. The file FTSCHD stores schedule events so that they are still available after a system outage.
System Action:
All records are deleted from the FTSCHD file.
User Action:
None.
Reason:
Object ID not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
There is no active schedule (in PROC OR POST stage) found for the related FTSCHD resource.
System Action:
The request is rejected.
User Action:
Wait until the Schedule is in PROC or POST stage before extending.
Reason:
The dialogue with $RFSCHED has been timed-out.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Unknown Reply from process $RFSCHED.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Another procedure is running. You cannot extend the monitoring period at this time.
System Action:
The request is rejected.
User Action:
Try later after other procedure finishes.
Reason:
A browsing of schedule time is completed.
System Action:
The request is completed.
User Action:
At this time you can only browse the schedule. The line command can be rerun later.
Reason:
This is a warning message.
System Action:
The request needs confirmation before proceeding.
User Action:
Press PF6 to confirm or PF12 to cancel without any change.
Reason:
This schedule is not eligible to be extended.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The request to extend the timers for schedule monitoring has completed successfully.
System Action:
The request is completed.
User Action:
No action is required.
Reason:
An attempt to extend the timers of an active schedule failed due to another procedure holding the system lock.
System Action:
The request is rejected.
User Action:
Try later after other procedure finishes.
Reason:
The request to extend timers for schedule monitoring has completed successfully.
System Action:
The request is completed.
User Action:
No action is required.
Reason:
The attempt to extend the schedule monitoring period was not acceptable.
System Action:
The request is rejected.
User Action:
Try again using another monitoring period.
Reason:
There is a time overlap problem in the schedule extension.
System Action:
The request is rejected.
User Action:
Try the extension with another time.
Reason:
The time for end processing has elapsed.
System Action:
The request is rejected.
User Action:
Try the extension with another time.
Reason:
An attempt to access the Schedule Checkpoint dataset failed. The above
Retcode and VSAM error code were generated.
System Action:
The request is rejected.
User Action:
Interpret the error code using the appropriate IDCAMS manual.
Reason:
An attempt to access the System Table failed. The above Feedback Code was generated.
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
The execution of procedure $RMDBMS failed. The above Retcode was generated.
System Action:
The request is rejected.
User Action:
Interpret the error code using the appropriate IDCAMS manual.
Reason:
All File Transfers Started Exit have been triggered for this resource.
System Action:
The system has started the user defined procedure for this exit.
User Action:
None.
Reason:
File Transfer Failed Exit has been triggered for this resource.
System Action:
The system has started the user defined procedure for this exit.
User Action:
None.
Reason:
All File Transfer Completed Exits have been triggered for this resource.
System Action:
The system has started the user defined procedure for this exit.
User Action:
None.
Reason:
The schedule has been completed by the exit for this resource.
System Action:
The schedule has completed by Exit for this resource. The monitoring is stopped.
User Action:
None.
Reason:
Schedule was forced off for this resource.
System Action:
The schedule was forced off for this resource. The monitoring is stopped.
User Action:
None.
Reason:
Schedule deleted for this resource.
System Action:
All schedule(s) have been deleted for this resource. The monitoring is stopped.
User Action:
None.
Reason:
Schedule's P1 transfer counts have been reset.
System Action:
The schedule's transfer counts have been reset. The counting of transfer is resumed.
User Action:
None.
Reason:
Only active schedule can be forced off.
System Action:
The request is rejected.
User Action:
None.
Reason:
The file transfer schedule filter definition control file P1 cannot be evaluated. The error is described by P2.
System Action:
The file transfer schedule terminates.
User Action:
Correct the filter entry in the filter definition control file.
Reason:
The Managed FTP SSI policy monitor has established that the SSI is active and ready for Managed FTP actions and events.
System Action:
Monitoring of the SSI policy monitor continues.
User Action:
None.
Reason:
The Managed FTP SSI policy monitor established that the SSI is either inactive, or is not ready for Managed FTP actions and events. The status of the Managed FTP SSI policy monitor will be rechecked within
P1 seconds.
System Action:
The status of the Managed FTP SSI policy monitor is monitored.
User Action:
This message is preceeded by RMEV25** messages. Refer to the explanation for those messages.
Reason:
A request to start a copy of the $RFSDMON procedure was ignored because another copy is currently running. This message may be issued if the FTPCNTL Customizer parameter group is actioned more than once.
System Action:
The request to start a new instance of the procedure is ignored.
User Action:
None.
Reason:
The message displays a Managed FTP SSI policy monitor trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
None.
Reason:
You have specified invalid dates.
System Action:
Validation of the search criteria fails.
User Action:
Correct the dates in the indicated fields.
Reason:
You have specified an invalid date-time combination.
System Action:
Validation of the search criteria fails.
User Action:
Correct the date and time in the indicated fields.
Reason:
The VFS operation, P1 , failed with file return code P2 and VSAM feedback code P3 for the VFS key, P4 .
System Action:
None.
User Action:
Contact your system administrator.
Reason:
An attempt to open the VFS database failed as the user does not have the authority to access the database.
System Action:
None.
User Action:
Contact your Security Administrator for assistance.
Reason:
An attempt to update the VFS database failed as the user does not have the update authority.
System Action:
None.
User Action:
Contact your Security Administrator for assistance.
Reason:
The P1 field has an invalid value. The OVER Byte field must be LESS than the UNDER Byte. And the UNDER Byte field must be GREATER than zero.
System Action:
Validation terminates.
User Action:
Correct the Over or Under Byte value and retry.
Reason:
Selection of fields from the list was cancelled.
System Action:
None
User Action:
None
Reason:
No fields were selected from the Fields Selection List. The target file cannot be created.
System Action:
The request is terminated.
User Action:
Redo your request and select one or more fields.
Reason:
An error occurred during a GET function on the vartable P1 for key P2 . The received error code is P3.
System Action:
The request is terminated and the procedure is ended.
User Action:
Contact your system administrator.
Reason:
A user cancelled the request to extract file transfer events from the EVNTDB database.
System Action:
The request to extract file transfer events is not processed.
User Action:
None.
Reason:
Your request to extract file transfer events starts the EVNTDB extract process as a background task that runs with your authority. Progress messages with the prefix RFLO82* are written to the activity log.
System Action:
The process is submitted to your background region.
User Action:
Check the activity log for progress. To access the log, enter the H.L path.
Reason:
The NDB Search did not find any record(s) that match(es) the Extract Criteria.
System Action:
None.
User Action:
Change your criteria and retry.
Reason:
A syntax error was detected during execution of an NDB SCAN statement.
System Action:
None.
User Action:
Review the scan and sort expression and retry the command.
Reason:
The P1 fields require valid value.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
You have specified invalid dates.
System Action:
Validation of the search criteria fails.
User Action:
Correct the dates in the indicated fields.
Reason:
You have specified an invalid date-time combination.
System Action:
Validation of the search criteria fails.
User Action:
Correct the date and time in the indicated fields.
Reason:
No records are defined in the database for the requested schedule name.
System Action:
None.
User Action:
Display the list of valid schedule names by placing a question mark (?) in this field.
Reason:
The VFS operation, P1 , failed with file return code P2 and VSAM feedback code P3 for the VFS key, P4 .
System Action:
None.
User Action:
Contact your system administrator.
Reason:
An attempt to open the VFS database failed because the user does not have authority to access the database.
System Action:
None.
User Action:
Contact your security administrator for assistance.
Reason:
An attempt to update the VFS database failed because the user does not have update authority.
System Action:
None.
User Action:
Contact your security administrator for assistance.
Reason:
The fields SYSTEM NAME and VERSION are required if a SCHEDULE NAME is provided.
System Action:
The field in error is highlighted.
User Action:
Enter a value.
Reason:
You did not select a value for the highlighted field.
System Action:
None
User Action:
None
Reason:
The P1 fields require valid value.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
Monitoring of SNA sessions is not available on CONNECT:Direct for P1 .
System Action:
Request is rejected.
User Action:
Delete the CDMON resource as it serves no purpose.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No records exist.
System Action:
None
User Action:
None
Reason:
The search mode has already been activated.
System Action:
None.
User Action:
None.
Reason:
An invalid slection was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
A request to present an Schedule List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the variable table was P3 , and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
This is an informational message indicating that a print request has successfully been sent to the requested printer.
System Action:
None
User Action:
None
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Request action on the database failed with non zero return code.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
An attempt was made to select the element described by P1 which had previously been selected.
System Action:
Request rejected.
User Action:
None.
Reason:
A VARTABLE GET failed during System Image Selection.
System Action:
System image selection terminates.
User Action:
Determine the reason for the VARTABLE error.
Reason:
An attempt was made to unselect the element described by P1 which had not previously been selected.
System Action:
Request rejected.
User Action:
None.
Reason:
A VARTABLE ADD failed during System Image Selection.
System Action:
System image selection terminates.
User Action:
Determine the reason for the VARTABLE error.
Reason:
Request action on the database failed with non zero return code.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
No system images with names or versions that start with P2 were found.
P1 is either SYSNAME or VERSION.
System Action:
None.
User Action:
If required, create the system image. You can use any of the following methods to create a system image:
- Use the AutoAssist Express Setup Facility (/RADMIN.AD.E).
- Use the System Images option on the Resource Administration menu (/RADMIN).
- Use the AutoAssist Auto Populate Facility (/RADMIN).
Reason:
No system images of the type P1 were found.
System Action:
None.
User Action:
If required, create the system image. You can use any of the following methods to create a system image:
- Use the AutoAssist Express Setup Facility (/RADMIN.AD.E).
- Use the System Images option on the Resource Administration menu (/RADMIN).
- Use the AutoAssist Auto Populate Facility (/RADMIN).
Reason:
An unknown command was passed to the criteria procedure.
System Action:
The request is rejected.
User Action:
Correct the command to the criteria procedure and rerun.
Reason:
No system image has been selected for schedule forecasting.
System Action:
The request has been abandoned.
User Action:
Select at least one system image and rerun.
Reason:
You pressed the ACTION key before entering values for all required fields: FROMDATE/TODATE/FROMTIME/TOTIME and System Image .
System Action:
The request has been abandoned.
User Action:
Enter values in the FROMDATE/TODATE/FROMTIME/TOTIME/System Image fields and press the ACTION key again.
Reason:
You have specified an invalid date-time combination.
System Action:
Validation of the search criteria fails.
User Action:
Correct the date and time in the indicated fields.
Reason:
You have specified an invalid date-time combination.
System Action:
Validation of the search criteria fails.
User Action:
Correct the date and time in the indicated fields.
Reason:
The P1 fields require valid value.
System Action:
The validation fails.
User Action:
Specify value in the P1 fields.
Reason:
A matched schedule was not found.
System Action:
The search is completed without a matched schedule.
User Action:
Try again with different criteria.
Reason:
The P2 field should be less than p1 field.
System Action:
The validation fails.
User Action:
Specify new values in the P1 and P2 fields.
Reason:
There is no SNA session activity on the Remote Names defined in the monitor definition.
System Action:
None.
User Action:
None.
Reason:
The transfer has stopped updating its record count and is in a stalled status.
System Action:
None.
User Action:
Investigate the reason for the stalled SNA session.
Reason:
The Stalled SNA Session Monitor has issued a heartbeat at the time indicated by P1 to the CONNECT:Mailbox STC and has not received a response.
System Action:
None.
User Action:
None.
Reason:
The Stalled SNA Session Monitor has found no SNA sessions in a stalled status. P1 is the time the monitor performed the heartbeat.
System Action:
None.
User Action:
None.
Reason:
The Stalled SNA Session Monitor has found that there are P1 sessions in a stalled state. This means that the record count has stopped updating. P2 is the time the monitor performed the heartbeat.
System Action:
The Monitor is set to a degraded state under ResourceView and an alert is sent to the Alert Monitor. If the field 'Stalled Time To Stop' is defined in the monitor definition then a stop command will be issued against the session.
User Action:
Issue the display command to check the list of stalled SNA sessions.
Reason:
The region received an FTP transfer termination event that does not have a corresponding START event.
System Action:
Processing continues.
User Action:
None.
Reason:
The region received an FTP transfer in progress event that does not have a corresponding START event.
System Action:
A START event is raised.
User Action:
None.
Reason:
Sthe region received an FTP event indicating that an FTP transfer has started.
P1 is the allocated transfer ID.
P2 is the User ID that initiated the FTP transfer.
P3 qualifies the local file as SOURCE or TARGET .
P4 is the local file name.
P5 is the SOURCE address.
P6 is the TARGET address.
System Action:
A file transfer START event is raised.
User Action:
None.
Reason:
The region received an FTP event indicating that an FTP transfer has successfully completed.
P1 is the allocated transfer ID.
P2 qualifies the local file as SOURCE or TARGET .
P3 is the local file name.
P4 is the number of bytes transmitted.
P5 is the SOURCE address.
P6 is the TARGET address.
System Action:
A file transfer END event is raised.
User Action:
None.
Reason:
The region received an FTP event indicating that an FTP transfer has failed. The message is followed by the RFTOEV06 message, which provides additional information about the failure.
P1 is the allocated transfer ID.
P2 qualifies the local file as SOURCE or TARGET .
P3 is the local file name.
P4 is the SOURCE address.
P5 is the TARGET address.
System Action:
A file transfer FAILURE event is raised.
User Action:
None.
Reason:
The region received an FTP event indicating that an FTP transfer has failed. The message follows the RFFTPV05 message.
P1 is the allocated transfer ID.
P2 is the FTP server error code.
P3 is the text "Reason:" if error text is available.
P4 is the associated error text (if available).
System Action:
None.
User Action:
None.
Reason:
The event handler procedure for the P1 product failed because of an internal error. P2 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The event handler procedure for the P1 product encountered a recoverable error. Check previous message(s) for the cause of the error.
System Action:
Event processing continues. However, some events might have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message - Relevant messages in the activity log
Reason:
The event handler procedure for the P7 product failed because of an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
The message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The event handler procedure failed because of a data error in the event received from the P8 product. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- CONNECT:Mailbox log record type, P6
- Statement text where the error occurred, P7
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is then ignored.
If file transfer logging is active, it is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The message displays a file transfer event trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A request to start a copy of the $RFTPEVM procedure was ignored because another copy is currently running.
System Action:
A new copy of the procedure is not started.
User Action:
None.
Reason:
The heartbeat value in the resource definition was less than the minimum global value. The heartbeat value is increased automatically to P1 .
System Action:
The heartbeat value is increased automatically to the minimum value.
User Action:
None.
Reason:
A TCPaccess FTP server FTPMGR resource changed state and invoked the $RFTPSCT procedure. However, the procedure was invoked without the required P1 keyword.
System Action:
The procedure ends with return code 8.
User Action:
Ensure that you created the FTPMGR resource definition by applying the supplied template. If you modified the parameters for the $RFTPSCT procedure on the State Change Exits panel, ensure that you have not removed the OWNER= or the SERVER= keyword.
Otherwise, contact Technical Support.
Reason:
The heartbeat procedure for stalled file transfers has commenced processing. The message shows the stalled time before an alert is issued, P1 , and the stalled time before the file transfer is flushed,
P2 .
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure of the stalled transfers monitor was invoked without the required Stalled Time to Alert parameter.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the definition, specify the missing value in the Stalled Time to Alert field.
Reason:
The transfer monitor has found no file transfers, for the owning CONNECT:Direct application, that exceed the specified stalled time limit.
P1 identifies the owning CONNECT:Direct application.
P2 is the name of the monitor resource.
P3 is the total number of transfers checked.
P4 is the time.
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure for a CONNECT:Direct monitor resource issued a command to solicit information from the CONNECT:Direct application, and received either no response or a response that was not expected. The response received is in the resource transient log.
P1 identifies the owning CONNECT:Direct region.
P2 is the name of the monitor resource.
System Action:
None.
User Action:
Check the resource transient log for the response, if any, that was received. The response may indicate a degradation within CONNECT:Direct that is causing it not to respond. In which case, remedial action might be necessary.
Reason:
Alerts were raised for P4 CONNECT:Direct file transfers because the transfers exceeded the Stalled Time to Alert value specified for the transfer monitor. P5 transfers were flushed because they exceeded the Stalled Time to Flush value specified for the monitor.
P1 identifies the owning CONNECT:Direct application.
P2 is the name of the monitor resource.
P3 is the number of file transfers checked.
P4 is the number of file transfers for which alerts were raised.
P5 is the number of file transfers flushed.
P6 is the time.
System Action:
None.
User Action:
None.
Reason:
The transfer monitor has found no file transfers in the execution queue of the CONNECT:Direct application being monitored.
P1 identifies the owning CONNECT:Direct application.
P2 is the name of the monitor resource.
P3 is the time.
System Action:
None.
User Action:
None.
Reason:
Monitoring of CONNECT:Direct stalled processes is not available for CONNECT:Direct for P1 .
System Action:
Request is rejected.
User Action:
Delete the CDMON resource as it serves no purpose.
Reason:
A request to act as the manager for CONNECT:Direct agents failed because another process was already performing the function. If KILLPREV=YES was specified, then this process could not be flushed.
System Action:
The request is rejected, and processing terminates.
User Action:
Contact Technical Support.
Reason:
A request to activate or inactivate a CONNECT:Direct agent failed because the manager process could not be started. The request being performed is P1 , and the name of the agent manager is P2 .
System Action:
The request is rejected, and processing terminates.
User Action:
Contact Technical Support.
Reason:
An invalid request was received by the CONNECT:Direct agent manager process. The request data was P1 .
System Action:
The request is rejected, and processing continues.
User Action:
Contact Technical Support.
Reason:
A request was received by the CONNECT:Direct agent manager process, but the request failed. The request was P1 , and the resource being actioned was P2 . The reason for the failure is given by the message,
P3 .
System Action:
Processing continues.
User Action:
Proceed according to message P3 as follows:
Unknown Agent indicates that an invalid agent was named as the file transfer agent. Check this name on the C:D File Transfer Manager General Description panel, and change if appropriate.
Host not known to UNIX agent indicates that the UNIX agent has no record of the named remote host. Check the list of remote hosts defined to the UNIX BMC PATROL agent.
Reason:
A request was successfully completed by the CONNECT:Direct agent manager process. The request was P1 , and the resource to be actioned was P2 .
System Action:
None.
User Action:
None.
Reason:
A request was received by the CONNECT:Direct agent manager process to determine the status of the agent. The resource object ID is P1 , the combined status for the resource is P2 , the status of the event receiver is P3 , and the status of the command broker is P4 . The status of CONNECT:Direct is P5 .
System Action:
None.
User Action:
None.
Reason:
A keyword parameter was either not specified or was specified with an invalid value. The keyword parameter was P1 and the value was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify the keyword parameter with a valid value.
Reason:
The CONNECT:Direct agent manager process has started the connection to the agent at port number P3 and host name/address P4 . The type of connection is P1 , and the resource name is P2 .
System Action:
None.
User Action:
None.
Reason:
A command request to the CONNECT:Direct agent failed because the connection to the agent is not active. The current status for the connection is P1 .
System Action:
Command is rejected.
User Action:
Try later when the connection is active.
Reason:
A command request to the CONNECT:Direct agent timed out.
System Action:
The command has been sent to the agent, but the command processor will terminate. If the timeout is caused by processing delay, then the command responses will eventually be written to the activity log. If there is an error, it will be reflected in the CDMGR resource.
User Action:
Check the activity log later, or check the status of the CDMGR resource.
Reason:
A command request was issued to the CONNECT:Direct agent, but only some of the expected command responses were received within the time allowed. The total number of responses actually received was P1 .
System Action:
The command has been sent to the agent, but the command processor will terminate. If the timeout is caused by processing delay, then the command responses will eventually be written to the activity log. If there is an error, then it will be reflected in the CDMGR resource.
User Action:
Check the activity log later, or check the status of the CDMGR resource.
Reason:
An event arrived indicating that a link manager process was inactive.
P1 indicates the reason, which can be FAILED or ENDED.
System Action:
If the CDMGR is being automated then it will be restarted automatically, otherwise a manual restart of the resource will be required.
User Action:
If the reason for the inactivation is because the process FAILED then check the activity log for related messages and contact your local support representative.
Reason:
The user P1 issued the command P2.
System Action:
The command is passed to the remote system for execution.
User Action:
None.
Reason:
CONNECT:Direct for P1 last completed initialization on the date, P2, at the time, P3, on the system, P4.
System Action:
None.
User Action:
None.
Reason:
The current version of the CONNECT:Direct server for P2 for CDMGR P1 is at version P3.
System Action:
None.
User Action:
None.
Reason:
A status query for CONNECT:Direct server for P1 for CDMGR P2 has returned P3.
System Action:
None.
User Action:
None.
Reason:
A connection to a CONNECT:Direct agent was aborted because of an unrecoverable error. P1 is the associated SOLVE Agent ID and P2 is the error condition.
System Action:
The connection is aborted and processing terminates. The CDMGR resource status is set to FAILED.
User Action:
Possible causes are Host Name or Host Address conflicts between the CDMGR resource definition and the remote agent definitions.
Issue a RES or a CHK CDMGR command to inactivate the resource.
Review and correct any conflicting parameters.
If the problem cannot be resolved, contact Technical Support.
Reason:
The message displays an Agent Link Manager trace record. P1 is the trace ID, P2 is the NCL ID, and P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The command requested was rejected because the server was already processing other commands. The timeout period expired before the command could be processed.
System Action:
Command rejected.
User Action:
Wait until all other commands have completed or use a higher timeout period.
Reason:
The command requested was sent to the remote host for execution.
System Action:
None.
User Action:
Wait for the command responses.
Reason:
The command requested could not be executed because of a communication failure with the remote host.
System Action:
Command rejected.
User Action:
Check the log for addtional messages that explain the actual error.
Reason:
Invalid data was received from a remote host. The remote host name/address was P2 and the port number was P1.
System Action:
The data is rejected. Subsequent messages will indicate the error and contents of the data received.
User Action:
Contact your local support representative.
Reason:
This is the first message of a group of messages showing the data that was received from a remote host. This message is the header for the dump of the data. P1 is the total length (in decimal) of the data and P2 is the total length in hexadecimal.
System Action:
None.
User Action:
Note this message and subsequent messages. Contact your local support representative.
Reason:
This is an informational message showing the invalid data received from a remote host.
System Action:
None.
User Action:
None.
Reason:
This is an informational message indicating the end of the display of invalid data received from a remote host.
System Action:
None.
User Action:
None.
Reason:
A connection was successfully established with a remote system using the protocol P1. The remote system is P2 version P3 on operating system platform P4. The process ID on the remote system is P5 and the NCLID on the local system is P6.
System Action:
None.
User Action:
None.
Reason:
This is the last of a set of messages returned in response to a command issued at a remote host.
System Action:
None.
User Action:
None.
Reason:
The tokens P1 to P2 of the data received were null.
System Action:
None.
User Action:
Note this message and subsequent messages. Contact your local support representative.
Reason:
Invalid data was received from a remote host. The received data was intended for component P1 but was not of the correct data type. Part of the data was P2 and optional type check is P3.
System Action:
The data is rejected. Subsequent messages show the entire data string received.
User Action:
Contact your local support representative.
Reason:
This is the first message of a group of messages showing the data that was received from a remote host. This message is the header for the dump of the data. The data dumped has already been translated and tokenized.
System Action:
None.
User Action:
Note this message and subsequent messages. Contact your local support representative.
Reason:
A command request to the remote CONNECT:Direct completed and no response messages resulted from the command.
System Action:
None.
User Action:
None.
Reason:
The data received from a remote host was invalid for a record type of
P1. The total length of the data received was P2. More messages will follow which dump out the tokenised data.
System Action:
None.
User Action:
Note this message and subsequent messages. Contact your local support representative.
Reason:
The command output was truncated to 1000 lines. The maximum number of lines allowed for a command response is 1000.
System Action:
Only the first 1000 lines of output are returned.
User Action:
None.
Reason:
The protocol connection P1 failed because the remote host, whose name/address is P3 was already connected to this region via the resource name P2.
System Action:
Connection rejected, processing terminates. The CDMGR resourse status is set to FAILED.
User Action:
Issue a RES or a CHK CDMGR command to inactivate the resource.
You are only allowed to connect to the same remote host ONCE per region. Specify a different remote host name/address and retry.
Reason:
The protocol connection P1 was rejected because an attempt to get the IP address for the specified host name failed/timed out. The host name was P2.
System Action:
Connection rejected, processing terminates. The CDMGR resourse status is set to FAILED.
User Action:
Issue a RES or a CHK CDMGR command to inactivate the resource.
See related messages to determine the reason for the error or specify the IP address in the resource definition.
Reason:
The protocol connection P1 could not determine the host name for address
P2.
System Action:
Processing continues.
User Action:
See related messages to determine the reason for the error.
Reason:
The message displays an Agent Connection trace record. P1 is the trace ID, P2 is the NCL ID, and P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
This message is a status message from the agent that monitors CONNECT:Direct. P1 is the host name of the system, P2 is the port number on which CONNECT:Direct is listening for API connections, and P3 is the status of CONNECT:Direct. The status can be either UP or DOWN .
P4 provides additional information if the status is DOWN.
System Action:
None.
User Action:
If CONNECT:Direct is up, no action is required.
If CONNECT:Direct is down or the CONNECT:Direct user exit is down, you must start or restart CONNECT:Direct.
Reason:
This message is a status message from the primary CONNECT:Direct agent on P1 . It indicates that the primary agent has established BMC PATROL connection to the secondary agent on P2 .
System Action:
The region will commence monitoring the status of CONNECT:Direct on P2 .
User Action:
None.
Reason:
This is a status message from the primary CONNECT:Direct agent on P1 . It indicates that the primary agent has lost BMC PATROL connection to the secondary agent on P2 .
System Action:
The status of the CDMGR resource for P2 is set to FAILED.
User Action:
Check the status of the BMC PATROL connection between P1 and P2 .
Reason:
This is a status message from the primary CONNECT:Direct agent on P1 . It indicates that the primary agent is attempting for the nth time to reestablish the BMC PATROL connection to the secondary agent on P2 .
System Action:
None.
User Action:
None.
Reason:
This is a status message from the primary CONNECT:Direct agent on P1 . Following an earlier failure, the primary agent has attempted to reestablish the BMC PATROL connection to the secondary agent on P2 , but the attempts have failed.
System Action:
None.
User Action:
Investigate the state of the BMC PATROL agents on the remote hosts.
Reason:
This is a status message about the Agent for CONNECT:Direct service that monitors CONNECT:Direct, and generates file transfer events and status events as they occur. P1 identifies the service and its status, which can be either UP or DOWN .
System Action:
None.
User Action:
If the service is up, no action is required.
If it is down, then the agent has failed to restart the service and assistance is required.
Reason:
An error occurred while a command (for example, a sys or CONNECT:Direct command) was being passed to a PATROL agent. P1 is the error text.
System Action:
None.
User Action:
See the PATROL agent message documentation for a full explanation.
The most common reason for the error is that the PATROL agent on the system to which you are sending the command is inactive.
Reason:
The log file, file ID P1 , is not available for processing because an attempt to open the file resulted in a file return code of P2 .
System Action:
The $RFVIEW log browsing procedure terminates.
User Action:
Refer to the NCL Reference to evaluate the file return code; this is the &FILERC system variable as set by &FILE OPEN. Use the SHOW ALLOC and SHOW UDB commands to determine why the file is not available. Correct the problem, and retry.
Reason:
The time must be specified as an operand of the TIME command.
System Action:
The command is not executed.
User Action:
Specify a time as an operand of the TIME command (for example, TIME 13.12.10).
Reason:
The specified time was invalid.
System Action:
The command is not executed.
User Action:
The time should be in the format hh.mm.ss.hs (for example, 10.30.25.05). Only the first two digits, which represent the hours, are mandatory.
Reason:
No log data was found for the date that you specified on the DATE command.
System Action:
None
User Action:
If appropriate, specify a different date. For a list of dates that contain log data, enter the DATE command without specifying a date.
Reason:
The / command was specified, indicating that any text following the / shall be issued as a command, but no text was specified.
System Action:
None.
User Action:
Specify a product command after the / .
Reason:
The / command was specified, indicating that any text following the / shall be issued as a command, but you are not authorized to issue commands.
System Action:
None
User Action:
Contact your system administrator to review your privileges.
Reason:
A command was issued by the use of the / command.
System Action:
None
User Action:
None
Reason:
You have entered the REGION or HLREGION command, specifying a value that contains too many characters.
System Action:
The command is not executed.
User Action:
Specify a value that is less than or equal to eight characters in length.
Reason:
You have entered the ORIGIN or HLORIGIN command, specifying an origin that is more than eight characters long.
System Action:
None
User Action:
Specify a value that is less than or equal to eight characters in length.
Reason:
The LOCATE command on this panel enables you to jump to any labels that you have previously defined.
System Action:
None
User Action:
The following is an example of how to define a label:
Command===> .TOP
The following is an example of how to locate a label:
Command===> LOCATE .TOP
The following is an example of how to get a pick list of defined labels:
Command===> LOCATE .?
If you wish to locate a time or date, use the TIME or DATE command.
Reason:
The number of records to be searched must be entered as an operand of the FINDMAX command.
System Action:
Command field placed in error.
User Action:
Specify the number of records to be searched as an operand of the FINDMAX command.
Reason:
The number of lines specified to search was invalid.
System Action:
Command field placed in error.
User Action:
The number of lines to search should be specified and must be in the range 500 to 10000.
Reason:
A print range that was defined previously has been cancelled.
System Action:
None
User Action:
None
Reason:
You have attempted to mark the start of a print range without indicating from which log record you wish the print range to start.
System Action:
None
User Action:
Mark the start of the range by using one of the following methods:
- To mark by cursor: Type PRINT START at the Command ===> prompt.
- Place your cursor on a log record within the scrollable window. - Press ENTER.
- To mark by time, use the DATE and TIME operands.
Reason:
The start of the print range was set successfully.
System Action:
None
User Action:
None
Reason:
You attempted to mark the start of the print range after the end-of- print range marker that you have set previously.
System Action:
The start-of-print position is not marked.
User Action:
Ensure that the start-of-print marker is always before the end-of-print marker. If necessary, you can enter the PRINT CANCEL command to remove any existing markers and then specify the new markers.
Reason:
The start of the print range was changed successfully.
System Action:
None
User Action:
None
Reason:
You have attempted to mark the end of a print range without indicating at which log record you wish the print range to end.
System Action:
None
User Action:
Mark the end of the range by using one of the following methods:
- To mark by cursor:
- Type PRINT END at the Command ===> prompt. - Place your cursor on a log record within the scrollable window. - Press ENTER.
- To mark by time, use the DATE and TIME operands.
Reason:
The end of the print range was set successfully.
System Action:
None
User Action:
None
Reason:
You attempted to mark the end of the print range before the start-of- print range marker that you have set previously.
System Action:
The end-of-print position is not marked.
User Action:
Ensure that the end-of-print marker is always after the start-of-print marker. If necessary, you can enter the PRINT CANCEL command to remove any existing markers and then specify the new markers.
Reason:
The end of the print range was changed successfully.
System Action:
None
User Action:
None
Reason:
An invalid operand was specified with the PRINT command.
System Action:
The command is not executed.
User Action:
Valid operands are START, END, and CANCEL. Press F1 (Help) for further information about the operands for the PRINT command.
Reason:
One of the operands you specified with the PRINT START or PRINT END command is invalid.
System Action:
The command is not executed.
User Action:
Specify a valid PRINT operand. Valid operands are DATE and TIME. The following are examples of valid PRINT commands:
PRINT START DATE=-1 TIME=13.30
PRINT END DATE=15/07/97 TIME=23.30.28
Reason:
The specified date was invalid.
System Action:
The command is not executed.
User Action:
The date should be in the format dd/mm/yy (for example, 21/07/97). For more information about date formats, press F1 (Help).
Reason:
The log you have selected is being swapped by the file transfer log process.
System Action:
The request is rejected.
User Action:
Wait a minute, then try again.
Reason:
The Log View procedure has been invoked without a specific file ID. The default of the currently active file transfer log cannot be used as there is no current active log.
System Action:
The request is rejected.
User Action:
Contact your systems administrator.
This message indicates that file transfer logging is inactive. The file transfer log is defined by the $RF FTLOGS parameter group. Review the group as follows:
- Ensure that file transfer logging has been requested.
- If logging is not active, consider starting it.
- If it is active, check the initialization log to ensure that the parameter group initialized successfully.
- If there are no apparent errors, re-activate the parameter group to restart the file transfer logging process. Review the activity log for additional messages.
Reason:
Processing stopped because an error was encountered during an attempt to read from the file transfer log file.
System Action:
The Log View procedure, $RFVIEW,terminates.
User Action:
Contact your systems administrator.
This message indicates a file transfer logging failure. Use the key, return code, and VSAM feedback code values to determine the specific nature of the error:
- FILEID( P1 ) is the current file ID.
- FILERC( P2 ) is the value for &FILERC as set by the &FILE GET NCL verb. Refer to the NCL Reference for an explanation of the value.
- VSAMFDBK( P3 ) is the VSAM Feedback code. Refer to your VSAM Reference manual for an explanation of the value.
The file transfer log is defined by the $RF FTLOGS parameter group. Review the group as follows:
- Check the file transfer log parameters, particularly the log file VSAM options. Ensure that these are consistant with the explanation of the VSAM feedback code.
- If there are no apparent errors, re-activate the parameter group to restart the file transfer logging process. Review the activity log for additional messages.
If the problem cannot be resolved, contact your local support representative.
Reason:
When issuing a DATE command for a remote log, the starting date must be specified.
System Action:
The command is rejected.
User Action:
The starting date must be specified with a DATE command. The date should be in the format dd/mm/yy (for example, 21/07/97). Refer to the help for further information about the date formats.
Reason:
Currently, there is no support for printing remote log records.
System Action:
The command is rejected.
User Action:
Log on to the remote region, and print the log records from there.
Reason:
Currently, there is no support available on cursor sensitive help for the remote file transfer activity log.
System Action:
The command is rejected.
User Action:
Help for messages is only available in the local region. Log on to the remote region, and view its file transfer log. You may then use the HELP command, normally assigned to the F1 key.
Reason:
The region received an unexpected return code while retrieving information from a remote file transfer log. This message displays the details of the failing NCL &APPC verb.
System Action:
The operation is terminated.
User Action:
A return code of 16 may indicate that the INMC link to the remote system is inactive. If the cause of the error cannot be determined, contact Technical Support.
Reason:
Unexpected APPC WHAT RECEIVED state was encountered when attempting to retrieve data from a remote log.
System Action:
None
User Action:
Contact your local support representative.
Reason:
An invalid keyword was passed to a procedure.
System Action:
The request is rejected.
User Action:
Contact your local support representative.
Reason:
The PRINT command was entered, but the section of the log for printing was not selected.
System Action:
The print request is rejected.
User Action:
Use the PRINT START and PRINT END commands to mark the section of the log that you wish to print, and then reissue the PRINT command.
Reason:
You have scrolled past either the beginning or the end of the log file, resulting in the log being swapped for the next log file in sequence.
System Action:
None
User Action:
The message is informational only.
Reason:
You have scrolled past either the beginning or the end of a day's log, resulting in records for the next or previous day being displayed.
System Action:
None
User Action:
The message is informational only.
Reason:
The cursor was not on a line with a valid timestamp.
The F4 (ActLog) function key (which issues the ACTLOG command) enables you to access the activity log from the file transfer log. The part of the activity log displayed is determined by the timestamp of the entry the cursor is on.
System Action:
The command is rejected.
User Action:
Place the cursor on a log entry in the file transfer log, and press F4 again. If there are no valid lines in the log, the ACTLOG function is not available.
Reason:
A search for records has been cancelled by the operator from the confirm search panel.
System Action:
The search is terminated.
User Action:
None.
Reason:
No log data was found for the time that you specified on the TIME command or as part of the PRINT TIME= command operand.
System Action:
None
User Action:
Review the logs to determine a valid time stamp.
Reason:
No file transfer events have been recorded by the region.
System Action:
None.
User Action:
None.
Reason:
The current state of the file transfer manager resource is not ACTIVE, as indicated by P1 .
System Action:
The VIP command is terminated.
User Action:
Investigate why the file transfer manager resource is not active, and take the necessary steps to rectify the situation.
Reason:
The VIP command has been issued against resource P1 . The listener TCP/IP port is required for command processing but cannot be obtained.
System Action:
The VIP command terminates.
User Action:
A possible cause of this condition is that you have not defined an FTP Server Monitor (FTPMON) resource of Type TC (TCP-CONNECT, TCP/IP Connection Monitor) for this FTPMGR.
Press F4 (Add) to define a TCP/IP Connection Monitor.
Reason:
The current state of the TCP/IP services is not ACTIVE, as indicated by
P1 .
System Action:
The VIP command is terminated.
User Action:
Investigate why the TCP/IP services is not active, and take the necessary steps to rectify the situation.
Reason:
The command is not supported by CONNECT:Direct for P1 .
System Action:
The command is rejected.
User Action:
None
Reason:
The process definition identified by P1 was changed successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was deleted successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was flushed successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was held successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was released successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The process definition identified by P1 was suspended successfully by the user P2 .
System Action:
None.
User Action:
None. This message is informational only.
Reason:
The P1 mail box P2 batch P3 was p4 by P5 .
System Action:
None.
User Action:
None.
Reason:
This message appears in the transient log for a resource and indicates which command was requested by which user for this resource.
System Action:
None.
User Action:
None.
Reason:
The following parameters were not passed to the GetCDProcess procedure within the $RFWEBPK package:
Parameter 1 - must specify the resource type (for example, STC).
Parameter 2 - must specify the queue type (for example, HOLD).
Parameter 3 - must specify the resource object ID.
System Action:
Package procedure fails.
User Action:
Update the parameters passed to this procedure.
Reason:
The resource status is active.
System Action:
None.
User Action:
None.
Reason:
The resource status is P1.
System Action:
None.
User Action:
None.
Reason:
The selected process is no longer active.
System Action:
None.
User Action:
Close the displayed window, refresh the list and select another process.
Reason:
The P1 CA-XCOM transfer request was held by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was released by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was resumed by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was suspended by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was terminated by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was deleted by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was altered by P2 .
System Action:
None.
User Action:
None.
Reason:
An attempt to translate an object into an XML document for transmission to a data warehouse failed. The data was sourced from application P1, data class P2. The error occurred in mapping the object, the return code and feedback codes for the action were P3. P4 is the name of the component in error.
System Action:
The object is discarded and processing continues.
User Action:
Contact your local support representative.
Reason:
A specified date was invalid. A valid format is dd-mmm-yyy (for example, 21-JUL-2001).
System Action:
None.
User Action:
Correct the date.
Reason:
A specified time was invalid. A valid format is hh.mm (for example, 17.10). hh is in the range 0 through 23; mm is in the range 0 through 59.
System Action:
None.
User Action:
Correct the time.
Reason:
The specified priority must be in the range 0 through 255.
System Action:
None.
User Action:
Specify the correct priority.
Reason:
You pressed F6 (Action) without specifying a value. You cannot perform the Alter action if there is nothing to alter.
System Action:
None.
User Action:
If you do not want to alter anything, press F12 (Cancel).
Reason:
The command processor failed to start an APPC conversation with a CA-XCOM region. P1 and P2 are the return and feedback codes for the APPC allocation.
System Action:
APPC allocation fails, and CA-XCOM command processing terminates.
User Action:
At the status monitor, review the extended display of the XCOM resource. If you cannot resolve the problem, contact Technical Support.
Reason:
The command processor failed while changing from sending to receiving in an APPC conversation. P1 and P2 are the return and feedback codes for the APPC PREPARE_TO_RECEIVE verb.
System Action:
CA-XCOM command processing terminates.
User Action:
At the status monitor, review the extended display of the XCOM resource. If you cannot resolve the problem, contact Technical Support.
Reason:
The command processor failed while in the receiving mode. P1 and P2 are the return and feedback codes for the APPC RECEIVE verb.
System Action:
CA-XCOM command processing terminates.
User Action:
At the status monitor, review the extended display of the XCOM resource. If you cannot resolve the problem, contact Technical Support.
Reason:
The command processor failed while in the sending mode. P1 and P2 are the return and feedback codes for the APPC SEND verb.
System Action:
CA-XCOM command processing terminates.
User Action:
At the status monitor, review the extended display of the XCOM resource. If you cannot resolve the problem, contact Technical Support.
Reason:
The command (action) on a CA-XCOM transfer request was successful.
System Action:
The command is processed by the CA-XCOM region.
User Action:
None.
Reason:
The P1 CA-XCOM command issued to the $RFXCCMD command processor is invalid. Ensure that one of the following values is specified in the COMMAND parameter passed to the processor:
ACTIVE to display active transfer requests.
QUEUED to display queued transfer requests.
HOLD to hold a transfer request. The CORR parameter is also required.
RELEASE to release a transfer request. The CORR parameter is also required.
SUSPEND to suspend a transfer request. The CORR parameter is also required.
RESUME to resume a transfer request. The CORR parameter is also required.
DELETE deletes a transfer request. The CORR parameter is also required.
ALTER to alter a transfer request. The following parameters are also required:
- CORR - ALTERFLG - ALTERDATA
System Action:
The command processor ($RFXCCMD) fails.
User Action:
Contact Technical Support.
Reason:
The command processor failed to define the transaction ID for communicating with the P1 CA-XCOM manager. P2 identifies the message that provides information about the failure.
System Action:
CA-XCOM command processing terminates.
User Action:
Reason:
The command processor cannot determine the LU name of the P1 CA XCOM region.
System Action:
The $RFXCCMD command processor terminates, and the extended display of the affected CA XCOM manager and monitors are updated.
User Action:
Ensure that the P1 CA XCOM region is set up correctly for the CA NetMaster FTM CA XCOM event exit.
For more information, see the CA NetMaster File Transfer Management Installation Guide.
Correct any problems, and then enter CHK beside the P1 manager.
If the event exit is implemented correctly and the problem still occurs, contact Technical Support.
Reason:
The P1 command to the P2 CA-XCOM region failed. P3 identifies the message that provides information about the failure.
A possible cause is that the command was issued to the CA-XCOM region to perform an action on a transfer request that did not have the correct status.
System Action:
CA-XCOM command processing terminates.
User Action:
If the problem persists, contact Technical Support.
Reason:
The command processor failed to terminate an APPC conversation with the
P1 CA-XCOM region and deallocate the associated resources. P2 and P3 are the return and feedback codes for the APPC DEALLOCATE verb.
System Action:
CA-XCOM command processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Enter CHK beside the P1 manager. If a problem still exists, contact Technical Support.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
The P1 manager resource is inactive.
System Action:
CA-XCOM command processing terminates.
User Action:
Activate the P1 resource. If the problem persists, contact Technical Support.
Reason:
The NetMaster for File Transfer CA-XCOM command processor failed because of an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The $RFXCCMD CA-XCOM command processor failed to profile for EDS notification of events for the P1 LU. The associated command is P2 .
P3 and P4 are the return and feedback codes.
System Action:
CA-XCOM remote node processing terminates.
User Action:
Contact Technical Support.
Reason:
This message provides debugging information for the CA-XCOM command processor.
System Action:
None.
User Action:
None.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM command processing terminates.
User Action:
Contact Technical Support.
Reason:
A MODIFY command to the CA-XCOM region failed. P1 provides the reason for the failure.
System Action:
CA-XCOM MODIFY command processing terminates.
User Action:
Review the activity log to determine if remedial action is required. If the problem persists, contact Technical Support.
Reason:
A MODIFY command to the CA-XCOM region failed. This may have occurred because invalid data was entered in the previously displayed panel, or the response received from XCOM was not complete.
System Action:
CA-XCOM MODIFY command processing terminates.
User Action:
Review the displayed output for indication of the failure. Perform any required remedial action, and reissue the command. If the problem persists, contact Technical Support.
Reason:
A MODIFY command was issued to the CA-XCOM region, and the response timed out.
System Action:
CA-XCOM MODIFY command processing terminates.
User Action:
Reissue the command. If the problem persists, contact Technical Support.
Reason:
The specified value must be a valid data set member name.
System Action:
The value is rejected.
User Action:
Correct the name.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM command processing terminates.
User Action:
Contact Technical Support.
Reason:
A MODIFY command to the CA-XCOM region failed. P1 is the return code from the $RMCMDRG procedure.
System Action:
CA-XCOM MODIFY command processing terminates.
User Action:
Review the activity log to determine what remedial action is required. If you cannot correct the problem, contact Technical Support.
Reason:
No member name has been specified.
System Action:
None.
User Action:
Specify a member name or press F12(Cancel).
Reason:
A specified value must be numeric and in the displayed range.
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM command processing terminates.
User Action:
Contact Technical Support.
Reason:
A MODIFY command to the CA-XCOM region failed. P1 provides the reason for the failure.
System Action:
CA-XCOM MODIFY command processing terminates.
User Action:
Review the activity log to determine if remedial action is required. If the problem persists, contact Technical Support.
Reason:
You specified a value for P1 that exceeded the value you specified for the maximum number of tasks allowed. The value in the Maximum Local Tasks Allowed or the Maximum Remote Tasks Allowed field must be less or equal to the value in the Maximum Tasks Allowed field.
System Action:
The value is rejected.
User Action:
Correct the value.
Reason:
You pressed F6 (Action) without specifying a value.
System Action:
None.
User Action:
Specify a value, or press F12 (Cancel) to cancel the operation.
Reason:
A CA-XCOM file transfer has started:
P1 identifies the transfer as CA-XCOM transfer ID(request number).
P2 is the initiator user Id and P3 is the initiator node.
This message is followed by RFXCEV02 which provides additional details.
System Action:
None.
User Action:
None.
Reason:
A CA-XCOM file transfer has started:
P1 identifies the transfer as CA-XCOM transfer ID(request number).
P2 is source node and P3 is the target node.
This message follows message RFXCEV01.
System Action:
None.
User Action:
None.
Reason:
A CA-XCOM file transfer has completed successfully:
P1 identifies the transfer as CA-XCOM transfer ID(request number).
P2 is source node and P3 is the target node.
System Action:
None.
User Action:
None.
Reason:
A notification has been received from CA-XCOM, indicating a failed file transfer:
P1 identifies the transfer as CA-XCOM transfer ID(request number).
P2 is source node and P3 is the target node.
This message is followed by RFXCEV11 which provides error details.
System Action:
None.
User Action:
None.
Reason:
A non-orderly CA-XCOM shutdown notification was received from P1 .
System Action:
A file transfer failure event will be raised for each currently active CA-XCOM transfer (if any).
User Action:
If desired, restart the CA-XCOM application.
Reason:
The region received a file transfer completion event for the P1 CA-XCOM file transfer but never received the corresponding START event.
System Action:
The region will create a dummy START event for this file transfer. Processing continues.
Important! The created START event uses data from the END event. The start time, the user name, and the transfer rate might be incorrect.
User Action:
None.
Reason:
A CA-XCOM file transfer failed, but no error message was received from the CA-XCOM region.
System Action:
None.
User Action:
Review the system log and check the CA-XCOM region to determine the cause of the failure.
Reason:
An unexpected CA-XCOM SHUTDOWN notification has been received.
System Action:
A file Transfer FAILURE event is raised.
User Action:
You may want to review the reasons for the CA-XCOM termination.
Reason:
A notification has been received from CA-XCOM, indicating a failed file transfer:
P1 identifies the transfer as CA-XCOM transfer ID(request number).
P2 is error text.
This message follows message RFXCEV05.
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer CA-XCOM event handler procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CA-XCOM event message format procedure has initialized successfully.
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer CA-XCOM event handler procedure has encountered a recoverable error. Check previous messages for the cause of the error.
System Action:
Event processing continues. However, some events may have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant activity log messages
- CA-XCOM message log
Reason:
The NetMaster for File Transfer CA-XCOM event handler procedure has failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The NetMaster for File Transfer CA-XCOM event handler procedure has failed due to a data error in the event received from CA-XCOM. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- CA-XCOM log record type, P6
- Statement text where the error occurred, P7
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is then ignored.
If file transfer logging is active, it is also written to the file transfer log.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. See the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
The message displays a file transfer event trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Incomplete or invalid data were received for the P1 CA-XCOM file transfer. Its compression could not be determined. P2 shows the number of compressed and uncompressed bytes.
System Action:
Processing continues with the compression percentage set to INCOMPLETE.
User Action:
In the CA-XCOM region, review the transfer details. If the compression data and byte counts are correct, contact Technical Support.
Reason:
The NetMaster for File Transfer CA-XCOM event manager could not process an event. This results in the loss of the event.
P1, describes the field in error.
System Action:
The event is discarded.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- CA-XCOM message log
Reason:
The $RFXCLNK transfer request monitor procedure failed to profile for Event Distribution Services (EDS) notification of events from the P1 manager. P3 and P4 are the return and feedback codes.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
The link to the P1 CA-XCOM region is inactive. P2 is the monitor affected by the link.
System Action:
Heartbeat and command processing terminate.
User Action:
If the P1 XCMGR resource is active, enter CHK beside it. If the problem persists, contact Technical Support.
If the P1 XCMGR resource is inactive, the message is issued as part of a CA-XCOM termination and is for information only.
Reason:
The P1 manager resource is inactive.
System Action:
Heartbeat and command processing terminates.
User Action:
Activate the P1 resource. If the problem persists, contact Technical Support.
Reason:
There were no CA-XCOM transfer requests with a P1 status.
System Action:
None.
User Action:
None.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
The NetMaster for File Transfer CA-XCOM display and action service procedure failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
You canceled the action to alter a CA-XCOM transfer request.
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was altered by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was deleted by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was terminated by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was held by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was released by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was resumed by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 CA-XCOM transfer request was suspended by P2 .
System Action:
None.
User Action:
None.
Reason:
The P1 transfer was not in the P2 state. The applied action could not be processed.
System Action:
None.
User Action:
Press F6 (Refresh) to refresh the list.
Reason:
You issued the P1 command against a transfer request with an incorrect status. The valid actions are as follows:
Transfer Request Status Actions ACTIVE S, /, V, A, SP, and T HELD S, /, V, A, D, and R INACTIVE S, /, V, A, D, and H SUSPENDED S, /, V, A, D, and RES NETERROR S, /, V, A, and D
System Action:
None.
User Action:
Issue a valid command against the transfer request.
Reason:
CA-XCOM has no transfer requests.
System Action:
None.
User Action:
None.
Reason:
You entered a command beside a transfer request, but the CA-XCOM region that processed that transfer had become inactive. P1 identifies the CA-XCOM region.
System Action:
CA-XCOM command processing terminates.
User Action:
When the CA-XCOM region is active again, retry the operation.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
CA-XCOM command processing failed at the $RFXCNTL CA-XCOM transfer monitor controller. P1 P2 identify the affected manager and monitor. Their transient logs contain messages about the failure.
System Action:
XCOM heartbeat processing terminates, and the extended display of the affected CA- XCOM manager and transfer request monitor is updated.
User Action:
Use the messages in the transient logs to help you correct the problem. If you are unable to correct the problem, contact Technical Support.
Reason:
The P1 command passed to the $RFXCNTL CA-XCOM transfer monitor controller is invalid. Valid commands that can be specified in the COMMAND parameter passed to the controller are ACTIVE and QUEUED.
System Action:
CA-XCOM heartbeat processing fails.
User Action:
Contact Technical Support.
Reason:
This message provides debugging information for the CA-XCOM transfer monitor controller.
System Action:
None.
User Action:
None.
Reason:
The NetMaster for File Transfer CA-XCOM display and action service procedure failed due to an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
It is suggested that the information be obtained immediately as follows:
1. Locate the message and dump in the activity log.
2. Use the PRINT START and PRINT END commands to mark the lines. Refer to the activity log help if you do not know how to do this. Ensure that the marked text contains this error message and the entire record dump (that is, up to and including the DD9007 message).
3. Use the PRINT command to print the marked section of the log.
Note: If you use a 3270 terminal emulator and choose to print the diagnostics by using the "cut and paste" procedure, ensure that you include an image where you scroll right to capture the end of this message.
Reason:
A ping command to the P1 CA-XCOM remote node failed. P2 and P3 are the return and feedback codes.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
The heartbeat procedure for the P1 P2 CA-XCOM remote node monitor has commenced.
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure for the P1 P2 CA-XCOM remote node monitor was invoked without the required remote node name.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the definition, identify at least one CA-XCOM remote node to monitor.
Reason:
The remote node monitor has determined that the monitored remote node is available:
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
P3 identifies the remote node.
P4 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The remote node monitor has determined that the monitored remote node is unavailable:
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
P3 identifies the remote node.
P4 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP interface is currently P1 . The monitoring of this resource requires that the status of the TCP/IP interface is ACTIVE.
System Action:
Heartbeat processing does not take place.
User Action:
Display the current TCP/IP services status by issuing a SHOW TCPIP command. Message N3AF05 shows the current TCP/IP interface status.
If the TCP/IP interface status is INACTIVE , issue a TCPIP START command. Wait for message N3B201, and then enter a CHK command against this resource.
If the TCP/IP interface status is QUIESCING or STOPPING , wait for the status to change to INACTIVE and then proceed as above.
If the TCP/IP interface status is STARTING , wait for message N3B201 and then enter a CHK command against this resource.
Reason:
The remote node monitor has determined that the monitored remote nodes are available:
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
P3 identifies the remote nodes.
P4 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The remote node monitor has determined that the monitored remote nodes are unavailable:
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
P3 identifies the remote nodes.
P4 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The region was unable to register for unsolicited messages from a CA-XCOM application. P1 is the reason for the failure. Messages from that application will not appear in the file transfer log.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The heartbeat procedure for the CA-XCOM stalled transfer monitor has commenced processing. The message shows the stalled time before an alert is issued, P1 , and the stalled time before a file transfer is terminated, P2 .
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure of the CA-XCOM stalled transfer monitor was invoked without the required Stalled Time to Alert parameter.
System Action:
Heartbeat processing is terminated.
User Action:
Update the definition of the affected resource. On the Monitor Details panel of the definition, specify the missing value in the Stalled Time to Alert field.
Reason:
The stalled transfer monitor has found no file transfers, for the owning CA-XCOM application, that exceed the specified stalled time limit.
P1 identifies the owning CA-XCOM application.
P2 is the name of the monitor resource.
P3 is the total number of transfers checked.
P4 is the time.
System Action:
None.
User Action:
None.
Reason:
The P1 P2 CA-XCOM stalled transfer monitor failed to terminate the P3 file transfer.
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
P3 is the transfer request number.
System Action:
None.
User Action:
Check the P2 resource transient log for messages that indicate the reason for the failure. Use the messages as a guide to correct the problem.
Reason:
The P1 P2 CA-XCOM stalled transfer monitor:
- Raised alerts for P4 file transfers because the transfers had been idle for the specified Stalled Time to Alert value.
- Terminated P5 file transfers because the transfers had been idle for the specified Stalled Time to Terminate value.
P1 identifies the owning CA-XCOM application.
P2 is the name of the monitor resource.
P3 is the number of file transfers checked.
P4 is the number of file transfers for which alerts were raised.
P5 is the number of file transfers terminated.
P6 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The CA-XCOM stalled transfer monitor has found no file transfers with a status of ACTIVE.
P1 identifies the owning CA-XCOM application.
P2 is the name of the monitor resource.
P3 is the time when the information is obtained.
System Action:
None.
User Action:
None.
Reason:
The heartbeat procedure starts processing for a CA-XCOM transfer request monitor. P1 is the status of the requests to be monitored, and P2 is the threshold specified for the number of requests.
System Action:
None.
User Action:
None.
Reason:
The P3 command passed to the $RFXCTRM CA-XCOM transfer request monitor procedure is invalid. P1 P2 identify the affected monitor. Valid commands that can be specified in the COMMAND parameter passed to the procedure are ACTIVE and QUEUED.
System Action:
CA-XCOM heartbeat processing fails.
User Action:
Contact Technical Support.
Reason:
The heartbeat procedure for a CA-XCOM monitor issued a command to solicit information from the CA-XCOM region but received either no response or a response that was not expected.
P1 identifies the owning CA-XCOM region.
P2 is the name of the monitor resource.
System Action:
None.
User Action:
Check the transient log. The log might indicate that a degradation in the CA-XCOM region is causing the region not to respond. When the degradation is removed, enter CHK beside the monitor.
Reason:
The P1 P2 CA-XCOM transfer request monitor checked the status of the monitored requests, and the number of requests found to be in the P3 state did not exceed the specified threshold.
P1 is the owning CA-XCOM region.
P2 is the name of the monitor.
P3 is the status of the monitored transfer requests.
P4 is the number of transfer requests that were in the P3 state.
P5 is the time when the information was obtained.
System Action:
None.
User Action:
None.
Reason:
The P1 P2 CA-XCOM transfer request monitor checked the status of the monitored requests, and the number of requests found to be in the P3 state exceeded the specified threshold.
P1 is the owning CA-XCOM region.
P2 is the name of the monitor.
P3 is the status of the monitored transfer requests.
P4 is the number of transfer requests that were in the P3 state.
P5 is the time when the information was obtained.
System Action:
None.
User Action:
None.
Reason:
An APPC request to the P1 remote system failed. P2 and P3 are the return and feedback codes for the APPC RPC verb.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
The $RFXCTRM transfer request monitor procedure failed to profile for EDS notification of events from the P1 manager. P3 and P4 are the return and feedback codes.
System Action:
CA-XCOM heartbeat processing terminates, and the extended display of the affected CA-XCOM manager and monitors is updated.
User Action:
Contact Technical Support.
Reason:
This message provides debugging information for the CA-XCOM transfer request monitor.
System Action:
None.
User Action:
None.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, is active. P1 shows the module name and version number. P2 identifies the receiver ID from which CA-XCOM events can be received.
System Action:
None.
User Action:
None.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, has requested the services of the event delivery facility, but the request was rejected because of one of the following:
- The required SSI is not active.
- The SSI is active but is running without the event delivery facility.
System Action:
Event records will be forwarded to the NetMaster for File Transfer region(s) when the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES). To determine the SSI used by this NetMaster region, see the SSI parameter group.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, has requested the services of the event delivery facility, but the request was rejected because the SSI region is not currently active.
System Action:
Event records will be forwarded to the NetMaster for File Transfer region(s) as soon as the SSI region (together with the event delivery facility) becomes active.
User Action:
Ensure that the SSI region is started with the event delivery facility (XEVNT=YES). To determine the SSI used by this NetMaster region, see the SSI parameter group.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, requested the services of the event delivery facility, but the request was rejected because the SSI is shutting down.
System Action:
The event record is not forwarded to this region. This file transfer event is lost.
User Action:
To enable this region to receive CA-XCOM events again, ensure that the SSI region is restarted.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, issued a $NMXEVNT request to forward a CA-XCOM event to the event receiver. The request was rejected. The values of the R0 and R15 return codes from the $NMXEVNT request are P1 and P2 respectively.
System Action:
The event record is not forwarded to this region.
User Action:
Note the value of R0 and R15, and contact Technical Support.
Reason:
This message is the first of a group of messages that are issued when an abend occurs in the CA-XCOM NetMaster for File Transfer exit, NM000FXX. The complete set of messages is:
RFXX06 ABEND AT +nnnn IN xxxxxxxx xxxx LEVEL xxxxxx
RFXX07 Received R1=xxxxxxxx RRD Addr=xxxxxxxx Request #:xxxxxx Status:x RFXX08 PSW=xxxxxxxx xxxxxxxx INT=xxxxxxxx
RFXX09 R0-R3 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFXX09 R4-R7 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFXX09 R8-R11 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
RFXX09 R12-R15 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Message RFXX06 identifies the abend offset, module, version, and level.
Message RFXX07 identifies the parameters passed by CA-XCOM:
Received R1 is the value in R1 when the exit was called.
RRD ADDR is the address of the CA-XCOM RRD. If R1 was invalid, this is shown as UNKNOWN.
Request # is the CA-XCOM request number. If either R1 or the RRD address was invalid, this is shown as ??.
Status is the CA-XCOM Status flag. If either R1 or the RRD address was invalid, this is shown as ?.
Message RFXX08 identifies the failing PSW and program interruption information.
Messages RFXX09 identify the general purpose registers at the time of the abend.
System Action:
The event record is ignored, and processing continues.
User Action:
Contact Technical Support. Ensure that you have the following information available:
- The entire group of messages (RFXX06 to RFXX09)
- The version and maintenance level of the CA-XCOM application
Reason:
This message is one of a group of messages that are issued when an abend occurs in the CA-XCOM NetMaster for File Transfer exit, NM000FXX.
Received R1 is the value in R1 when the exit was called.
RRD ADDR is the address of the CA-XCOM RRD. If R1 was invalid, this is shown as UNKNOWN.
Request # is the CA-XCOM request number. If either R1 or the RRD address was invalid, this is shown as ??.
Status is the CA-XCOM Status flag. If either R1 or the RRD address was invalid, this is shown as ?.
For more information, see the help for message RFXX06.
System Action:
See RFXX06.
User Action:
See RFXX06.
Reason:
This message is one of a group of messages that are issued when an abend occurs in the CA-XCOM NetMaster for File Transfer exit, NM000FXX.
For more information, see the help for message RFXX06.
System Action:
See RFXX06.
User Action:
See RFXX06.
Reason:
This message is the last of a group of messages that are issued when an abend occurs in the CA-XCOM NetMaster for File Transfer exit, NM000FXX.
For more information, see the help for message RFXX06.
System Action:
See RFXX06.
User Action:
See RFXX06.
Reason:
The forwarding of CA-XCOM events has resumed. This message indicates a recovery from a previous error condition (for example, the required SSI region was successfully restarted).
System Action:
CA-XCOM events are now sent to the event receiver.
User Action:
None.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, requested the services of the event delivery facility. The request was rejected because the event delivery facility could not obtain storage (R0=7 and R15=28 returned from $NMXEVNT).
System Action:
The CA-XCOM event is not sent to the event receiver.
User Action:
Contact Technical Support.
Reason:
This is a diagnostic trace message.
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, was called by CA-XCOM. The event record was identified as follows:
P1 is the CA-XCOM request number.
P2 is an NM000FXX action:
SELECTED indicates that the event record will be forwarded to the NetMaster for File Transfer region(s).
IGNORED indicates that the event record is ignored.
P3 is the CA-XCOM request status.
P4 is the CA-XCOM request type.
P5 is the CA-XCOM transfer type.
System Action:
None.
User Action:
None.
Reason:
The CA-XCOM NetMaster for File Transfer exit, NM000FXX, was called by XCOM. The event record is not recognized as a valid CA-XCOM event.
P1 and P2 are the reasons for the error.
System Action:
The event record is not forwarded to this region.
User Action:
Contact Technical Support. Ensure that you have the version and maintenance level of the CA-XCOM application.
Reason:
The CA-XCOM exit for NetMaster for File Transfer, NM000FXX, was unable to obtain or free up working storage. P1 is the failing request, and
P2 is a code that indicates the reason of the failure.
System Action:
The request cannot be processed.
User Action:
Use the R15 code to determine the cause of the error.
Reason:
A request to initiate or terminate events tracing has been accepted by the CA-XCOM exit for NetMaster for File Transfer, NM000FXX.
P1 is either ON or OFF .
System Action:
CA-XCOM exit for NetMaster events tracing is activated or deactivated.
User Action:
None.
Reason:
The CA-XCOM exit for NetMaster for File Transfer, NM000FXX, has received a notification of an immediate or abnormal CA-XCOM shutdown.
System Action:
A CA-XCOM shutdown event is sent to the NetMaster for File Transfer region(s).
User Action:
None.
Reason:
The CA-XCOM exit for NetMaster for File Transfer, NM000FXX, has received an unsupported CA-XCOM operator command ( P1 ).
System Action:
The command is ignored, and processing continues.
User Action:
Check the spelling of the command, and reissue the command.
Reason:
This is a diagnostic trace message.
The NetMaster for File Transfer CA-XCOM exit, NM000FXX, has received the
P1 CA-XCOM operator command.
System Action:
The P1 command is processed.
User Action:
None.
| Copyright © 2012 CA. All rights reserved. |
|