Chapter 6: Link error messages 293Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance GuideThis might happen when the Application Module or IPE Module isexperiencing heavy message traffic while other activities (trace running,monitoring, and so on) are running. Avoid unnecessary activity on theApplication Module or IPE Module during high message traffic periods.mlusr error messagesThe following summary of the error messages reported by applicationsoftware to the system console covers the error messages in ApplicationRegistration, DN Registration, Link Maintenance, and Message Facility.Note: 0x may appear in the error message, and indicateshexadecimal. It is not listed with the error messages in this guide.An explanation is provided for each error message; a solution is suggestedon how to correct the error. The following message may appear in the LinkStatus Response Message:000A - Link to SL1 down pending security validationWhenever the link to the Meridian 1 is established, checks are made toverify that package 209 is installed and that the machine ID and thetape ID match. This message indicates these checks are under way. Ifthe checks are successful, the link will establish normally.The following values may appear in the Application Registration Responsemessage.000B - Request already in progressA user has attempted to invoke an mlusr command (such as continuitytest) that has already been invoked.0502 - Association Table is fullIndicates the limit for the number of applications that can register hasbeen reached. This state can be remedied either by restarting theapplication by rebooting the module or by releasing one or moreassociations.0902 - Link process does not existMeridian Link software MLINK or HLINK processes cannot beinvoked. To rectify this problem, shut down and restart the application(including the Meridian Link software).
