Initialization messages

DFSMSrmm issues several types of initialization messages requiring your intervention. Your installation should have set procedures, many of them automated, for handling many of the error situations described in these messages.

Critical initialization errors usually cause DFSMSrmm to shut down. Report any diagnostic error messages to your system programmer as soon as possible.

If a working version of the old initialization parameters is still available, you can restart DFSMSrmm using the old parameters. If tapes used and the DFSMSrmm subsystem cannot be started, you can remove DFSMSrmm from the system and, if your installation permits, allow tape mounts to be processed without a media management system. See Stopping the DFSMSrmm subsystem for more information.

The following lists initialization messages, many that require your response:
  • EDG0001I DFSMSrmm SUBSYSTEM INTERFACE INITIALIZATION COMPLETE FOR ENTRY ssname
    • DFSMSrmm is beginning to come up. It is still down. Wait for message EDG0105I. You do not need to reply to this message.
  • EDG0204I DFSMSrmm BEING INITIALIZED FROM MEMBER member_name IN parmlib_dataset
    • DFSMSrmm is getting setup information from its parmlib member. Wait for message EDG0105I. You do not need to reply to this message.
  • EDG0110D ENTER TODAY'S DATE WITH FORMAT day date_option OR "CANCEL"
    • Reply with today's date. Use the date format set by your installation.
      where:
      • day is MON, TUE, WED, THU, FRI, SAT, SUN
      • date_option is the date format set by your installation
      For example, reply with: THU,02/20/1993.
    • This reply is checked against the system date, and the message reoccurs if the system date is different. In this case, either reset the system date or reply with the correct current date.

      Do not automate your response to this message. Until you respond to this message, DFSMSrmm initialization does not complete and no tape mounts are allowed.

  • EDG0114I SYSTEM DATE system_date VERIFIED
    • The date entered in message EDG0110D is the same as the system date. You do not need to reply to this message.
    EDG0105I DFSMSrmm SUBSYSTEM INITIALIZATION COMPLETE
    • DFSMSrmm is now up and active. You do not need to reply to this message.
  • EDG0101I STARTED TASK ENDED BECAUSE THE DFSMSrmm SUBSYSTEM IS ALREADY ACTIVE
    • DFSMSrmm is already up and active, but a START command was issued again and the second START command failed.

      You do not need to reply to this message since DFSMSrmm is already running. Do not start DFSMSrmm without first stopping DFSMSrmm.

  • EDG0104E DFSMSrmm SUBSYSTEM INITIALIZATION FAILED
    • DFSMSrmm is down and could not be brought up. Notify your system programmer immediately. Do not mount any tapes.

      You do not need to reply to this message.

  • EDG1001A DFSMSrmm ADDRESS SPACE ENDING - RESTART IT
    • DFSMSrmm is down.
    • Start DFSMSrmm. If it does not come up, notify your system programmer immediately. Do not mount any tapes.

      You do not need to reply to this message.

  • EDG0103D DFSMSrmm SUBSYSTEM INTERFACE IS INACTIVE - ENTER "IGNORE", "CANCEL", OR "RETRY"
    • DFSMSrmm issues this message at DFSMSrmm procedure start up time or at refresh time when DFSMSrmm is modified to use a new parmlib member.
    • Reply RETRY.
  • EDG0115D THE DFSMSrmm SUBSYSTEM IS NOT RUNNING UNDER A JOB ENTRY SYSTEM - SOME DFSMSrmm FUNCTIONS ARE NOT AVAILABLE. REPLY "IGNORE" OR "CANCEL"
    • DFSMSrmm issues this message at DFSMSrmm procedure start up time or at refresh time when DFSMSrmm is modified to use a new parmlib member. The DFSMSrmm NOTIFY function is one of the functions that is not available when DFSMSrmm is not running under a JES2 or JES3 subsystem.
    • Notify your system programmer and reply as directed.
  • EDG0117DDFSMSrmm DYNAMIC INSTALLATION EXITS INITIALIZATION FAILED – REPLY “IGNORE”, “CANCEL” OR “RETRY”
  • EDG0123D function FOUND TO BE ACTIVE ON SYSTEM system_name - REPLY "Y" TO RESET STATUS OR "N"
    • DFSMSrmm issues this message if inventory management or backup is running on two shared systems, but only one system should run it. DFSMSrmm also issues this message if the subsystem has determined that inventory management is in process on another system but has not completed successfully. This could occur if an z/OS® system has failed and recovery is in process on another system.
    • Notify your system programmer and reply as directed.
  • EDG0215D ERRORS DETECTED IN INITIALIZATION PARAMETERS - ENTER "Y" TO CONTINUE OR "N" TO CANCEL.
    • Errors occurred while bringing up DFSMSrmm, which generate other error messages.
    • Check for other error messages. Based on those messages, either reply Y to allow DFSMSrmm to run or reply N to bring down DFSMSrmm.
    • Notify your system programmer immediately if you bring down DFSMSrmm, as this causes all tape mounts to fail.
  • EDG0228E REUSEBIN(STARTMOVE) REQUIRES EXTENDED BIN ENABLED - USING (CONFIRMMOVE) - REPLY "CONTINUE" OR "CANCEL"
    • DFSMSrmm is processing the OPTION command in parmlib, and checking if the extended bin support is enabled.
    • Report the error to the system programmer. Reply CONTINUE if you want to start DFSMSrmm with parmlib option REUSEBIN(CONFIRMMOVE). Reply CANCEL to stop DFSMSrmm.
  • EDG0238E OVERLAPPING VOLUME SET DEFINED FOR command TYPE(type). value1 OVERLAPS value2
    • A PRTITION or OPENRULE command has specified volume selection operands that conflict with another command.
    • Notify the system programmer. Reply to message EDG0215D as directed. Restart DFSMSrmm when the system programmer has corrected the error.
  • EDG0239E REJECT COMMAND FOUND IN PARMLIB AND NO LONGER SUPPORTED
    • A REJECT command has been found, but one or more PRTITION and OPENRULE commands are also specified. You must use either REJECT commands or OPENRULE and PRTITION commands.
    • Notify the system programmer. Reply to message EDG0215D as directed. Restart DFSMSrmm when the system programmer has corrected the error.
  • EDG0240E YOU CANNOT MIX IBM® AND USER SMF RECORD TYPES FOR SMFAUD AND SMFSEC
    • Both the SMFAUD and SMFSEC operands have been specified. One of the operands specifies "YES" and the other specifies a SMF record type from the user-assigned range.
    • Notify the system programmer. Reply to message EDG0215D as directed. Restart DFSMSrmm when the system programmer has corrected the error.
  • EDG0241E PRTITION COMMAND TYPE(type) volumeorrange valueLOCATION(location) IS NOT A STORAGE HOME LOCATION
    • The location name you specified does not correspond to a LOCDEF defined location of TYPE(STORAGE,HOME).
    • Notify the system programmer. Reply to message EDG0215D as directed. Restart DFSMSrmm when the system programmer has corrected the error.
  • EDG0242E DUPLICATE MEDINF COMMAND FOR NAME name MEDIATYPE type_id,type_name RECORDINGFORMAT format_id,format_name
    • You have specified duplicate MEDINF commands.
    • Notify the system programmer. Reply to message EDG0215D as directed. Restart DFSMSrmm when the system programmer has corrected the error.
  • EDG0243Ioperand IGNORED FOR SYNONYM MEDINF COMMAND FOR NAME name MEDIATYPE type_id,type_name RECORDINGFORMAT format_id,format_name
    • You have specified CAPACITY or REPLACE operands on MEDINF commands that specify synonym names for MEDIATYPE or RECORDINGFORMAT. The CAPACITY and REPLACE operands do not apply to synonym entries and these operands are ignored.
    • Notify the system programmer.
  • EDG0353I SERVER LISTENER TASK HAS ENDED - USE THE MODIFY COMMAND WITH "RESTART LISTENER" TO RESTART
    • The DFSMSrmm server subsystem TCP/IP listener task has ended. If you require the DFSMSrmm subsystem to run as a server use the F DFRMM,RESTART LISTENER operator command once the errors are corrected.
  • EDG0358D SERVER servername COMMUNICATION ERROR - REPLY "CANCEL", OR "RETRY" OR "M=xx"
    • The DFSMSrmm subsystem is communicating between the DFSMSrmm client and server. Reply to EDG0358D with one of the valid responses:
      Reply
      And the result is
      CANCEL
      The current request fails. If the current request is to connect to the server at DFSMSrmm subsystem startup, replying CANCEL stops the DFSMSrmm subsystem.
      RETRY
      Before you RETRY, correct the error that prevented the client system from connecting to the server. DFSMSrmm retries connecting to the server and attempts to continue processing the current request.
  • EDG0361D SERVER STARTUP ERROR - REPLY "RETRY" OR "IGNORE"
    • The DFSMSrmm server subtask is starting up and has been unable to set up TCP/IP communication. Reply RETRY when you want DFSMSrmm to try starting up the server system again by retrying TCP/IP communications. Reply IGNORE when it is acceptable for the DFSMSrmm subsystem to run as a standard system and not as a server system.
  • EDG1101I DFSMSrmm command COMMAND ACCEPTED
    • A stop or modify command was issued and completed. You do not need to reply to this message.
  • EDG1105I STOP COMMAND ENTERED WHILE DFSMSrmm IS QUIESCED AND REQUESTS ARE WAITING TO BE PROCESSED
    • DFSMSrmm issues this message if the STOP command is entered and DFSMSrmm is already quiesced.
    • Reply to message EDG1107D as directed.
  • EDG1106I STOP COMMAND ENTERED WHILE DFSMSrmm IS QUIESCED AND REQUESTS ARE WAITING TO BE PROCESSED - INCLUDING CATALOG STATUS TRACKING
    • DFSMSrmm issues this message if the STOP command is entered and DFSMSrmm is already quiesced.
    • Reply to message EDG1107D as directed.
  • EDG1107D REQUESTS WAIT TO BE PROCESSED – REPLY "STOP", "QUIESCE", "RESTART", OR "M=xx"
    • DFSMSrmm issues this message if the STOP command is entered and DFSMSrmm is already quiesced.
    • Reply to message EDG1107D as described in Table 1.
      Table 1. Operator responses to message EDG1107D
      To Reply And the result is
      Stop DFSMSrmm STOP DFSMSrmm fails the waiting requests and stops.
      Return to the quiesce state QUIESCE DFSMSrmm returns to the quiesce state.
      Restart DFSMSrmm and process waiting requests RESTART DFSMSrmm is restarted using the current DFSMSrmm EDGRMMxx parmlib member.
      Restart DFSMSrmm using a specific parmlib member and process waiting requests M=xx DFSMSrmm is restarted using the DFSMSrmm EDGRMMxx parmlib member you specified.
  • EDG9115I I/O INHIBITED FOR DFSMSrmm PROBLEM DETERMINATION OUTPUT DATA SET, REASON CODE reason_code
    • DFSMSrmm issues this message at start up time if the PDA trace EDGPDOX and EDGPDOY data sets are not defined to DFSMSrmm. DFSMSrmm issues this message once when EDGPDOX is not defined and then again if EDGPDOY is not defined.
    • You need not respond to this message.