SMR0300E SMF Miner: open of SMRLOAD DD failed, RC=hex_return_code
Explanation: The SMF exit load module, SMRXPGM0, must be dynamically loaded from a DD named SMRLOAD that is separate from the joblib and steplib, although the DD may reference the same APF authorized data set as the joblib and steplib, it still must be specified as a separate DD.
Action: Verify that there is an SMRLOAD DD statement in the agent’s job step and that it references an APF authorized load library (PDS or PDSE) containing the load module SMRXPGM0.
SMR0301I SMF Miner: SMF record collection started
Explanation: This message is issued after the SMF exit has successfully completed its initialization and the three SMF exit points have been dynamically installed.
Action: None
SMR0302I SMF Miner: SMF exit removal was successful
Explanation: This message is issued after the SMF exit has been successfully terminated and all ECSA storage it used has been released.
Action: None
SMR0303E SMF Miner: SMF exit removal failed
Explanation: This message will be preceded by other messages indicating the specific problem that occurred in dynamically removing the SMF exit points, deactivating the exit program, and releasing its ECSA storage.
Action: Shut down the agent normally, if possible, or cancel it, then run the stand-alone SMF exit cleanup job after updating the JCL parm with the name of the failing agent job name, PARM=’CLEANUP=SDS.SMR.jobname’. Save the job log from the agent and the stand-alone cleanup job and any SVC dumps that were produced, and contact SDS Technical Support.
SMR0304D SMF Miner: collection requests have changed
Explanation: This message is issued only when debug messages are enabled. It indicates that the SMF collection filters have changed causing the SMF exit to be removed and reinstalled with the new filters.
Action: None
SMR0305D SMF Miner: program_name exit_function_name hex_return_code
Explanation: This message is issued only when debug messages are enabled. It provides a trace of calls from program_name to an SMF exit subroutine exit_function in SMRXPGM0 while the SMF Miner is running.
Action: None
SMR0306E SMF Miner: program_name SMF exit sanity check failed, RC=hex_return_code
Explanation: After the SMF exit has been loaded into ECSA and activated, the next function call to it from the agent is to verify its internal structure. If the exit’s storage has been corrupted, this message will be issued followed by SMR0309E, and the exit will be removed.
Action: Save the job log from the agent and the stand-alone cleanup job and any SVC dumps that were produced, and contact SDS Technical Support.
SMR0307E SMF Miner: program_name IEANTCR failed, TKN=token_name, IEANTRT RC=hex_return_code
Explanation: This message is issued by SMF Miner program_name when it attempts to retrieve the name/token pair created to identify the ECSA storage allocated for the SMF exit as a means of verifying that the name/token pair was created successfully. As a result of the error identified by this message, the SMF exit will immediately be removed and its ECSA storage released.
Action: If the return code is X’04’ this means that another name/token pair has the same name. This could mean that another agent with the same job name is running on the same system or that the SMF exit’s ECSA storage was not released the last time the agent ran. Shut down the current agent and run the stand-alone cleanup job specifying PARM=’CLEANUP=token_name’. If the cleanup job is successful, then restart the agent; otherwise, save the job logs from the agent and the cleanup job and contact SDS Technical Support.
SMR0308I SMF Miner: SMF exit successfully installed and activated
Explanation: This message is issued after the SMF exit has been successfully initialized and SMF collection has started.
Action: None
SMR0309E SMF Miner: SMF exit installation failed
Explanation: This message will be preceded by other error messages that explain the reason for the failure. The partially installed SMF exit will be removed and ECSA storage released.
Action: Save the job log from the agent and the cleanup job and any SVC dumps that were produced, and contact SDS Technical Support.
SMR0310E SMF Miner: no SMF exit points were dynamically installed
Explanation: One of the last steps in the process of activating the SMF exit is to dynamically install the SMF exit points for the system (SYS.IEFU8x) and each subsystem, if any subsystems were defined. Exit module names must be unique. The SMF exit suffixes the exit number (83, 84,85) following the first 6 or less characters of the job name. This error implies that another agent is running with the same first 6 job name characters, or the previous SMF exit was not removed.
Action: Issue this console command to determine the status of all the system exits including the SMF exits: D PROG,EXIT,ALL. Then for each xxx.IEFU8x exit, issue this command: D PROG,EXIT,EX=xxx.IEFU8x, replacing the xxx with a specific exit name. If the module name for the SMF exits looks like the first 6 characters of your jobname, verify that another agent with the same first 6 characters in its jobname is not currently running on the same system. If there is no other agent running, then run the stand-alone cleanup job specifying your agent job name in the JCL parm, PARM=’CLEANUP=SDS.SMR.jobname’. If the cleanup job runs successfully, then you can restart your agent; otherwise contact SDS Technical Support for assistance.
SMR0325E SMF Miner: maximum of 16 collection schedules exceeded
Explanation: This message indicates that there were more unique SMF collection filters (record type/subtype combinations) than the SMF exit could process. Some SMF collection requests were ignored, but normal SMF collection continues. This should never happen.
Action: Save the job log from the agent and contact SDS Technical Support.
SMR0326D SMF Miner: Request=decimal_integer, RT=decimal_integer, RS=decimal_integer, CT=decimal_integer, CS=decimal_integer, KD=keep_delete_option
Explanation: This message is issued only when debug messages are enabled. It shows the values of each SMF collection filter during the current filter scan cycle where RT=record type, RS=record subtype, CT=custom record type, CS=custom subtype, and KD=(K)eep or (D)elete option.
Action: None