multi-platform subsystem test - oracle · 2010-12-29 · multi-platform subsystem test messages and...

��

Multi-PlatformSubsystem Test

Messages and CodesManual

Version 2.04

112151207

112151207EC 123095

The information in this document is confidential and proprietary to Storage TechnologyCorporation and may be used only under the terms of the product license or nondisclosureagreement. The information in this document, including any associated software program, maynot be disclosed, disseminated, or distributed in any manner without the written consent ofStorage Technology Corporation.

Limitation on Warranties and Liability

This document neither extends nor creates warranties of any nature, expressed orimplied. Storage Technology Corporation cannot accept any responsibility for your use of theinformation in this document or for your use of any associated software program. StorageTechnology Corporation assumes no responsibility for any data corruption or erasure as a resultof the use of the information in this document, or the use of software programs. You should becareful to ensure that your use of the information complies with all applicable laws, rules, andregulations of the jurisdictions with respect to which the information is used.

Warning: No part or portion of this document may be reproduced in any manner or in anyform without the written permission of Storage Technology Corporation.

Restricted Rights

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth insubparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause atDFARS 252.227–7013 or subparagraphs (c) (1) and (2) of the Commercial Computer Software–– Restricted Rights at 48 CFR 52.227–19, as applicable.

TrademarksStorageTek is a registered trademark of Storage Technology Corporation.

IBM is a registered trademark of International Business Machines Corporation.

Other product names mentioned in this manual may be trademarks. They are used foridentification purposes only.

Seventh Edition – April 2000

This edition applies to version 2.04 of the Multi-Platform Subsystem Test software for MVS,VM, and PC/DOS operating systems. Information contained in this publication is subject tochange. Comments concerning the contents of this manual should be directed to:

Storage Technology CorporationManager, WWCS Strategic ToolsMS: 4361One StorageTek DriveLouisville, Colorado 80028–4361

� Copyright Storage Technology Corporation 2000. All Rights Reserved.

iii About this Book

About this Book

The Multi-Platform Subsystem Test (MPST) Messages andCodes manual describes the messages issued by MPST, theStand-Alone Executive (SAE), the Control Card Editor, andMPST functions.

For messages issued by the StorageTekFRIEND function refer tothe StorageTekFRIEND Function for MPST Reference Manual.

AudienceThis book was written for Storage Technology Corporation(StorageTek) personnel to support the testing and diagnostics ofStorageTek products.

We’d like to know what you think about this book. For thatpurpose, we’ve included a reader’s comment form in the back ofthis book. Please copy the form, fill it out, and mail it to us.

Reader’sComments

iv MPST Messages and Codes Manual – Version 2.04

About the Software

The following MPST software levels are supported by this book:

� MPST/MVS Version 2.04

� MPST/VM Version 2.04

� MPST/PC Version 2.04

How this Book is Organized

This book contains the messages issued by the Multi-PlatformSubsystem Test (MPST) software program for MVS, VM, andPC/DOS operating systems. Messages are arranged in this bookalpha-numerically by message number.

� Chapter 1. “Return and Abend Codes”.

� Chapter 2. “MPSTCCE.” Control Card Editor messages.

� Chapter 3. “MPSTCCW.” Channel Command-Word Tracemessages.

� Chapter 4. “MPSTCKM.” Count-Key-Data Map messages.

� Chapter 5. “MPSTCPY.” Tape Copy messages.

� Chapter 6. “MPSTDEF.” DEFINE messages.

� Chapter 7. “MPSTGSA.” Generate Stand-Alone Programsmessages.

� Chapter 8. “MPSTINT.” Attention Interrupt messages.

� Chapter 9. “MPSTLEX.” LSM Exerciser messages.

� Chapter 10. “MPSTLIB.” Library Mount messages.

� Chapter 11. “MPSTLOK.” Library Look messages.

� Chapter 12. “MPSTMAN.” MPST Main Processingmessages.

v About this Book

� Chapter 13. “MPSTRLB.” Random Locate Blockmessages.

� Chapter 14. “MPSTTIP.” Tape Independent Protocol Setmessages.

� Chapter 15. “MPSTTKD.” Track Dump messages.

� Chapter 16. “MPSTTMC.” Tape Monitor and Controlmessages.

� Chapter 17. “MPSTTSC.” Tape Scan messages.

� Chapter 18. “MPSTVSC.” Volume Scan messages.

� Chapter 19. “MPSTVTM.” Terminal Control UnitVerification messages

� Chapter 20. “MPSTWRC.” Write-Read Cartridgemessages.

� Chapter 21. “MPSTWRD.” Write-Read Disk messages.

� Chapter 22. “MSAE.” MPST Stand-Alone Executivemessages.

� Index

vi MPST Messages and Codes Manual – Version 2.04

Conventions for Reader Usability

Conventions are used to shorten and clarify explanations andexamples within this book.

The following typographical conventions are used in this book:

� Bold is used to introduce new or unfamiliar terminology.

� ��is used to indicate command names,filenames, and literal output by the computer.

� �� is used to indicate literal input tothe computer.

� �� is used to indicate that you mustsubstitute the actual value for a command parameter. Inthe following example, you would substitute your name forthe “username” parameter.

��

� A bar ( | ) is used to separate alternative parameter values.In the example shown below either username orsystemname must be entered.

��

� Brackets [ ] are used to indicate that a command parameteris optional.

� Ellipses ( ... ) are used to indicate that a command may berepeated multiple times.

� The use of mixed upper and lower case characters (fornon-case sensitive commands) indicates that lower caseletters may be omitted to form abbreviations. Forexample, you may simply enter ��when executing the��command.

Typographic

vii About this Book

Single keystrokes are represented by double brackets ��

surrounding the key name. For example, press �ESC� indicatesthat you should press only the escape key.

Combined keystrokes use double brackets and the plus sign (+).The double brackets surround the key names and the plus sign isused to add the second keystroke. For example, press �ALT��+

�C� indicates that you should press the alternate key and the Ckey simultaneously.

The instruction to “press the �ENTER� key” is omitted from mostexamples, definitions, and explanations in this book.

For example, if the instructions asked you to “enter”��, you would type in��and press�ENTER�.

However, if the instructions asked you to “type”��

��, you would type in��and you would notpress �ENTER�.

The following symbols are used to highlight text in this book.

Warning: Information necessary to keep you from damagingyour hardware or software.

Caution: Information necessary to keep you from corruptingyour data.

Hint: Information that can be used to shorten or simplify yourtask or they may simply be used as a reminder.

Note: Information that may be of special interest to you. Notesare also used to point out exceptions to rules or procedures.

Keys

Enter Command

Symbols

STOP

!

xxxxxxxx

viii MPST Messages and Codes Manual – Version 2.04

Technical Support

Contact CS Software Support at 1–800–866–6789.

Related Documentation

The following books provide more information about the MPSTsoftware product:

� MPST/PC Installation and User’s Guide

� MPST/PC Functions Reference Manual

� MPST/MVS Installation and User’s Guide

� MPST/MVS Functions Reference Manual

� MPST/VM Installation and User’s Guide

� MPST/VM Functions Reference Manual

� StorageTekFRIEND Function for MPST Reference Manual

ix Contents

Contents

About this Book iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reader’s Comments iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Software iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this Book is Organized iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions for Reader Usability vi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typographic vi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keys vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enter Command vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbols vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Support viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1. Return and Abend Codes 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Program and Function Return Codes 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abnormal End (ABEND) Codes 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2. MPSTCCE 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Card Editor Messages 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3. MPSTCCW 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Command-Word Trace (CCWTRACE) Messages 15. . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4. MPSTCKM 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Count-Key-Data Map (CKDMAP) Messages 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5. MPSTCPY 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tape Copy Messages 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

x MPST Messages and Codes Manual – Version 2.04

Chapter 6. MPSTDEF 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEFINE Messages 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7. MPSTGSA 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generate Stand-alone Programs (GENSAPGM) Messages 53. . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8. MPSTINT 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attention Interrupt Messages 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9. MPSTLEX 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Storage Module Exerciser (LSMEXER) Messages 63. . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10. MPSTLIB 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Mount (LIBMOUNT) Messages 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 11. MPSTLOK 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Look (LIBLOOK) Messages 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12. MPSTMAN 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPST Main Processing (MPSTMAIN) Messages 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 13. MPSTRLB 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Random Locate Block (RLB) Messages 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 14. MPSTTIP 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tape Independent Protocol Set (TIPS) Messages 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 15. MPSTTKD 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Track Dump (TRKDUMP) Messages 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 16. MPSTTMC 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tape Monitor and Control (TMC) Messages 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 17. MPSTTSC 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tape Scan Messages 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 18. MPSTVSC 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Scan (VOLSCAN) Messages 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 19. MPSTVTM 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Control Unit Verification (VTERM) Messages 219. . . . . . . . . . . . . . . . . . . . . . . . . . . .

xi Contents

Chapter 20. MPSTWRC 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write-Read Cartridge (WRCART) Messages 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 21. MPSTWRD 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write-Read Disk (WRDISK) Messages 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 22. MSAE 263. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MPST Stand-Alone Executive (MPSTSAE) Messages 263. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xii MPST Messages and Codes Manual – Version 2.04

1 Chapter 1. Return and Abend Codes

Chapter 1. Return and Abend Codes

Program and Function Return Codes

The return code sent to the system is the highest return codeposted by any function to MPST. A return code is only sent ifMPST executes successfully.

Refer to the appropriate Multi-Platform Subsystem TestFunctions Reference Manual for additional information on��and function return code testing.

ReturnCode

Program Use Function Use

0 No errors No errors

4 Not used Warning or minor error

8 Not used Serious error

12 Control card error Control card error or testdevice �� failure

16 File �� or ��failed to ��

2 MPST Messages and Codes Manual – Version 2.04

Abnormal End (ABEND) Codes

��codes indicate problems within the MPST program. Thefollowing �� codes apply to MPST:

ABEND Code 087An [E]STAE environment could not be established for anOS/VS environment. Contact CS Software Support.

ABEND Code 088��for MPST��failed. Increase the partition or region size and tryagain.

ABEND Code 089��for MPST��failed. Increase the partition or region size and try again.

ABEND Code 090Not used. Contact CS Software Support.

ABEND Code 091��/��problem. Contact CS SoftwareSupport.

ABEND Code 092Test device�� /��problem. Contact CS SoftwareSupport.

ABEND Code 093Write to operator problem. Contact CS Software Support.

ABEND Code 094MPST program modules are not at the correct level.Remove all older versions of MPST from the system.

3 Chapter 1. Return and Abend Codes

ABEND Code 095The field test version of MPST has expired. Once a fieldtest has expired MPST prompts the operator for apassword. If the password is entered, execution continues;if the password is not entered, MPST abends. Install thelatest version of MPST.

ABEND Code 099Option��is in effect and the specified trace point IDhas been reached.

5 Chapter 2. MPSTCCE

Chapter 2. MPSTCCE

Control Card Editor Messages

All MPST functions and diagnostics use standard I/O operationchecking routines and these routines issue standard messages forerrors. Error message numbers are issued according to whichfunction or diagnostic was being run when the error occurred.

Hint: To make finding the messages easier, both the messagenumber and the message text are bold.

The following messages are issued for the Control Card Editor:

MPSTCCE00 MPSTCCE05


��

Explanation: This message is issued at the start of the ControlCard Editor.

Solution: None required.

��

Explanation: Either the��or��file does notexist or there are no Control Cards in the existing file.

Solution: Check the��or��file for ControlCards.

��

Explanation: The requested default Control Card set �� wasnot found in the��file.

Solution: Check the��file for control cards set��.

��

Explanation: The MPST function listed is invalid.

Solution: Correct the function name listed in the SYSINControl Card or in the Control Card.

��

Explanation: No SYSIN data was detected in the Job JCL.

Solution: Correct the Job JCL or use the Control Card Editor.

MPSTCCE06 MPSTCCE22


��

Explanation: The current Active and Alternate Control Cardsfailed to save to the�� ile.

Solution: Check that the��still exists and that datacan be written to the file.

�� !"��

Explanation: The Control Card Editor requires a response.

Solution: Enter one of the following:

� ��—to list the Control Card Editor’s edit commands.

� ��—to list the control card sets defined in the��file. �� lists the control cards incontrol card set ��.

� ��$ #—to list the control card set numbers defined inthe��file. ��$ #�� lists the control cards forcontrol card set��.

� �� —to terminate.

��

Explanation: There is no active Control Card in the��

file.

Solution: Check the��file for active Control Cards.

��

��

Explanation: The current active control cards are all listed.


MPSTCCE23 MPSTCCE29


�� !'�#%��%#"$'�#%�� &�#%��#


Solution: Respond to message ��:

� Enter��!'�if you want to list, swap, or modify alternateand/or active control card sets.

� Enter��%#"$'�if you want to list the available control cardset (��) or request a specific control card set��.

� Enter�� &�if you want to build the control card set online.

� Enter��#�if you do not need to modify control cardstatements and you’re ready to start MPST operation usingthe current, active control card set.

�� #%��

Explanation: The Control Card Editor requires a response.Message��will sequentially display Control Cardnumbers 01 through 16 until��is entered.

Solution: Enter the text for the Control Cards. Enter�� toterminate.

��

Explanation: The text entered for Control Card �� wasaccepted. Message��follows this message anddisplays the next sequential Control Card number.


��

Explanation: The maximum number of Control Cards that canbe entered for a set is 16.


MPSTCCE32 MPSTCCE52


��

Explanation: Controls Cards 1 through �� are listed for thecurrent active Control Card set.


��

Explanation: The parameters available for Control Card ��

function are listed.


��

Explanation: �� was entered and the available defaultControl Card sets are listed.


��

Explanation: The HELP file��was not found.

Solution: Load the��file. Refer to the installationinstructions.

��


Solution: Enter the edit command to be performed, �� to listthe available edit commands, or �� to terminate the editfunction.

MPSTCCE53 MPSTCCE55


�� !��

Explanation: The edit command �� is not valid.

Solution: Enter the correct edit command or �� to list theavailable edit commands.

�� !�� !�� #��&%��"�� "�� !�� !�� !� � ��!��!��"�� "��!�� !��

��$��

Explanation: The valid edit commands are listed.


��

Explanation: Edit was requested, but there are no currentControl Cards.

Solution: Enter the name or number for the current ControlCard set.

MPSTCCE56 MPSTCCE61


��

Explanation: The current Control Card �� is listed with itscontents.


��

Explanation: Either �� (list active) or �� (list alternate)was entered and there are no Control Cards for that request.

Solution: Enter the correct request.

��

Explanation: The edit command��(replace) was entered.The Control Card Editor requires a response.

Solution: Enter the contents for the replacement Control Card.

��

Explanation: Control Cards are being inserted into the ControlCard Set and there is no more room. The maximum number ofcontrol cards allowed per control card set is 16.

Solution: End insert mode.

��

Explanation: A change from/to command was entered and thechange from text was not found in the current Control Card.

Solution: Enter the correct change command.

��

Explanation: Either �� (insert after) or �� (insert before)was entered. The Control Card Editor requires a response.

Solution: Enter the contents of the Control Card being inserted.

MPSTCCE62 MPSTCCE93


��

Explanation: The list of active Control Cards was requestedand are listed as part of this message.


��

Explanation: The list of alternate Control Cards was requestedand are listed as part of this message.


��

Explanation: Default Control Card set �� was requested andwas not found in the��file.

Solution: Enter the correct request.

��

Explanation: The Active Control Cards are listed.


��

Explanation: The Alternate Control Cards are listed.


��

Explanation: No Active Control Cards were found in the��file.


MPSTCCE94 MPSTCCE99


��

Explanation: No Alternate Control Cards were found in the��file.


��

Explanation: The Control Card Editor has terminated.


15 Chapter 3. MPSTCCW

Chapter 3. MPSTCCW

Channel Command-Word Trace (CCWTRACE) Messages



The following messages are issued for Channel Command-WordTrace:

MPSTCCW40 MPSTCCW40


� ��

Explanation: This message is issued if CCWtrace is on at thestart of I/O operation (SIO).

� ��—if this is an immediate CCW,��is displayed atthe start of the message. Otherwise,��is displayed.

� �� —the cpu id and the UUT of thecontrol-unit unit.

� �� —the channel-address word specifies theaddress of the channel-command word (CCW).

� �� —the condition code.

� �� —the channel-status wordspecifies the key, the next CCW in the chain, the unitstatus (��) and channel status (��), and the byte count.

� �� —��specifies the CCW address for the channel-command word,the command code (��), data address, flag (��), �� (notused), and the byte count.

� �� —specifies the data address ofthe last CCW in the chain.


MPSTCCW41 MPSTCCW41

17 Chapter 3. MPSTCCW

��

Explanation: This message is issued if CCWtrace is on and aninterrupt has occurred.

� �� —the cpu id and the UUT of thecontrol-unit unit.

� �� —the channel-status wordspecifies the key, the next CCW in the chain, the unitstatus ( �) and channel status (��), and the byte count.

� �� — �� specifies the CCW address for the channel-commandword, the command code (��), data address, flag (��), ��(not used), and the byte count.

� �� —specifies the data address ofthe last CCW in the chain.


19 Chapter 4. MPSTCKM

Chapter 4. MPSTCKM

Count-Key-Data Map (CKDMAP) Messages



The following messages are issued for Count-Key-Data Mag:

MPSTCKM01 MPSTCKM11


��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the��function.


��

Explanation: The record read from cylinder 0, head 0, record 3of the test device was not a valid volume label.


��

Explanation: The volume is not in OS Count-Key-Data format.


��

Explanation: The test device is not a direct access device.


��

Explanation: The test device is not a supported device.Supported devices include:

� 2305–2

� 3330–1, 3330–11

� 3350

� 3380, 3380E, 3380J, 3380–3X

� 3390–1, 3390–2, 3390–3


MPSTCKM13 MPSTCKM23


��

Explanation: The test device failed to open.


��

Explanation: The first DSCB read in the VTOC (volume tableof contents) was not a type 4 DSCB. The VTOC is in error.


��

Explanation: The area GETMAIN’d to hold the internal tracklist was not large enough to contain the number of extentsencountered. This should not happen.

Solution: Contact CSE Software Support.

��

Explanation: The area GETMAIN’d for the internal data setlist was not large enough to contain the number of data setsencountered. This should not happen.

Solution: Contact CSE Software Support.

��

Explanation: An error was found in one or more extents duringVTOC processing. The totals for allocated and free tracks maybe incorrect due to the error.


MPSTCKM24 MPSTCKM27


��

Explanation: The FMT1 DSCB contains a pointer to acorresponding FMT2 or FMT3 DSCB. The record pointed to bythis pointer was not a valid FMT2 or FMT3. The VTOC is inerror.


��

Explanation: The FMT4 DSCB contains a pointer to the firstFMT6 DSCB which then points to the next FMT6 DSCB and soon. The VTOC is in error.


��

Explanation: The��function will only process up to512 split cylinder allocations. More than 512 were encountered.

Solution: Decrease the number of split cylinder allocations.

��

Explanation: Two linked lists are created during VTOCprocessing. The first is a list of data set names with informationconcerning that data set. The second is a list of all extentallocations on the pack. The error occurred when GETMAINswere attempted for these lists and not enough storage wasavailable.

Solution: Increase the region size and retry.

MPSTCKM28 MPSTCKM32


��

Explanation: If a format 6 DSCB (split cylinder allocation) isencountered, a 2K table is GETMAIN’d to construct a list of allsplit cylinder allocations. The error occurred when GETMAINwas issued and not enough storage was available.

Solution: Increase the region size and retry.....

��

Explanation: An I/O error was encountered while attempting toread the volume label at cylinder 0, head 0, record 3.


��

Explanation: An I/O error was encountered while attempting toread a miscellaneous DSCB.


��

Explanation: An I/O error was encountered while attempting toread the first DSCB (format 4) of the VTOC.


25 Chapter 5. MPSTCPY

Chapter 5. MPSTCPY

Tape Copy Messages



The following messages are issued for Tape Copy:

MPSTCPY00 MPSTCPY02


��

Explanation: The��function will be executed on thedevices listed by message��.


��


Solution: Enter the correct parameter.

��

Explanation: Device��at address��with volumeserial number��configured without error.


MPSTCPY03 MPSTCPY03


��

��

��

��

��

��

MPSTCPY04 MPSTCPY04


��

Explanation: The summary for this execution of��

for device��at address��with volume serial number��is printed.

� The number of passes executed and the number of recordsand tape marks processed is listed along with the totalnumber of compare, sequence, temporary, and permanentread and write errors.

� The total elapsed time is the time used for all passes.

� The total bytes transferred, written, and read are also listed.

� If the�� parameter was specified, the number ofcontrol units detected (��) functions for read andwrite temporary, erase gap, and read and write transienterrors are listed.

� If�� is specified, these counts are zero (0).

� If��is active, the counts for��functions arelisted; otherwise they are zero (0).


��

Explanation: No test devices were configured for thisexecution of�� .

Solution: Verify defined devices.

MPSTCPY05 MPSTCPY07


��

Explanation: A��for a portion of memory to be usedfor data comparison failed. Data comparison cannot be done.

Solution: For data comparison, increase the size of the regionor partition where MPST is executing and then re-execute.

��

Explanation: An I/O error occurred during configuration.

This may occur when attempting to overwrite a tape using anon-expanded format device if the tape was previously writtenusing an expanded format device.

Solution: Initialize the tape with a tape mark using anon-expanded format device to correct the problem.

Warning: Initializing the tape with a tape mark will result in allexisting data on the tape being lost.STOP

MPSTCPY08 MPSTCPY11


��

Explanation: Device��was not configured. ��for not configuring:

� ��—The test device DD card is not atype 5 DD card.

� �� —The drive isassigned to another path.

� ��—A test sequence with a write pass wasspecified but the cartridge is file protected. No testing canbe done on this device.

� ��—An I/O error occurred during configuration.The error was described in message��.

� ��—No device has beendefined for this DD name.

� ��—��is activeand only �� or �� are allowed.

� ��—An open for the device failed.

� �� —Device characteristics readdo not match the DD type specified.

� ��—Unable to get sense data from the device.

� ��—The test device DD carddoes not define a cartridge device.

Solution: Verify that the test devices are correctly defined,online and available.

��

Explanation: The number of passes specified by the��

parameter has been completed for device��at address��with volume serial number��. Testing hasterminated on that device but continues on other devices.


MPSTCPY12 MPSTCPY20


��

Explanation: ��has detected that a��commandwas entered at the operator’s console. Testing on test device��at address��with volume serial number��hasbeen stopped.


��

Explanation: Testing on test device��at address��with volume serial number��has been terminated due toa permanent error.


��

Explanation: ��commands issued to configure the devicewere rejected.

Solution: Verify that the device has the current level ofmicrocode.

��

Explanation: The tape comparison passed (OK) or failed andthe data � �� is one of the following:

� ��Byte Record number�

� Tape Mark number�

� 2nd Tape Mark number�


MPSTCPY21 MPSTCPY23


��

Explanation: ��is active and the data �� is:

� ��Byte Record number��

� Tape Mark number��

� 2nd Tape Mark number��


��

Explanation: ��is active and the data �� is:

� ��Byte Record number��

� Tape Mark number��

� 2nd Tape Mark number��


��

Explanation: ��, ��, or �� are active and thedata has been detected.

Solution: Respond to the message:

� Respond� ��to not copy data to output.

� Respond��to copy data to output.

� Respond��to copy data to output and to end theconfirmation operation.

MPSTCPY24 MPSTCPY26


��

Explanation: ��was entered for the confirm response and�� is being skipped. �� is one of the following:

� 2nd Tape Mark

� Tape Mark

� Record


��

Explanation: Skipping is active and copy has not yet started.


� Respond��to not start copy.

� Respond��to start copy.

��

Explanation: An error with ERPA code �� detected.


� Respond��to not skip the error. ��ends with anerror.

� Respond��to skip the error and continue.

� Respond� ��to skip the error and try to Forward SpaceBlock. Depending on the error, this response may or maynot work.

MPSTCPY27 MPSTCPY30


��

Explanation: ��or��was entered for the skip ERPAmessage. �� is one of the following:

� Error.

� Err & Fwr Space Block


��

Explanation: ��is active and the input cartridge tapehas a standard label.


� Respond��!�to not copy the label.

� Respond�� "�to copy the label.

��

Explanation: The��parameter was entered and allcopy functions have been disabled. Only compare operationswill run.


��

Explanation: The physical end of tape was detected on��.

Solution: If��is the output tape, use a longer tape foroutput or enable ICRC on the output tape. Rerun �� .

If��is the input tape, no action is required.

MPSTCPY31 MPSTCPY40


��

Explanation: Incorrect status was received for an I/O operationto device��at address��during a��pass. Theactual status received was��and the command executed was��.


��

Explanation: An open for test device��at address��failed after the cartridge volumes were exchanged. Testing onthe device terminates.


��

Explanation: The actual data read from a record did not matchthe expected data for that record.


��

Explanation: A read forward pass has started for device��

at address��. The cartridge was written in ICRC format andthe drive is not capable of ICRC.

Solution: Move the cartridge to a device that is ICRC capable.

MPSTCPY41 MPSTCPY42


��

��

��

��

��

Explanation: A write pass has been completed for device��at address��with volume serial number��.The summary report for the write pass is contained within thismessage.

If��is active, the counts for��functions are listed;otherwise, they are zero.


��

Explanation: The summary information for all passes for testdevice��and tape volume serial number��is notbeing kept.


MPSTCPY43 MPSTCPY43


��

��

��

��

��

Explanation: A read forward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read forward pass iscontained within this message.

If��is active, the counts for��functions are listed;otherwise, they are all zero.


MPSTCPY44 MPSTCPY45


��

��

��

��

Explanation: A read backward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read backward pass iscontained within this message.


��

Explanation: A read backward pass has started for device��at address��. The cartridge was written in ICRCformat and the drive is not capable of ICRC.


MPSTCPY50 MPSTCPY50


��

Explanation: A temporary error was detected and the controlunit is in forced logging mode on test device��at address�� with volume serial number�� mounted.

� �� —The record number of the record on whichthe error occurred.

� ��—The number of bytes transferred at thetime of the error.

� ��—The number of times the operation hasbeen retried.

� ��—The channel command being executed.

� ��—The SIO condition code.

� ��—The unit and channel status for CSW.

� ��—The CPU ID of the CPU on which the erroroccurred.

� ��—The actual channel path on which the erroroccurred.

� � ��—The sense bytes.


MPSTCPY51 MPSTCPY51


��

��

Explanation: A temporary error has occurred on test device��at address��with volume serial number�� at��

� ��—The record number of the record on whichthe error occurred.


� � �� —The number of times the operation hasbeen retried.


� �� —The SIO condition code.




� ��—The sense bytes.


MPSTCPY52 MPSTCPY52


��

��

Explanation: A permanent error has occurred on test device�� at address��with volume serial number��.� �� indicates the date and time the erroroccurred. ��indicates an error condition of either ��or��.


� �� —The number of bytes transferred at thetime of the error.

� �� —The number of times the operation hasbeen retried.

� �� —The channel command being executed.



� � ��—The CPU ID of the CPU on which the erroroccurred.



MPSTCPY54 MPSTCPY54


� ��is a message describing the error. Somepossible messages and their meanings are:

� ��—The channel status byte ofthe CSW indicated a channel-type error.

� ��—The event control block (ECB) completioncode was not 7F (no error) or 41 (permanent error).Any other ECB code is a fatal error.

� ��—The error was not a datacheck or an overrun. Data checks and overruns areretried. All other errors are considered permanent.

� �� —Read error recovery failedto recover from a temporary read error. The error isnow a permanent error.

� �� —Write error recoveryfailed to recover from a temporary write error. Theerror is now a permanent error.

� �� —The error occurredduring read error recovery. �� is the commandwhich failed during retry.

� ��—The failing CCW could notbe determined and no recovery action could be taken.

� �� —The error occurredduring write error recovery. �� is the commandwhich failed during retry.


��

Explanation: The��command issued to device��at address��with volume serial number��failed.


MPSTCPY55 MPSTCPY58


��

Explanation: An error occurred on device��at address��with volume serial number��. The ERPA code of��is unsupported.

Solution: Notify CS Software Support of this message and givethem the sense data.

��

Explanation: The buffered log overflowed for device��ataddress��with volume serial number��. The logcounters have been added to the statistics.


��

Explanation: The buffered log data is read at the end of eachpass for device��at address��with volume serialnumber��. The log counters have been added to thestatistics.


��

Explanation: A read buffered log CCW was issued to obtainthe current buffered log for device��at address��withvolume serial number��. The CCW failed with an SIOcondition code of��and��of�� .


MPSTCPY59 MPSTCPY62


��

Explanation: A unit check was posted due to end of data beingdetected on the cartridge tape. This is an excepted error. Thetype of pass (��) is��for a write pass,��for a readforward pass, or��for a read backward pass.


��

Explanation: A pass has been started on test device��ataddress��with volume serial number�� . The type ofpass (��) is��for a read forward pass,��for a readbackward pass, or��for a write pass.


��

Explanation: A pass has ended on test device��ataddress��with volume serial number�� . The type ofpass (��) is��for a read forward pass,��for a readbackward pass, or��for a write pass.

The start and end date and times, as well as the elapsed time forthis pass, are listed.


MPSTCPY63 MPSTCPY91


�� !��% � ""!�� "� �� #��% �� #��

Explanation: This message always follows message�� .


�� !��% � ""!��!��!��"��!��!��!%��#��!��$��!

Explanation: A cartridge tape written in 3480–2 XF format ismounted on device��at address��and the device doesnot support 3480–2 XF format.


�� !��%�� !�� !��%��!��""!��!��%� ��&'��

Explanation: Data on output device��will be destroyedby�� .


� Enter�%� �to continue�� . The data currently onthe output tape will be destroyed when the data on theinput tape is copied to the output tape.

� Enter��to drop the output device. The data currently onthe output tape will not be destroyed nor will theinformation on the input tape be copied to the output tape.

�� !��%� ��!��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the��command for the�� function.

Solution: Re-enter the��command using the correctparameter.

MPSTCPY96 MPSTCPY98


��

Explanation: The��command��was issued to�� . The valid��commands for�� followthis message.


��

Explanation: The��is not supported by the�� function.


��

Explanation: This message is issued in response to a��

��command requesting the current value of��.


47 Chapter 6. MPSTDEF

Chapter 6. MPSTDEF

DEFINE Messages



The following messages are issued for��:

MPSTDEF00 MPSTDEF05


��

Explanation: The��function is executing.


��



��

Explanation: A required parameter for the��functionwas not specified.

Solution: Reissue the��function with the requiredparameters.

��

Explanation: This DD name��has already been defined.


��

Explanation: This device address �� has already beendefined.


��

Explanation: This device��is not supported by the��function.


MPSTDEF06 MPSTDEF12


��

Explanation: The type��DD card specified is invalid for thisdevice��.

Solution: Correct the DD card type.

��

Explanation: The device at address��is not defined to theoperating system.

Solution: ��the device to the current device definitions.

��

Explanation: A type 3 or 4 DD card was specified and the dataset name does not match type 3 or 4 patterns.


��

Explanation: The device at address��failed to open.


��

Explanation: Device��could not be allocated, ��are:

� �� —The��function adds offline/unassigned devices to the currentdevice definitions.

� �� —The device is offlinebut it is in use by another program that allocates offlinedevices.

� � ��—An attempt to assign the device failed.


MPSTDEF13 MPSTDEF18


��

Explanation: An attempt to obtain storage for a Data ExtentBlock (DEB) failed.


��

Explanation: The maximum number of devices (eight) havebeen defined.


��

Explanation: DD name��has been defined for the deviceat address��for a type��DD card.


��

��

Explanation: This message lists the devices currently definedby the��function.

� ��is the device’s DD name.

� ��is the device address.

� ��is the DD card type.


MPSTDEF55 MPSTDEF58


��

Explanation: The��function requires confirmation thatdevice��can be initialized.

Warning: If you respond��(yes), all data currently on thisdevice will be destroyed. Refer to message��.


� ��to continue device initialization.

� ��to terminate.

��

Explanation: Device��must be varied offline to all othersystems.

Solution: Vary device��offline. Once the device has beenvaried offline, enter any character from the operator console tocontinue��function execution.

��

Explanation: The��function requires confirmation thatthe data on the volume mounted on device��can bedestroyed.


� ��if the data can be destroyed.

� ��if the data cannot be destroyed.

STOP

MPSTDEF59 MPSTDEF99


��

Explanation: The��parameter was specified and noconfirmation for initialization or data destruction will be, or was,requested.


��

Explanation: Write to offline DASD is not yet allowed. Thisis a future enhancement.

Solution: DASD devices must be online.

53 Chapter 7. MPSTGSA

Chapter 7. MPSTGSA

Generate Stand-alone Programs (GENSAPGM) Messages



The following messages are issued for the Generate Stand-alonePrograms Function:

MPSTGSA00 MPSTGSA06


��

Explanation: The �� (Generate Stand-Alone Programs)function of MPST is executing.


��

Explanation: The parameter (��) is either coded incorrectlyof is invalid for the �� function.


��

Explanation: An MPSTSAE IPL��is being generated.��can be��, ��, or ��.


��

Explanation: An open for file��was unsuccessful.

Solution: Check the job EXECs. Verify that the referenced datasets exist.

��

Explanation: Either IPL text (other than MPSTSAE IPL text)or user volume labels exist on the MPSTSAE IPL disk volume.The �� function cannot replace non-MPSTSAE IPL text.MPSTSAE IPL text will not be written to the volume.

Solution: Obtain a different disk volume.

MPSTGSA07 MPSTGSA12


��

Explanation: A permanent error has occurred. The errorindicated in messages�� and�� could notbe successfully retried.

Solution: Obtain different input and output devices.

��

Explanation: The �� function completed successfullyand an MPSTSAE IPL tape, disk or minidisk was created.


��

Explanation: The �� function did not completesuccessfully. No MPSTSAE IPL tape, disk or minidisk wascreated. A prior message should indicate why the function wasunsuccessful.

Solution: Check� ��file, correct the problem andrerun the �� function.

��

Explanation: The�� parameter specified by thedefined device is not a 3330–1, 3330–11, 3350, 3375, 3380 or3390 type device.

Solution: Obtain correct disk type and rerun the ��

function.

MPSTGSA13 MPSTGSA14


�� or��

Explanation: Either a default control card set has just beencreated or the control card set contains no cards.


��

Explanation: The default control card set just created had aninvalid format.

Solution: Correct the control card set format.

MPSTGSA15 MPSTGSA15


�� or��

Explanation: A write to the IPL minidisk, at device address4FE, failed.

� ��—the last seek address.

� ��—the last Search ID Equal argument.

� ��—the count field of the record that could not bewritten.

� ��—the start block.

� ��—the number of blocks.

Solution: Check the following:

� When ��=� and �=��, device 4FE is not attached.Ensure that the device at address 4FE is defined and retry��.

� When ��=� and �=��, device 4FE is busy or has aninterrupt pending. Retry ��.

� When ��=� and �=��, unit status contained unitexception. Report this error to CSE Software Support.

� When ��=� and �=��, channel status contained incorrectlength. Report this error to CSE Software Support.

� When ��=� and �=��, a permanent I/O error occurred oran unsupported device was specified. ��is sense bytes0 and 1.

If the sense data is zero or it indicates a programmingproblem (such as command reject or no record found),report the error to CSE Software Support.

If the sense data indicates a device error (such as a datacheck or an equipment check), retry ��.

MPSTGSA16 MPSTGSA19


��

Explanation: The input data set specified by the �� DDcard or �� does not contain valid input for MPST�� or the input data is for the wrong version of MPST.

Solution: Check the following:

� Check the �� DD card or ��.

� Verify that the correct tape is mounted.

� Increase the number of cylinders on the 4FE device andretry ��.

�� or��

Explanation: Either an active or alternate control card set hasjust been created or the control card set contains no cards.


�� or��

Explanation: Either a default device definition card set has justbeen created or the device definition card set contains no cards.


��

Explanation: The default device data set just created had aninvalid format.

Solution: Correct the device definition format and rerun��.

MPSTGSA20 MPSTGSA21


�� or��

Explanation: Either a general help card set has just beencreated or the general help card set contains no cards.


�� or��

Explanation: Either a StorageTekFRIEND help card set hasjust been created or the StorageTekFRIEND help card setcontains no cards.


61 Chapter 8. MPSTINT

Chapter 8. MPSTINT

Attention Interrupt Messages



The following messages are issued for Attention Interrupt:

MPSTINT20 MPSTINT40


��

Explanation: MPST device �� is running under MVS/OSand is an attention interrupt type device. The ��

�� has no empty slots to support this device.

Solution: None required

��

Explanation: No path was found for device ��.

Solution: To continue, vary a path �� for device �� and reply�. To cancel, reply .

��

Explanation: The current test device has been determined to bea VIO (virtual input output) device and is not supported byStorageTek MPST.


63 Chapter 9. MPSTLEX

Chapter 9. MPSTLEX

Library Storage Module Exerciser (LSMEXER) Messages



The following messages are issued for the Library StorageModule (LSM) Exerciser:

MPSTLEX00 MPSTLEX02


��

Explanation: The library exerciser��has started.


��



��

Explanation: The cartridge tape drive��at address��with volume serial number �� configured without error.


MPSTLEX03 MPSTLEX03


��

��

Explanation: The��for this execution of��isprinted. The number of passes executed and the number ofrecords and tape marks processed is listed along with the totalnumber of compare, sequence, and temporary and permanentread and write errors. The total number of bytes transferred andthe number of bytes written and read is also listed.


MPSTLEX04 MPSTLEX07


��

Explanation: The� ��parameter (��) is invalid.


��

Explanation: A��for a portion of memory to be usedfor data comparison failed.

Solution: Increase the size of the region or partition that MPSTis executing in and re-execute MPST.

��

Explanation: An attempt to��more than the maximumnumber of cartridge tape drives to��failed. Message� �� displays the failing drives.

Solution: Reduce the number of cartridge tape drives beingdefined. Up to a maximum of sixty-four drives can be defined.

��

Explanation: An error occurred on device��whileprocessing command ��. Message � �� follows thismessage.


MPSTLEX08 MPSTLEX09


��

Explanation: Device��at address��was notconfigured. ��for not configuring:

� ��—The device wasassigned to another path by the HOST CPU.

� � ��—A test sequence with a write pass wasspecified but the cartridge is file protected. No testing willbe done on this device.

� ��—An I/O error occurred during configuration.The error is described in message �� .

� �� —An open for the device failed. Verify thatthe DD card is coded correctly.

� �� —The cartridge volumemounted on this device contains a valid OS tape label.Testing will not be done on this device.

� ��—The test device DD cardfor this DD name does not define a cartridge device.Verify that the DD card is correctly coded.


��

Explanation: The maximum number of��or��cell locations was exceeded and the�� terminates.

Solution: Reduce the number of��or��entries.Up to 200 each is allowed.

MPSTLEX10 MPSTLEX13


��

Explanation: The��specified for the�� parameterwas invalid.

Solution: ��must be between 1 and 9999 minutes.

��

Explanation: All passes specified for device��at drive��with volume serial number��have completed.Testing has terminated on that device for the cartridge withvolume serial number��.


��

Explanation: ��has detected that a��commandwas entered at the operator’s console. Testing on test device��at address��with volume serial number��hasbeen stopped.


��



MPSTLEX14 MPSTLEX18


��

Explanation: The��parameter was entered and nomemory was available for the drive data buffer. The mountsrequested will not be performed.

Solution: If intervention is required, correct the problem andrestart the program.

��

Explanation: The LSM id (��) for the��parameter wasinvalid.

Solution: The LSM id must be between��and��.

��

Explanation: No CAP panel was found for LSM��.

Solution: This error indicates either an LMU configurationerror or a hardware error.

��

Explanation: This message is issued at the end of��

and indicates the number of times the cleaning cartridge wasused.

Solution: Mark the cleaning cartridges indicating the number ofpasses.

MPSTLEX19 MPSTLEX20


��

Explanation: Dynamic device definition has failed on drive��.

Solution: Check availability of device and retry.

��

Explanation: The message identifies the tape drive that createdthe cartridge being read and the tape drive reading the cartridge.� ��is the volume serial number of the cartridge.

The drive reading the cartridge is identified by:

� ��—The tape drive’s address.

� ��—The DD name.

The drive that created the cartridge is identified by:

� ��—The tape drive’s address.

� ��—The DD name.

� ��—The control unit’s serial number.

� ��—The tape drive’s physical address.

� ��—The tape drive’s logical address.

If the current pass is a read forward, ��and��identifywhen the write pass started on the creating tape drive.

If the current pass is a read backward, ��and��identifywhen the write pass ended on the creating tape drive.


MPSTLEX21 MPSTLEX24


��

Explanation: Incorrect�� was received for an I/Ooperation for device��at drive��during a��.


��

Explanation: A read forward pass is being executed on testdevice��at address��with volume serial number��. The BOT label on the cartridge is not a BOT label that��would write on a test volume. Testing on the deviceterminates.


��

Explanation: A data record was expected but an EOT label wasread on a read forward pass of the cartridge on test device��

at address��with volume serial number��. (The tapemark separating the data records and the EOT record wasmissed.) Testing on the device terminates.


��

Explanation: The cartridge on test device��at address��with volume serial number��mounted is missingthe EOT label that��writes on a test volume. Testingon the device terminates.


MPSTLEX25 MPSTLEX27


��

Explanation: The number of blocks read (��) does notcompare with the number of blocks written ( ��) as listed inthe EOT label for the cartridge on test device��at address��with volume serial number��. This is the equivalentof an��. Testing on the device continues.


��

Explanation: A read backward pass is being executed on thecartridge on test device��at address��with volumeserial number��mounted. The first record read was notthe EOT label, as expected; or the EOT record was not foundafter skipping a maximum of three tape marks. Testing on thedevice terminates.


��

Explanation: A read backward pass is being executed on testdevice��at address��with volume serial number��mounted. The EOT label was read successfully but thenext record on the cartridge was not the tape mark preceding theEOT record. Testing on the device terminates.


MPSTLEX28 MPSTLEX30


��

Explanation: A read backward pass is being executed on testdevice��at address��with volume serial number��mounted. A data record was expected but a BOT labelwas read. (The tape mark separating the data records and theBOT record was missed.)


��

Explanation: The cartridge on test device��at address��with volume serial number��mounted is missingthe BOT label that��would write on a test volume.Testing on the device terminates.


��

Explanation: The last pass executed on test device��ataddress��with volume serial number��mounted wasnot a write pass or a read forward pass. A read backward passcannot be executed.

The read backward pass is skipped and testing on the devicecontinues.

Solution: Modify the��parameter.

MPSTLEX31 MPSTLEX35


��

Explanation: A record was read on test device��ataddress��with volume serial number� ��mounted thatwas not the length expected. ��expected record number��to have��bytes but��bytes were received.


��

Explanation: At initialization more cartridges were found thancan fit into the CAP.


��

Explanation: The�� parameter entered (��) isinvalid.


��

Explanation: A sequence error occurred on test device��

at address��with volume serial number� ��mounted. ��expected��but received��.


MPSTLEX36 MPSTLEX39


��

Explanation: The record (��) read on test device��ataddress��with volume serial number�� had incorrectid fields. The first four bytes��did not match the last fourbytes��.


��

Explanation: A short record was read on test device��ataddress��with volume serial number�� mounted. Adump of the record follows.


��


at address��with volume serial number�� mounted. ��expected record��but read record��


��

Explanation: The current compare record for device��ataddress��with volume serial number�� is displayed.


MPSTLEX41 MPSTLEX43


��

��

Explanation: A write pass has been completed for device��at address��with volume serial number��.The summary report for the write pass follows this message.


��

��

Explanation: A read forward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read forward pass followsthis message.


MPSTLEX44 MPSTLEX49


��

��

Explanation: A read backward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read backward pass followsthis message.


��


at address��. The cartridge��was written in ICRCformat and the drive is not ICRC capable.


��

Explanation: Device��has been defined to to the��function using the�� parameter, but was notdefined to MPST. I/O will not be performed on this device.

Solution: If you want to perform I/O on this device, the devicemust defined.

MPSTLEX51 MPSTLEX51


��

Explanation: A permanent error has occurred on test device��at address��with volume serial number�� mounted. Testing on the device terminates.






� ��—The unit and channel status for CCW.




� ��—A message describing the error. Somepossible messages and their meanings are:


� ��—The event control block (ECB)completion code was not 7F (no error) or 41(permanent error). Any other ECB code is a fatalerror.

� �� —The equipment check bit is setin the channel status.

MPSTLEX53 MPSTLEX54



� ��—Read error recovery failedto recover from a temporary read error. The error isnow a permanent error.

� ��—Write error recoveryfailed to recover from a temporary write error. Theerror is now a permanent error.



��

Explanation: Following a sequence error,��attemptsto get back in sync by resetting the record expected based uponthe record just processed. If the record read is more than four offof the record expected, the error is too great to correct in thismanner.


��

Explanation: The�� command issued to device��at address��with volume serial number��mounted failed with��.


MPSTLEX55 MPSTLEX61


��

Explanation: An error occurred on device��at address��with volume serial number��. The ERPA code of��is unsupported.


��

Explanation: The buffered log overflowed for device��ataddress��with volume serial number��. The logcounters have been added to the statistics.


��

Explanation: ��is� ��for a read forward pass,� ��for aread backward pass, or�� for a write pass. This messageprints if�� is active.


��

Explanation: A pass has been started on test device��ataddress��with volume serial number��. The type ofpass ( ��) is� ��for a read forward pass,� ��for a readbackward pass, or�� for a write pass. ��followsthis message.


MPSTLEX62 MPSTLEX68


��

Explanation: A pass has ended on test device��ataddress��with volume serial number��. The type ofpass (�� ) is�� for a read forward pass,��for a readbackward pass, or��for a write pass.


��

Explanation: This message always follows message��.


��

Explanation: The cleaning cartridge is being cycled.


��

Explanation: This message prints when the status (��) ofthe cartridges is requested by the��parameter. Theoriginal CAP location (��) and the current location(��) are also displayed as part of this message.


MPSTLEX69 MPSTLEX72


��

Explanation: This message prints when a CAP cycle is beingperformed with��in effect.


��

Explanation: The move count was equal to the mount count,enabling a mount transaction, but no drives were available. Thismessage prints if��is active.


��

Explanation: A mount transaction was issued and failed fordrive��volume serial number��at��:��:��on��/��/��for cartridge�� , move number�� .


��

Explanation: The move for cartridge�� was completed fromLSM location��to��. This message prints if��is active.


MPSTLEX73 MPSTLEX76


��

Explanation: The mount for cartridge��was completed ondrive��at LSM location��from��. Thismessage prints if� ��is active.


��

Explanation: The��failed for cartridge �� from LSMlocation��to��.


��

Explanation: The number of errors has exceeded the limit(��) of errors (�� ). The exercise terminates.


��

Explanation: The number of errors has exceeded the limit(��) of errors (�� ) for cartridge tape drive��. Thisdrive will no longer be used.


MPSTLEX77 MPSTLEX80


��

Explanation: The number of errors has exceeded the limit oferrors (��) for cartridge number��. This cartridge willno longer be used.


��

Explanation: A fatal error has occurred on drive ��. Thisdrive will no longer be used.

Solution: If intervention is required, correct the condition andrestart the program.

��

Explanation: A fatal error has occurred on cartridge ��. Thiscartridge will no longer be used.


��

Explanation: No cartridges were available for movement.Either no cartridges were placed into the CAP or all cartridgeswere removed from use due to errors. ��terminates.

Solution: If intervention is required, correct the problem andrestart the program.

MPSTLEX81 MPSTLEX83


��

Explanation: This message prints if��is active and move��using cartridge��has started.


��

Explanation: �� has ended.


��

Explanation: The status for LSM �� is printed. Either�� has ended or the time specified by the��

parameter has expired.


MPSTLEX84 MPSTLEX87


��!� ��

Explanation: ��has ended and cleanup is moving thecartridges back to their original starting positions in the CAP.


��!� ��

Explanation: The CAP has completed its audit and the 20cartridge volsers in the CAP are� ��if a label was read,�� if cartridge��had no label, or�� if nocartridge was found in location��.


��!� ��"��!��

Explanation: This message prints after all LSM summarymessages have been printed. The status reflects the timescomputed by the host CPU including any overhead time due tohost activity.


��! ��"��

Explanation: LSM��went not ready at��:��:��/��/��and will no longer be used.


MPSTLEX88 MPSTLEX92


��

Explanation: �� is cycling the cartridge back to theCAP and then moving the next CAP cartridge to be tested. Thisoccurs if��was specified.


��



��

Explanation: This message lists the number of cartridgesinserted into all possible LSM cells whenever the��

parameter is specified.


��

Explanation: Parameter (��) is either coded incorrectly or isinvalid for the��command for the�� function.

Solution: Enter the correct��parameter.

��

Explanation: No LSMs were found available for generating arandom cell location. The current cartridge will not be moved,the consecutive error counter will increment, and the nextcartridge will be tried.


MPSTLEX93 MPSTLEX97


�� !��

Explanation: The panel� ��passed by the LSM status datawas invalid.


�� !��

Explanation: This message prints if��is active and therandom locations generated were not available after 16 attempts.If�� is enabled, a location in another LSM will be tried.If�� is not enabled, this cartridge will be skipped forthis move.


��

Explanation: The mount and passthru check counts were thesame. One of the counts was changed to�� .


��

Explanation: The passthru check count was an even multipleof the mount check count and has been changed to�� .


�� !��

Explanation: The��parameter (��) is not supportedby the��function.


MPSTLEX98 MPSTLEX99


��

Explanation: This message is issued in response to a� ��



��

Explanation: The following conditions could effect thefunction of�� if:

� ��is run concurrently with the host softwarecomponent (HSC) there is a possibility that the HSC CAPtask will abend if it tries to reserve a CAP already reservedby MPST.

� MPST uses an empty cell just prior to HSC also using thatcell, HSC will try to eject the MPST cartridge.

� The HOSTID used by MPST is also being used by HSC,the LMU will alternate all messages and responsesbetween HSC and MPST.

� ��is run concurrently with LDL diagnostics, aconflict may occur causing LMU errors.

Solution: If the HSC command��is issued for eachHSC HOSTID, the problem with a CAP being reserved isminimized.

Hint: If you want to continue running��, reply��tothis message.

91 Chapter 10. MPSTLIB

Chapter 10. MPSTLIB

Library Mount (LIBMOUNT) Messages



The following messages are issued for Library Mount:

MPSTLIB00 MPSTLIB05


��

Explanation: The��program has been loaded andstarted.


��



��

Explanation: The maximum number of cartridge tape drives orrequests has been exceeded for the parameter (��) beingdecoded.


��

Explanation: The parameter data entered is invalid.

Solution: Enter the correct parameter data.

��

Explanation: The HOST tried to initialize the LMU and failed.The LMU is either not attached, not defined, or failed.

Solution: Issue the��command to determine if the LMUexists.

��

Explanation: An error occurred while executing a transactionwith the LMU.


MPSTLIB06 MPSTLIB10


��

Explanation: The��is being sent to the LMU.This message prints if��is active.


��

Explanation: The��is being resent to the LMU.This message prints if��is active.


��

Explanation: The��was sent to the LMU and no��(acknowledge or response) was received from the LMU in��seconds. The sequence number for the transaction is #� �.


��

Explanation: An error occurred while executing a readfollowing an attention interrupt.


�� !��

Explanation: An interrupt was received from the LMU but the��it presented was not recognized as valid data. Thismessage prints if��is active.


MPSTLIB11 MPSTLIB16


��

Explanation: A message was received from the LMU.


��

Explanation: An interrupt was received from the LMU and theresponse set the error indicator.


��

Explanation: An invalid request was issued to��.

Solution: Enter a valid request.

��

Explanation: An attempt to��a drive failed because nomore drives are allowed.

Solution: Reduce the number of cartridge tape drives beingdefined. Up to a maximum of 64 drives can be defined.

��

Explanation: A�� to��for a cartridge tapedrive at address��failed because the drive was not defined.

Solution: �� !��the drive.

��

Explanation: A�� to��to mount a cartridgeon drive��failed because a cartridge is already mounted onthat drive.

Solution: Mount the cartridge to another drive or issue a��"$!#/��!#�command to the drive.

MPSTLIB17 MPSTLIB22


��

Explanation: An interrupt was received from the LMU, and the�� is invalid.


��

Explanation: The format of the data in the�� received from the LMU is invalid.


��

Explanation: A��to��to dismount acartridge on drive��failed because the drive is not mounted.


��

Explanation: The location��is not a valid drivelocation in the LSM.

Solution: �� a valid location.

��

Explanation: The location��is not a valid celllocation in the LSM.

Solution: Specify a valid location.

��

Explanation: The exchange request between drives��and�� failed.


MPSTLIB23 MPSTLIB28


��

Explanation: The��request between drives��and��failed.


��

Explanation: An attempt to disband either the��or��LMU failed.


��

Explanation: An attempt to�� the cartridge from drive�� back to the last location for that cartridge failed.


��

Explanation: The��data received from the LMUwas in error.


��

Explanation: An error occurred while executing a block��

to the LMU.


��

Explanation: Drive��has been defined.


MPSTLIB29 MPSTLIB32


��

Explanation: This message only prints if��wascalled by controls cards and the status of a cartridge haschanged.


��

Explanation: The drive is unavailable at location��.Possible��are:

� ��

� ��

� ��

� ��

� ��


��

Explanation: LSM status indicates that LSM��is not ready.


��

Explanation: LMU configuration data indicates that LSM��is not configured.


MPSTLIB33 MPSTLIB37


��

Explanation: A� ��command (��or��)issued to LSM��failed.


��

Explanation: A��was issued to a drive at LSM location��and no drive is located there.


��

Explanation: A��was sent to the LMU and isbeing retried.


��

Explanation: A��request issued to drive��failed.


��

Explanation: A cartridge movement (� �) transaction is aboutto be issued but there is no active cartridge at location��.

Solution: Specify an occupied location.

MPSTLIB38 MPSTLIB42


��

Explanation: A��request transaction was issued forcartridge�� at LSM location��and the requestfailed.


��

Explanation: Cartridge�� was successfully moved fromLSM location��to LSM location��. Thismessage prints if��is active.


��

Explanation: The exerciser was trying to put cartridges backinto the CAP. Cartridge �� at LSM location��wasnot entered into the CAP.


��

Explanation: A ��or��command issued toLSM��CAP�� failed.


��

Explanation: A��(audit)�� issued for cells��–��for LSM��failed. The responses received resultingfrom the request is�� for both�� and�� .


MPSTLIB43 MPSTLIB47


�� "�� !��

Explanation: An��or��command issued to LSM�CAP��failed.


��

Explanation: A�� transaction has failedfor��.


�� "�� "��

Explanation: The LSM exerciser has started or ended and thetest cartridges must be inserted into or removed from�the CAPat LSM location�.

Solution: Insert or remove the cartridge.

��

��

��

Explanation: The��audit has ended for LSM�.


�� "��

Explanation: The CAP door has been opened or closed inresponse to an��or��command.


MPSTLIB48 MPSTLIB52


�� "��

Explanation: The cartridge listed in the previously displayederror message was lost or stuck.

Solution: Manually locate the cartridge.

��

Explanation: When cartridge tape drive��was undefinedafter a�� transaction was attempted, drive��wasfound active.


�� !� ��

Explanation: MPST waited for��wait periods fortransaction sequence��to either complete or fail. Thismessage prints if��is active.


��

Explanation: The acknowledgement for transaction sequence��has been lost and a response was detected for thetransaction request. The transaction will be completed as if��

was received.


�� !��

Explanation: CAP��cannot be reserved to HOSTID��because the specified CAP is already reserved to another HOSTid.


MPSTLIB53 MPSTLIB57


��

Explanation: CAP��was successfully reserved to HOSTID��.


��

Explanation: CAP��was successfully released fromHOSTID��.


��

Explanation: A CAP��command from HOSTID��to CAP��failed. The CAP is��to anotherHOSTID.


��

Explanation: A CAP�� command was requested butfailed. The CAP is not reserved to the requesting HOST.


��

Explanation: A CAP�� command was requested butfailed. The CAP is not reserved to the requesting HOST.


MPSTLIB58 MPSTLIB61


��

Explanation: A command was retried��times, but theLMU buffer is full.


�� "��!�� "�� "�� "��

Explanation: The status is listed for LSM��, and the statusfor all configured LSMs will be printed. ��is:

� �� or ��,

� ��, or

� ��.


��

Explanation: This message prints if�� is active. ��is the block message and �� is the first 23characters of the transaction.


��

Explanation: This message prints if�� is active. ��is the block message and �� is the first 23characters of the transaction.


MPSTLIB62 MPSTLIB66


��

Explanation: The volser at cell��had a mismatch for eitherthe first, second, or third pass of a verify request.


��

Explanation: No volser was found at cell location��.


��

Explanation: A CAP cycle is being performed with the��parameter active. CAP��for LSM��is tobe opened and closed as part of the CAP cycle.

Solution: Open and close the CAP door.

��

Explanation: This message prints when a cartridge recoveryhas been issued. �� will be one of the following:

� ��

� ��

� ��

� ��


MPSTLIB70 MPSTLIB73


��

Explanation: This message prints at initialization of��

or��. ��is the level of firmware.


��

Explanation: An open error occurred on LMU��.


��

Explanation: An LMU switch was requested but only oneLMU is configured.


��

Explanation: This message prints at initialization of��

or��.

� ��is the address of the master LMU if dual LMU isrunning, or the address of the LMU if dual LMU is notrunning.

� ��is the address of the standby LMU if dual LMU isrunning.


MPSTLIB74 MPSTLIB77


��

Explanation: A force or auto switch-over request failed withdual-LMU running.

� �� is the standby address.

� �� is the type of switch-over failure thatoccurred.


��

Explanation: This message prints if a functional LMU cannotbe found.


��

Explanation: This message prints if��is active. ��will be one of the following:

� ��

� ��

� � ��


��

Explanation: An LMU join request failed. The ��LMU at address�� failed to join theHOST.


MPSTLIB78 MPSTLIB97


��

Explanation: Communications between the master LMU andthe standby LMU have been re-established. The standby LMUstill failed to join with the HOST.


��

Explanation: An attention interrupt was received from thestandby LMU. This message prints if��is active.


��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the��command for the �� function.

Solution: Enter the command using the correct parameter.

��



��

Explanation: The�� is not supported by the�� function.


MPSTLIB98 MPSTLIB99


��


�� command for the��function and displays thecurrent value for the requested parameter.


��

Explanation: The following conditions could effect thefunction of��:

� If��is run concurrently with the host softwarecomponent (HSC), there is a possibility of causing theHSC CAP task to abend if it tries to reserve a CAP alreadyreserved by MPST.

� If MPST uses an empty cell just prior to HSC also usingthat cell, HSC tries to eject the MPST cartridge.

� Also, if the HOSTID used by MPST is also being used byHSC, the LMU alternates all messages and responsesbetween HSC and MPST.

� If��is run concurrently with LDL diagnostics, aconflict may occur causing LMU errors.

Solution: If the HSC command �� is issued for eachHSC HOSTID, the problem is minimized.


109 Chapter 11. MPSTLOK

Chapter 11. MPSTLOK

Library Look (LIBLOOK) Messages



The following messages are issued for Library Look:

MPSTLOK00 MPSTLOK04


��

Explanation: Th��program has been loaded andstarted.


��



��

Explanation: The parameter (��) is incomplete.

Solution: Enter the complete parameter.

��

Explanation: The configuration for panels �� through �� islisted for LSM ��.


MPSTLOK05 MPSTLOK08


�� #��!�� !�� !��

Explanation: The status of LSM �� is listed.


�� "�� "��

Explanation: The maximum number of panel audit requests(200) has been exceeded.

Solution: Respecify the number of panel audit requests.

�� "�� "��

Explanation: The maximum number of CAP audit requests(200) has been exceeded.

Solution: Respecify the number of CAP audit requests.

�� "�� !�� "��

Explanation: The maximum number of cartridge tape driveaudit requests (200) has been exceeded.

Solution: Respecify the number of cartridge tape drive auditrequests.

MPSTLOK09 MPSTLOK13


��

Explanation: The maximum number of CAP parameters (100),which result in CAP audit requests, has been exceeded.

Solution: Respecify the number of CAP parameters.

��

Explanation: The� ��command was entered by the operator.


�� !"� ��

Explanation: The CAP parameter entered (��) isinvalid for the��.

Solution: Use the��command to enter the correct��parm.

�� !"��

Explanation: The panel list parameters found by the��

function are corrupted.

Solution: Exit MPST and notify CS Software Support. Theprinter output should be retained and given to CS SoftwareSupport.

��

Explanation: The panel number () entered for a 9740 drive isinvalid.

Solution: Respecify the panel number.

MPSTLOK17 MPSTLOK95


��

Explanation: ��tried to load the��functionand failed.

Solution: Exit MPST and notify CS Software Support. Theprinter output should be retained and given to CS SoftwareSupport.

��

Explanation: The audit request has ended. The time to run, thenumber of cells that were actually audited, and the average timeper cell are listed.

Hint: Remember if� ��or� ��was specified, thetotal time and cell count is three times that requested.


��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the command for the��function.


�� "$��'"��

Explanation: The��function is ready to acceptcommands via the�%&!#�(�command. This message isrepeated, after the function processes input parameter, until an��parameter is received.


MPSTLOK96 MPSTLOK98


��

Explanation: The��command�� was issued to��. The valid��commands for��followthis message.


��

Explanation: The��is not supported by the��function.


��


��command for the��function and displays thecurrent value for the requested parameter.


MPSTLOK99 MPSTLOK99


��

Explanation: The following conditions could effect thefunction of��:

� If��is run concurrently with the host softwarecomponent (HSC), there is a possibility of causing theHSC CAP task to abend if it tries to reserve a CAP alreadyreserved by MPST.

� If MPST uses an empty cell just prior to HSC also usingthat cell, HSC tries to eject the MPST cartridge.

� Also, if the HOSTID used by MPST is also being used byHSC, the LMU alternates all messages and responsesbetween HSC and MPST.

� If��is run concurrently with LDL diagnostics, aconflict may occur causing LMU errors.

Solution: If the HSC command �� is issued for eachHSC HOSTID, the problem is minimized.


117 Chapter 12. MPSTMAN

Chapter 12. MPSTMAN

MPST Main Processing (MPSTMAIN) Messages



The following messages are issued for MPST Main Processing:

MPSTMAN02 MPSTMAN06


��

Explanation: This is the last message issued by MPST prior tonormal termination. The highest return code encountered duringexecution was �. This return code (�) is returned to thesystem (calling program).


��

Explanation: The last control card listed has requested anunknown function.

Solution: Correct the control card.

��

��

��

Explanation: The function��started or ended at time��and the return code for the last function was��. Thefunction performed��EXCPs to the test device andenvironmental sense data was received��times. If the testdevice is a 33XX type device, the last��occurrences ofenvironmental sense data are listed.


��

Explanation: The��option is in effect and theMPST online control card editor will be entered at the end of thecurrent control card string.

Solution: ��will remain in effect until��is specified.

MPSTMAN07 MPSTMAN08


��

Explanation: The��option is in effect while a controlcard set is being processed. The current value of��is thenumber of times to repeat the current control card set. Thismessage is issued each time the control card set is repeated.

Solution: Execution ends when the value of��equals zero.

��

Explanation: The following conditions could exist:

� A control card indicated that function parameters werecontinued on the next card, but an end of file occurredwhen MPST attempted to read the next card.

� The last control card contains more than 31 parameters orthe total of all parameter characters exceeds 512.

One of the following messages is displayed:

� ��

� ��

� ��

� ��

��

� ��

��

� ��

� ��

� ��

� ��

� ��

��

Solution: Check for missing commas or missing blank spacesbetween parameters. Parameters must be separated by a commaor by blank spaces.

MPSTMAN10 MPSTMAN15


��

Explanation: The parameter is coded incorrectly or is invalidfor the��function.


��

Explanation: The current settings of the��functionparameters are listed.

Solution: Refer to the appropriate MPST Functions ReferenceManual for an explanation of the listed options

��

Explanation: The requested device or devices are not defined.

Solution: Redefine the requested device or devices.

��

Explanation: The requested Sense ID data for DD name ��

is displayed.


��

Explanation: The requested Read Device Configuration datafor DD name �� is displayed.


��

Explanation: The requested Read Configuration Data for DDname �� is displayed.


MPSTMAN19 MPSTMAN20


��

Explanation: During open the DD card is missing for�� .

Solution: Correct the DD card.

��

Explanation: The��parameter of the��functionwas specified. This message lists the I/O status for an I/Ooperation when it is posted as completed.

� ��—The device address.

� ��—The ECB completion code.

� ��—The SIO condition code, the unitand channel status, and the residual byte count from theCSW.

� ��—Sense bytes 0 and 1.

� ��—The IOB flag bytes.

� ��—The seek address in hex.

� �� —The DASD file mask byte.

� ��—The I/O appendages flag byte.

� ��—The CPU ID on which the operation occurred.If no error occurred, the � will be ��.

� ��—The actual path used for the operation. If noerror occurred, the �� will be ��.

� ��—The sense bytes, if available.

� ��—The command code, flag byte,and the byte count for each CCW in the CCW chain. Theformat of the last CCW executed is ��.


MPSTMAN21 MPSTMAN21


��

Explanation: The��function��parameter wasspecified. MPST lists the results of a successful open request.

� ��—The DD name that was opened.

� ��—The device address

� ��—The volume serial number mounted on thedevice.

� ��—The device type.

� ��—The hexadecimal address of the cylinder.head atthe start of the first data set extent if a DASD device.

� ��—The hexadecimal address of the cylinder.head atthe end of the first data set extent is a DASD device.

� ��—The number of tracks in the data set extent.


MPSTMAN22 MPSTMAN25


��

Explanation: The��function��parameter wasspecified. MPST indicates that a close request for device��

was successful.


��

Explanation: Environmental data was detected for deviceaddress ��.


��

Explanation: The missing interrupt handler (��) has posted anMPST I/O operation completed. This message is normallyfollowed by an error message from the MPST function that isexecuting on device��.

Solution: Determine why the device lost the interrupt.

��

Explanation: Environmental data was detected for device��. The sense��contain the environmental data.


MPSTMAN26 MPSTMAN26


��

Explanation: The device at address��has caused a SIMrecord to be logged.

� ��and��—The data and time of theSIM.

� �� —The DASD volser.

� ��—The device code.

� �� —The device type and modelnumber.

� �� —The controller type and modelnumber.

� ��—The error code.

� ��—The severity code,SIM type, and an indicator that the SIM is repeated.

� �� —The manufacturer andplant ID.

� �� —The plant serial number.

� ��—The SIM ID.

� ��—The reference codes.

� ��—The ServiceTek sequence code.

� ��—The message code.

� ��—The message modifiers.

� ��—The raw sense byte.


MPSTMAN27 MPSTMAN42


��

Explanation: SMS VIO (Virtual Input Output) devices areconsidered to be non-StorageTek devices and are not supported.

Solution: Special ACS Routines must be provided by thecustomer to successfully run MPST/MVS in an SMS controlledinstallation.

��

Explanation: MPST has detected that a��command wasentered at the operator’s console. MPST terminates at the nextavailable stop point.


��

Explanation: The control card file contained no control cards.

Solution: Verify that the SYSIN DD statement is present,correctly coded, and followed by one or more MPST functioncontrol cards.

��

Explanation: The return code from the��was greaterthan zero. This condition indicates an error that does not allowMPST to perform properly and MPST terminates immediately.Previous errors should have indicated the errors that resulted inthe return code being greater than zero.

Solution: Correct the errors and re-execute MPST.

MPSTMAN43 MPSTMAN70


��

Explanation: The return code from the last function executedwas greater than the return code allowed by the��

paramete. MPST terminates immediately.


��

Explanation: A�� command was entered at the operator’sconsole and MPST operation terminates. All MPST controlcards may not have been processed.


��

Explanation: MPST requires a response.

Solution: Enter the��command to stop the execution ofMPST or enter null to continue MPST execution.

��

Explanation: The response to message� ��wasneither�� nor null.

Solution: Enter��to stop the execution of MPST or null tocontinue MPST execution.

��

Explanation: The��command��was issued to� ��. The valid��commands for� ��followthis message.


MPSTMAN71 MPSTMAN99


��

Explanation: The� ��is not supported by the��function.

Solution: Enter the correct� ��parameter.

��

Explanation: The� ��parameter��for the��function has been rejected. The control cards to be repeatedmust have been previously loaded into the control card buffer.

Solution: Re-run the operation with the correct control cardsource.

��

Explanation: The��function��parameter wasspecified and trace point��was encountered.


129 Chapter 13. MPSTRLB

Chapter 13. MPSTRLB

Random Locate Block (RLB) Messages



The following messages are issued for Random Locate Block:

MPSTRLB00 MPSTRLB03


��



��



��

Explanation: Device��at address��with volumeserial number��configured without error.


��

MPSTRLB03 MPSTRLB03


��

��

��

��

��

��

��

��

��

��

Explanation: The summary for this execution of��fordevice��at address��with volume serial number��is printed.

� The number of passes executed and the number of recordsand tape marks processed is listed along with the totalnumber of compare, sequence, temporary, and permanentwrite errors.

� The total bytes transferred by write are also listed.

� If the�� parameter was specified, the number ofcontrol units detected (��) functions for writetemporary, erase gap, and write transient errors are listed.



Note: The information in the summary report marked with anasterisk is not always included in this message.


xxxxxxxx

MPSTRLB04 MPSTRLB07


��

Explanation: No test devices were configured for thisexecution of��.


��

Explanation: The��parameter specified a value of lessthan 28 or greater than the maximum size allowed. The��parameter was changed to reflect the correct range for��.

� On MVS either��or the device maximum is themaximum��allowed.

� On the PC�� is the maximum��allowed.

� On VM either��or the device maximum is themaximum��allowed.


��





MPSTRLB08 MPSTRLB08


��


� ��—Thetest device is not defined as the correct DD card type.Correct the DD card type.

� ��—DD card type6 specifies read-only operations. Correct DD card type.



� ��—A��for a20K I/O buffer failed. Increase the size of the region orpartition in which MPST is executing.


� ��—No device has beendefined for this DD name. Verify the device definition.

� ��—An open for the device failed. Verify thedevice definition.

� ��

��—The cartridge volume mounted on this devicecontains a valid OS tape label and is not file protected toprevent an inadvertent write. Testing cannot be done onthis device. With an OS tape label and file protection allwrite pass commands will be changed to table build passcommands.

MPSTRLB09 MPSTRLB12


� ��—The��command has failed morethan 10 times on this device.

� �� —The test device definitiondoes not define a cartridge device. Verify the devicedefinition.

Solution: Verify that the test devices are correctly defined,online, and available.

�� !��

Explanation: � ��parameter detected but UUT��was notdefined. Volume serial number��will be ignored.


�� #��"��

Explanation: If the block size specified by the��parameter is less than 4098, the time to execute��tocompletion may be very long.


��




��

Explanation: ��has detected a��command entered atthe operator’s console. Testing on test device��at address��with volume serial number��has been stopped.


MPSTRLB13 MPSTRLB15


��



��

Explanation: The��parameter requested a larger blocksize than the device can handle. The block size has beenchanged to the correct��for this device.





��

Explanation: The test device��at address��encountered an error in the segment number while performing awrite pass or a table build pass. The segment number wasneither equal to nor one greater than the previously retrievedsegment number.


MPSTRLB16 MPSTRLB17


��

Explanation: The test device��at address�� had asequential locate performed on block identifier ��. Theblock identifier sought (��) should be identical to theblock identifier read (��). If these block identifiers arenot identical, the message��is flagged with trailingasterisks (*).

The block identifier is 4 bytes long.

� The first byte is the segment number.

� The first two bits of the second byte identify the formatmode.

� The last six bits of the second byte and the third and fourthbytes are the logical block number.


��

Explanation: The test device��at address�� had arandom locate performed on block identifier ��. Theblock identifier sought (��) should be identical to theblock identifier read (��). If these block identifiers arenot identical, the message��is flagged with trailingasterisks (*).






MPSTRLB18 MPSTRLB19


��

Explanation: The test device��at address��encountered an error while building a block identifier using arandomly generated logical block number. The randomlygenerated logical block number did not fit within the boundariesof the Block ID Table and the table was corrupted.





Solution: Notify CS Software Support.

��

��

Explanation: This message identifies the tape drive that iscreating the cartridge.

� The drive reading the cartridge is identified by ��,drive address �� and ��.

� The drive creating the cartridge is identified by ��,drive address ��, control unit serial number ��,tape drive physical address ��, and tape drivelogical address ��.

� The time is specified by hour:minute:second (��)and the date is specified by month:day:year (��).They identify when the write pass started.

� ��is the number of records per file.

If this device is a Model 3490E, the characters ’3490E’ willfollow��.


MPSTRLB20 MPSTRLB21


��

Explanation: The test device��at address��encountered an error while performing a block identifier readduring a write pass or a table build pass. Either the logical blocknumber or the segment number was out of sequence. The�� field (� ��) remainsthe same on subsequent messages until a proper sequence isreestablished.





The format mode bits are not used in the calculations made todetermine if the block identifier is in error.


��

Explanation: Incorrect status was received for an I/O operationto device��at address��during a��pass. Theactual status received was��and the command executed was��.


MPSTRLB22 MPSTRLB23


��

Explanation: The test device��at address�� encountered a logical block number of zero in the last entry ofthe Block ID Table during a random locate pass.

The table entry is 8 bytes long.




� The fifth byte is reserved and always contains zeros.

� The sixth, seventh, and eighth bytes are the highest logicalblock number of the segment.


��

Explanation: For each block identifier read during a write passor a table build pass both the test device��and the addressare identified, and the block identifier number read is listed.

The��field (��) is 4 bytes long.




Solution: To stop message�� from being issued, enterthe� ��parameter.

MPSTRLB24 MPSTRLB26


��

Explanation: The test device��at address��completed a write pass or a table build pass. The last blockidentifier (��) resulting from this pass is entered into theBlock ID Table.

If the write pass or the table build pass was successful, this�� number should match the block identifier in message��.

Note: If the completed table build pass was performed on a tapepreviously created by a write pass, the��number is oneless than the block identifier number displayed in the messageaccompanying the initial write pass.






��

Explanation: The test device��at address��encountered a block identifier of zero when a Read Block IDwas performed.


��

Explanation: The test device��at address��completed a write pass or a table build pass. ��was thelast block identifier retrieved from the tape.


xxxxxxxx

MPSTRLB28 MPSTRLB41


�� " �� $��

Explanation: The test device��encountered a deferredunit check during a table build pass. The first four bytes(�� ) of the channel status word (CSW) and the first foursense bytes (�� ) are displayed


�� #��

Explanation: The Block ID Table was filled during a write passor a table build pass and the pass was terminated. Subsequentpasses are executed using the entries in the table which may notinclude all the Block ID’s on the tape.


�� $��"��$��"��"��"��

��$��

� ��"�� "�� "��

� ��"�� "��$�� !�"��$��"��$�� "�� !�"�� #��

MPSTRLB42 MPSTRLB42


��

��

��

��

��

��

��

��

��

��

��



Note: The information in the summary report marked with anasterisk is not always included in this message.


��



xxxxxxxx

MPSTRLB50 MPSTRLB50


��












MPSTRLB51 MPSTRLB51


��

��

Explanation: A temporary error has occurred on test device��at address��with volume serial number�� at�� on ��.











MPSTRLB52 MPSTRLB52


��

��

Explanation: Either a permanent or a degraded error hasoccurred on test device��at address��with volumeserial number�� at �� on ��.











MPSTRLB54 MPSTRLB57


��

Explanation: The��command issued to device��at address��with volume serial number�� failed.


��

Explanation: An error occurred on device��at address��with volume serial number�� . The error recoveryprocedure action (ERPA) code of��is unsupported.

Solution: Gather the sense data and notify CS SoftwareSupport.

��

Explanation: The buffered log overflowed for device��ataddress��with volume serial number�� . The logcounters have been added to the statistics. This message willspecify when the overflow was caused by a dismount.


��

Explanation: The buffered log data is read at the end of eachpass for device��at address��with volume serialnumber�� . The log counters have been added to thestatistics.


MPSTRLB58 MPSTRLB61


��



�� "��

Explanation: A unit check was posted due to end of data beingdetected on the cartridge tape. This is an excepted error.


�� "��!��

Explanation: The control until detected an incorrect blockidentifier sequence on test device��at address��withvolume serial number��mounted. An error recoveryprocedure action (ERPA) code of X’41’ is returned.


��

Explanation: A pass has been started on test device��ataddress��with volume serial number��. The type ofpass ( ��) is��for a table build pass,��for a sequentialread block identifier pass,��for a random locate pass, or��

for a write pass.


MPSTRLB62 MPSTRLB64


��

Explanation: A pass has ended on test device� ��ataddress��with volume serial number�� . The type ofpass (��) is��for a table build pass,��for a sequentialread block identifier pass,��for a random locate pass, or��

for a write pass.


�� !��

Explanation: This message always follows message��.


�� !��

Explanation: A cartridge tape written in 3480–2 XF format ismounted on device� ��at address��and the device doesnot support 3480–2 XF format.


MPSTRLB65 MPSTRLB91


� ��

Explanation: If the��parameter was specified, thismessage is displayed at the conclusion of a write pass or a tablebuild pass. Each message contains two eight byte table entries.Message��is repeated until all table entries have beenlisted.

The table entry is 8 bytes long.




� The fifth byte is reserved and always contains zeros.

� The first two bits of the sixth byte identify the formatmode.

� The last six bits of the sixth byte and the seventh andeighth bytes are the logical block number for the last blockof this segment.


� ��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the� ��command for the��function.

Solution: Re-enter the� ��command using the correctparameter.

MPSTRLB96 MPSTRLB98


��

Explanation: The� ��command��was issued to��. The valid� ��commands for��follow thismessage.


��

Explanation: The� ��is not supported by the��function.


��

Explanation: This message is issued in response to a� ��



151 Chapter 14. MPSTTIP

Chapter 14. MPSTTIP

Tape Independent Protocol Set (TIPS) Messages



The following messages are issued for Tape IndependentProtocol Set:

MPSTTIP00 MPSTTIP06


��



��



��

Explanation: Device��is starting.


��

Explanation: A��command was entered; but no devicesare currently defined.

Solution: Define devices.

��

Explanation: ��is ending operation with the specifieddevice.


��

Explanation: Up to 128 devices can be defined at one time.

Solution: Define fewer drives.

MPSTTIP07 MPSTTIP20


��

Explanation: Command��failed on device��.

Solution: Correct the problem and reissue the command.

��

Explanation: Device��at address��failed. ��specifies why it failed.


��

Explanation: Only 29 commands are allowed per��

operation.

Solution: Delete commands from this operation of��.

��

Explanation: A 15 second timeout has occurred.

Solution: Retry device.

��



��

Explanation: Summary information for the��operationfollows this message header.


MPSTTIP21 MPSTTIP84


��

��

Explanation: This message lists the��commands thatcompleted or failed for each test device.


��

Explanation: The��command did not receive a correct��key reply.

Solution: Verify that the device is��capable.

��

Explanation: ��was unable to allocate the requesteddevice.

Solution: Verify that the device is accessible.

��

Explanation: An error occurred on device��while��was executing.

Solution: Enter��(ignore this device),��(retry this device), or��(cancel operation).

��

Explanation: An error occurred while trying to save thetransferring file.

Solution: Check the JCL or the data set name.

MPSTTIP85 MPSTTIP96


��

Explanation: The size transferred did not match the size in thetape header. This is probably a bad tape.


��

Explanation: Size mismatch or no dump is available.

Solution: Issue a��command and verify availability.Then, reissue the��command.

��

Explanation: The file specified by the��command couldnot be accessed.

Solution: Check the file name, data set name, or JCL.

��

Explanation: The file specified by the��command couldnot be accessed.

Solution: Check the file name, data set name, or JCL.

��



MPSTTIP97 MPSTTIP99


��


command.


��


command.


��

Explanation: This message lists the��commands thatcompleted or failed for the test device.


157 Chapter 15. MPSTTKD

Chapter 15. MPSTTKD

Track Dump (TRKDUMP) Messages



The following messages are issued for Track Dump:

MPSTTKD00 MPSTTKD04


�� !��"��#

Explanation: The� ��function is executed on device��with volume��on a��device.


��

Explanation: A�� macro for an I/O buffer has failed.

Solution: Increase the size of the memory for MPST and rerunthe job.

��

Explanation: An open for the test device failed or the testdevice is not a DASD device.

Solution: Verify that the first test device DD card is codedcorrectly.

�� !��

Explanation: The cylinder or head number specified by the ��parameter is not valid for the current test device.

Solution: Enter the correct cylinder or head number.

��

Explanation: The home address (HA) or record zero (R0)record could not be read, or the number of permanent errorsreading data records exceeded the number specified by the�� parameter. Dumping of that track terminates anddumping of the next track (if specified) begins.


MPSTTKD05 MPSTTKD09


��

Explanation: A permanent error occurred dumping a datarecord. Any data that could be read is printed. Dumping of thatrecord terminates and dumping of the next record begins.


��

Explanation: A permanent error occurred reading a data record.Any data that could be read is printed but may not be the exactdata that was in the record.


��

Explanation: A�� command was accepted by the��

function.


��

Explanation: The��parameter requested is greater thanthe number of tracks remaining on the SA cylinder.

Solution: Reduce the number of tracks requested.

��

Explanation: The��parameter requested is greater thanthe number of tracks remaining on the CE cylinder.

Solution: Reduce the number of tracks to dump.

MPSTTKD10 MPSTTKD14


��



��

Explanation: An error occurred while attempting to read thehome address (HA) record.


��

Explanation: An error occurred while attempting to read recordzero (R0).


��

��

Explanation: An error occurred while attempting to read orsearch for a data record.


��

Explanation: An error occurred while executing a sense (04)command on initial startup.


MPSTTKD15 MPSTTKD19


��

Explanation: An error occurred while attempting to read thecount field of a data record.


��

Explanation: The dump which follows is a space count dumpof the track.


��

Explanation: A space count dump was requested but no datawas transferred by the space count CCW chain.


��

Explanation: An error occurred while executing a space count(0F) and read data (06) command chain.


��

Explanation: The��parameter requested is greater thanthe number of tracks remaining on the volume. Tracks aredumped until end of volume is reach. Then,��

terminates with return code 4

Solution: Reduce the number of tracks requested.

MPSTTKD20 MPSTTKD24


��

Explanation: A read device characteristics command failedwhile trying to initialize the device.

Solution: Retry��. If the problem persists, printeroutput should be retained and given to CS Software Support.

��

Explanation: This is the start of the dump of a track. ��is the track address in hexadecimal and in decimal.


��

Explanation: This is the end of the dump of a track. ��isthe track address in hexadecimal and in decimal.


��

Explanation: This is the dump of a record on a track. The��is the record address in hexadecimal and indecimal.


��

Explanation: The track to be dumped is a defective alternatetrack. Dumping of that track terminates and dumping of thenext track (if specified) begins.


MPSTTKD25 MPSTTKD28


��

Explanation: The track to be dumped is a defective track. Thealternate track assigned to this track will be dumped.


��

Explanation: The track to be dumped is an unassignedalternate track. Dumping of that track terminates and dumpingof the next track (if specified) begins.


��

Explanation: The track to be dumped is an assigned alternatetrack. The dump of that track follows this message.


��

Explanation: The table printed is a summary of the records onthe track being dumped. The cylinder (��), head (�� and��), record number (�� and ��), key field length (�� and ��),and data field length (�� and ��) for each record on thetrack is listed in hexadecimal and decimal.


MPSTTKD29 MPSTTKD33


��

Explanation: The device for��has no valid CE or SAcylinders.


��

Explanation: The��parameter was not specified and the��function terminates. ��.�� is a requiredparameter for��.

Solution: Correct the��control card.

��

Explanation: The record dump was an end-of-file record.


��

Explanation: The record dumped was part of an overflowrecord.


��

Explanation: The number of bytes used on this track up to andincluding this record, but not including home address (HA) andrecord zero (R0), is��.


MPSTTKD34 MPSTTKD44


��

Explanation: The number of bytes read for this track exceedthe track capability of the device.


��

Explanation: The data that follows is the data from the homeaddress (HA) record. The five bytes dumped are the flag byte,the cylinder address (two bytes), and the head address (2 bytes).


��

Explanation: The data that follows is the data from the countfield for the record. The eight bytes dumped are the cylinderaddress (two bytes), the head address (two bytes), the recordnumber (one byte), the key field length (one byte), and the datafield length (two bytes).


��

Explanation: The data that follows is the data from the keyfield for the record.


��

Explanation: The data that follows is the data from the datafield for the record.


MPSTTKD51 MPSTTKD54


��

Explanation: No data was transferred when the record wasread.


��

Explanation: Less than eight bytes were transferred when therecord was read. The complete count field was not transferredand the length of the key and data fields is unknown. Thesefields will not be dumped.


��

Explanation: Exactly eight bytes were transferred when therecord was read (only the count field) but the count fieldindicated that the data field length was greater than zero (not anend of file record).


��

Explanation: The key field length in the count field was greaterthan zero but less than the number of bytes transferred when therecord was read. A dump of the partial key field follows thismessage.


MPSTTKD55 MPSTTKD60


��

Explanation: The data field length in the count field wasgreater than zero but less than the number of bytes transferredwhen the record was read. A dump of the partial data fieldfollows this message.


��

Explanation: When the record was read, more data bytes weretransferred than the total for the key and data field as indicatedin the count field. The extra data bytes follow this message.


��

Explanation: A correctable data check occurred while thisrecord was being read. The uncorrected data is printed for therecord.

Solution: The data at offset �� is in error and should becorrected to ��.

��

Explanation: The record��, requested in the��option,was not found on the specified track.

Solution: Specify��to obtain a summary of therecords on this track.

MPSTTKD91 MPSTTKD96


��

Explanation: The parameter (��) is either coded incorrectlyor invalid for the��command for the� ��function.

Solution: There are no��command parameters for ��.

��

Explanation: The��parameter was specified, butthe device is not defined.

Solution: If the first device defined in the device definition isnot the device to be used, specify the correct address or DDname in the parameter.

��

Explanation: The��parameter specified does nothave a path available.

Solution: Select another device.

��

Explanation: The��parameter specified is notenabled.

Solution: Enable the device and try again.

��

Explanation: The��command�� was issued to ��. There are no��command parameters for ��.


MPSTTKD97 MPSTTKD97


��

Explanation: The�� is not supported by the��function.


171 Chapter 16. MPSTTMC

Chapter 16. MPSTTMC

Tape Monitor and Control (TMC) Messages



The following messages are issued for Tape Monitor andControl:

MPSTTMC00 MPSTTMC04


�� "��"�� #�� "�� "��



��



�� !��

Explanation: The��status for all defined drives is listed.


�� !��

Explanation: A��command was entered; but no devices arecurrently defined.

Solution: Define devices.

�� #��

Explanation: ��is waiting for another��command tobe entered.

Solution: You can enter a��command now.

MPSTTMC05 MPSTTMC09


��

Explanation: The��parameter was entered and�� is the trace point position.


��

Explanation: Too many devices are being defined.

Solution: The maximum number of device definitions is 8.

��

Explanation: Device��encountered an error on the��

command.


��

Explanation: Device��at address��failed toconfigure. ��specifies why it failed.


��

Explanation: Too many commands were entered at one time.

Solution: Enter fewer commands.

MPSTTMC10 MPSTTMC13


��

Explanation: ��has terminated and devices��were leftwith forced logging enabled.

Solution: Disable force logging mode.

��

Explanation: The timer was set to a value other than zero andhas timed out.


��

Explanation: ��called the��function and the calltype failed. ��describes the failure.

Solution: Correct the problem described in the failure ��.

��

Explanation: An attempt was made to request a��

for device��, prior to that device being defined to��.

Solution: � �� device and reissue the command.

MPSTTMC14 MPSTTMC95


�� ! �� "�� !��! ��

Explanation: The message is sent in response to the timervalue being set to zero.


��



��

Explanation: Parameter (��) is either coded incorrectly or isinvalid for the��function.


��

Explanation: When entering the �� command,��must be entered before any other commands.

Solution: Correct the problem.

� If��was entered as a run-time command, using�� , re-enter the commands with��entered first.

� If��was entered in an incorrect position in a controlstatement,��function ends. Correct the control cardand restart��.

MPSTTMC96 MPSTTMC99


��

Explanation: The�� command��was issued to��. The valid�� commands for��follow thismessage.


��



��




��

Explanation: This is an informational message.


177 Chapter 17. MPSTTSC

Chapter 17. MPSTTSC

Tape Scan Messages



The following messages are issued for Tape Scan:

MPSTTSC00 MPSTTSC05


��

Explanation: The��function is executed on device��with volume��on a��device.


��


Solution: Correct the error and restart��.

��

Explanation: A sense command failed to completesuccessfully.


��

Explanation: ��has detected a tape mark condition.


��

Explanation: The only device types supported for��

are 3480 and 3490.


��

Explanation: An open for the test device failed.

Solution: Verify that the first test device DD card is codedcorrectly.

MPSTTSC06 MPSTTSC10


��

Explanation: An error has occurred while trying to read thefirst record on the tape. ��is unable to determine thelabel type. No additional processing of this tape will occur.


��

Explanation: The number of physical blocks counted withinthe data file does not compare to the block count written in thetrailer record. This message applies to standard label (SL) tapesonly.


��

Explanation: An I/O error has occurred while trying to read alabel during a label dump.


��

Explanation: A��command was accepted by the��function and��terminates.


��

Explanation: A permanent error was detected causing��to terminate.

Solution: Determine the cause of the permanent error andrestart��.

MPSTTSC11 MPSTTSC14


��

Explanation: The file ID and the data set name in ��

contains all zeroes. This is usually the result of a program (suchas ��) that rewrites header labels. An all-zero file ID is adummy HDR1 record.

The last operations to the tape were label rewrites.


��

Explanation: The��label dump function has started.


��

Explanation: The file ID (data set name) in HDR1 does notcompare to the next�� ’s file ID.

This condition indicates that this tape was not closed outproperly when it was last used as an output tape. The trailerrecords are old and not associated with the HDR1�records.

Solution: Check the system or console log for any unusualconditions that may have occurred while this tape was beingcreated (such as�� or a��).

��

Explanation: The label dump will continue after skipping theerror record.


MPSTTSC15 MPSTTSC18


�� !��

Explanation: The rewind command has failed.


�� "��

Explanation: The tape has either two tape marks in a row orhas a tape mark followed by a trailer label at the beginning ofthe tape.

This may indicate that while this tape was being created an�� occurred, ��was received, andthe operator made the volume��at load point to satisfy theintervention. (The operator should have used a “dummy” tape tosatisfy any intervention.)

Solution: This volume requires re-initialization before it can beused as an SL tape.

��

Explanation: �� did not detect any problems whileperforming this function.


�� $��#��

Explanation: An error occurred while�� wasattempting to read the first record on the tape.

Solution: Re-initialization or a tape mark may be requiredbefore the volume can be reused.

MPSTTSC19 MPSTTSC22


��

Explanation: This message indicates that data records arebeing skipped (via FSB commands) in order to get to the nexttape mark where the trailer records should reside.

If the tape is not closed out and an old tape mark is not present,unpredictable results can occur after this point.


��

Explanation: The tape was read immediately after detection ofa tape mark and the last tape mark was probably the last validrecord written. This error is caused by “old data” being read.


��

Explanation: A read CCW with a byte count of 80 and no SLIwas executed and resulted in an�� indicatorbeing set. A record other than 80 bytes in length was read whena label record was expected.


��

Explanation: The volume being read starts with two tapemarks. � ��will only process NL tapes until two tapemarks are detected. Testing on this tape terminates.


MPSTTSC23 MPSTTSC28


��

Explanation: The failing record��is reported for file��.


��

Explanation: An 80 byte record with VOL1 as the first fourbytes was detected as the first record at load point.


��

Explanation: If ��is��, a tape markwas the first record detected at load point.

If ��is� � (non-standard label), the tape is determinedto have a non-standard label.


�� "��

Explanation: ��and��will only be executedagainst SL (standard label) tapes.


�� !�� "��

Explanation: The next record following the error record wasnot in sequence indicating “old data” was read. The label dumpwill try to continue after skipping the error record.


MPSTTSC29 MPSTTSC33


�� "��

Explanation: The back space block command failed duringprogram error recovery of a label record.


��

Explanation: No error was detected while reading the recordswithin file��.


�� "� �� "��

Explanation: Since no data was transferred on the read-forwardcommand, the record may have a partial beginning. ��

will attempt a read-backward command at this point.


�� !��

Explanation: ��has positioned the tape for visualexamination after a data check.

Solution: Visually examine the tape for damage.

��

Explanation: The first 80 bytes of data for file��, record��follow this message.


MPSTTSC34 MPSTTSC37


�� !��

Explanation: A forward space file (FSF) command failed whilethe program was trying to position the tape to the next set oflabels.


�� !��

Explanation: A minimum of one byte and up to a maximum of80 bytes of data transferred forward. The error record followsthis message.


��

Explanation: ��has successfully skipped over theerror record.


�� "��

Explanation: ��has determined that the program hadread into “old data”.

This may indicate that when the new data set was created it didnot complete properly and data, from a prior write operation,was left on the tape. The tape is not closed out.


MPSTTSC38 MPSTTSC40


��

Explanation: The volume under test did not complete normallywhen it was last used as an output tape.

This may indicate that while this tape was being created asystem problem occurred and the CPU needed to be IPL’d.

Solution: Check the system and console logs for unusualconditions such as: ��, re-IPL of CPU, or interventions.

��

Explanation: The tape appears to��to havecompleted properly when created, but the tape now has a readerror.

Solution: Check the tape for damage.

� If the tape is damaged, check the last two devices that usedthe tape.

� If the tape is not damaged, check the device used to createthe tape.

Note: If the tape stick is visible, replace the volume.

��

Explanation: The analysis of the first error follows thismessage.


xxxxxxxx

MPSTTSC41 MPSTTSC44


��

Explanation: This message suggest that the label dump outputbe reviewed.

Solution: Review the label dump output.

� SL tapes should have��labels followed by��labels.

� The file ID in��should match the file ID in��or��.

��

Explanation: This messages suggests that�� be re-runwith the��parameter.

Solution: Re-run�� with the��parameter.

��

Explanation: This message suggests that�� be re-runwith the�� parameter.

Solution: Re-run�� with the�� parameter.

��

Explanation: While attempting to read an error record in thebackward direction no data was transferred. This may indicate apartial record at end-of-record.


MPSTTSC45 MPSTTSC49


�� #�� ! �� !��

Explanation: A read backward command of an error recordcaused data transfer. From 1 to 80 bytes are printed.


��

Explanation: The�� function has started.


��

Explanation: If��is��, the firstrecord of this file is a��record.

If�� is ��, the first record of this file is a��record.

If��is��, the first recordof this file is an��or��record.


�� "�� $ ��

Explanation: After skipping over an error record, the nextoperation was either “read a tape mark” or an “error” whilereading the next record.


�� #�� ! ��

Explanation: An incorrect record length was detected. ��expected��and received��.


MPSTTSC50 MPSTTSC56


��

Explanation: The��of blocks counted by��within file��.


��

Explanation: The��should be the number of physicalblocks written in data file��preceding the trailer label at thetime of creation.


��

Explanation: The��of files processed includes all��,��, and��files.


��

Explanation: The forward space block command failed.


��

Explanation: The label dump utility completed successfully.


��

Explanation: The read forward command (02) failed.


MPSTTSC57 MPSTTSC61


��

Explanation: Read forward command (02) failed whileattempting to read a record label.


�� !��

Explanation: ��has finished; the number of filesprocessed (��) includes�� ,�� , and��files.


�� "��!��!�� "��"��

Explanation: The��parameter will readall files and report any errors found. If a second error isdetected, unpredictable results may occur.


��

Explanation: The data following this message is the 17-bytefile ID field of�� .


��

Explanation: The data following this message is the 17-bytefile ID field of��or��.


MPSTTSC62 MPSTTSC67


��

Explanation: The Julian day and year are retrieved from HDR1of the failing data set file. If the system date was properly set byoperations, this should be the date the failing data was created.


��

Explanation: The last record within the data file failed.

This may indicate that a write data check or a write equipmentcheck ��’d the job during the creation phase.

Solution: Check the system and console logs for errors.

��

Explanation: This messages suggests that the system andconsole logs be checked for any unusual conditions.


��

Explanation: An error was detected reading a��label.


��

Explanation: The next I/O error will be the second sequentialerror in a row.


MPSTTSC68 MPSTTSC71


��

Explanation: Operator reply to a console message.


�� $�� %&��

Explanation: �� detected that the tape is not fileprotected. �� is a read-only function and can onlyprocess��tapes.

Solution: Reply to the message.

� If “ �” is entered, the function will ignore the write enabledcondition.

� If “ ” is entered, the function will unload the tape andprompt the operator to file protect the tape and remount.

� If “ �” is entered,�� will cancel.

�� "��!��"�� "��#��

Explanation: Blank tape was detected during the��dumputility.


�� $�� !��

Explanation: If the tape control unit does not have the blanktape detection feature installed, the tape can ’run away’ whenblank tape is read. This could cause a missing interruptcondition or it may cause an IFCC (interface control check)condition.


MPSTTSC72 MPSTTSC75


�� !��

Explanation: If the tape was not closed out properly, it mayhave run off the end of the reel.

Solution: Check the label dump output.

��

Explanation: An interface control check has been received.

Solution: Ensure that the tape control units are still in properworking order.

�� !��

Explanation: No error conditions were encountered whilereading the record after the error.


�� "�� !� ��

Explanation: The tape was not file protected.

Solution: Unload and file protect the tape. Remount the tape.Press any character on the keyboard to continue.

MPSTTSC76 MPSTTSC79


��

Explanation: A block ID sequence error was detected withinthe label of this tape.

This may indicate that a prior write error has occurred andcaused this condition.

Solution: The tape may require re-initialization before it can bereused.

��

Explanation: A block ID sequence error was detected.

This may indicate that the last job that wrote to this tape did notcomplete properly.


��

Explanation: An incorrect length record was read within thelabel of this tape.

This may indicate that a prior write error has occurred andcaused this condition.

Solution: The tape may require re-initialization before it can bereused.

��

Explanation: This messages states that the tape will requirere-initialization before it can be reused.

Solution: Re-initialize the tape.

MPSTTSC80 MPSTTSC83


��

Explanation: A read block ID command (22) has failed. Thesense data for this error follow this message.


��

Explanation: A locate block command (4F) has failed. Thesense data for this error follow this message.


��

Explanation: No errors were detected while scanning anNL/NSL tape.


��

Explanation: The last record within the data file failed.

This may indicate that a write data check or a write equipmentcheck ��’d the job during the creation phase.


MPSTTSC84 MPSTTSC87


��

Explanation: A tape void was detected immediately after anerror record.



��

Explanation: The first error during input was PEOT.

This may indicate that the output job wrote into the physicalEOT (end of tape).


��

Explanation: The record size exceeds the buffer size.


��

Explanation: A sequence error was detected after an errorrecord.



MPSTTSC88 MPSTTSC92


��

Explanation: After the error record, the beginning of the nextrecord is printed. A maximum of 80 bytes of data aretransferred. This data may help determine if “old data” was thecause of the first error.


��

Explanation: An incorrect length record was detected withinthe data set. All data set records are checked for block size ifrecord format was variable or fixed.

Message��follows this message.


��

Explanation: The record��for file��is incorrect.Message��follows this message.


��

Explanation: Parameter (��) is either coded incorrectly or isinvalid for the�� command for the��function.

Solution: Enter the�� command using the correctparameter.

��

Explanation: The record read had a length of��bytes.


MPSTTSC93 MPSTTSC98


��

Explanation: Multiple errors were detected; the analysis of thefirst error cannot be completed.


��

Explanation: The expected block��was received. It is +1from the last readable record.


��

Explanation: The block �� read from the tape was writtenwhen the record was created. If the��read is out of sequencewith the prior record (indicating “old data” was read), a��

�� error (ERPA code 41) will occur.

This may indicate that the output job did not complete normallyor was not closed out properly. It may also indicate thatsubsystem error recovery positioned the tape at an unexplainedsection of the tape.


��




MPSTTSC99 MPSTTSC102


��

Explanation: This warning is placed on the reports if SL tapesare being processed.

�� attempts to process SL labels as IBM or ANSIstandard. Tapes that use an 80-byte��record as the firstrecord on the tape will be treated as an SL-labeled volume.

Any other types of labels, that begin with a��record, maycause unpredictable results.


��

Explanation: �� will attempt to proceed to thevoid/physical EOT after skipping the 1st record after a doubletape mark.


��

Explanation: The number of double tape marks processed by�� is��.


��

Explanation: �� has finished; the number of filesprocessed (��) includes��,��, and��files.


MPSTTSC103 MPSTTSC208


��

Explanation: ��has finished; the number of filesprocessed (��) includes��,� ��, and�� files.


��

Explanation: ��has finished. There were too manyerrors found and� ��will not continue past this volume.


��

Explanation: The last ERPA code received was��.


��

Explanation: The�� process has started.


��

Explanation: The record count was��just before thecounter was reset.


201 Chapter 18. MPSTVSC

Chapter 18. MPSTVSC

Volume Scan (VOLSCAN) Messages



The following messages are issued for Volume Scan:

MPSTVSC00 MPSTVSC03


��

Explanation: The��function is executed on the deviceat address��with volume serial number��. Thedevice� ��is:

� 3330–1 (3330 Mod 1), 3330–11 (3330 Mod II)

� 3350 C1 (3350 in 3330 Mod 1 compat mode), 3350 C11(3350 in 3330 Mod 11 compat mode), 3350 N (3350 innative mode)

� 3380, 3380E (3380 2X), 3380J, 3380K

� 3390-1, 3390–2, 3390–3, 3390–9


��

Explanation: The parameter��is either coded incorrectlyor is invalid for the��function.


��

Explanation: An I/O error occurred while attempting toexecute a sense (04) command.

Solution: Retry the command. If the problem persists, notifyCS Software Support.

��

Explanation: The��function terminated because theend of a VM/370 mini-disk, or the end of a 4305 in 3380 mode,was detected. ��.��is displayed in decimal and hex.


MPSTVSC04 MPSTVSC06


��

Explanation: The value specified for the��or the��parameter is not valid for the device being tested.

Solution: Correct the value and retry the command.

��

Explanation: The test device failed to open, the test device isnot a DASD device, or the program does not recognize the typeof DASD.

Solution: Verify that the first test device defined is codedcorrectly.

��

Explanation: An I/O error occurred while reading a datarecord. � ��is executing in��mode. In this mode,a random record on a track is read.

Solution: Try scanning in normal mode to see if the error ispermanent.

MPSTVSC07 MPSTVSC07


��

��

��

��

��

Explanation: This message prints a table of errors by head anda table of errors by type. Only one error will be counted pertrack and errors encountered during retry do not appear in thistable.

The��table lists the total number of errorsencountered for each head and the total number of defect skipsassigned for all tracks scanned for that head and the total numberof tracks that had any defect skips assigned. The head number islisted in decimal and in hexadecimal.

The��table lists the total number of errors forall tracks scanned for each format error type. ��errors areerrors which are not format 0 through format 8 errors.Correctable format 4 errors are counted as format 5 errors here.Format 6 errors are not presented.


MPSTVSC08 MPSTVSC11


��

Explanation: This message prints a table of cylinders witherrors by head. The head number is listed in decimal andhexadecimal. If the message� ��is also printed,more than 512 errors occurred.


��

Explanation: A��command was entered and accepted bythe��function and��terminates.


��

Explanation: ��is unable to continue because anunrecoverable error occurred. An unrecoverable error could be achannel error or intervention required.

Solution: If intervention is required, correct the condition andrestart the program.

��

Explanation: No errors were detected by the��

function on the device at address��with volume serialnumber��.


MPSTVSC12 MPSTVSC15


��

Explanation: Correctable/temporary errors were detected by��on the device at address��with volume serialnumber��.

Solution: This message indicates problems that should beinvestigated at the next scheduled maintenance period. TheMPST printer output should be retained and given to CSSoftware Support.

��

Explanation: Device errors were detected by��on thedevice at address��with volume serial number��.

Solution: This message inidcates problems that should beinvestigated as soon as possible. The MPST printer outputshould be retained and given to CS Software Support.

��

Explanation: The CE cylinder could not be scanned due to anerror in the parameter list.

Solution: Notify CS Software Support.

��

Explanation: An I/O error occurred while attempting toexecute a sense ID (E4) command.


MPSTVSC16 MPSTVSC18


��

Explanation: Correctable data checks were detected by��on the device at address��with volume serialnumber��.

Solution: This message indicates possible problems that shouldbe investigated at the next scheduled maintenance period. TheMPST printer output should be retained and given to CSSoftware Support.

��

Explanation: No problems were detected by the��

function on the device at address��with volume serialnumber��.


��

Explanation: An I/O error occurred while attempting toexecute a read device characteristics command.


MPSTVSC20 MPSTVSC20


��

Explanation: An error occurred while attempting to read thehome address (HA) and record zero (R0) of the alternate trackthat is assigned to this defective track. The address of thealternate track found in the count field of the defective track isprinted with the error information.

� ��—The cylinder/head address in decimal andhexadecimal.

� ��—The CPU id.

� ��—The actual path where the error occurred.

� ��—The unit and channel status from theCSW.

� ��—The condition code.

� � ��—The ECB completion code.


Solution: The MPST printer output should be retained andgiven to CS Software Support.

MPSTVSC21 MPSTVSC23


��

Explanation: An error occurred while reading the track.

� ��—The cylinder/head address in decimal andhexadecimal.

� �—The CPU id.

� ��—The actual path where the error occurred.

� ��—The unit and channel status from theCSW.

� �� —The ECB completion code.



��

Explanation: An error occurred reading the home address (HA)and the record zero (R0) of this track.


��

Explanation: An error occurred reading record number��

(decimal) or��(hexadecimal) of this track. ��is the retry count for��.


MPSTVSC24 MPSTVSC27


��

Explanation: The track is flagged as a defective track, and thealternate track assigned is listed in decimal and hexadecimal.


��

Explanation: The track is an alternate track that is flagged asdefective.


��

Explanation: The track is an alternate track and an erroroccurred while reading the home address (HA) and the recordzero (R0) of the defective track.


��

Explanation: Two possible conditions may exist:

� The track was flagged as defective, but the alternate trackpointed to does not point back to the defective track.

� The track is an assigned alternate, but the defective trackpointed to by this alternate track does not point back to thealternate.


MPSTVSC28 MPSTVSC29


��

Explanation: The count field of the record read was not instandard format. The actual record count field is printed ascylinder (��), head (��), record (�), key (�), and data (��).

The following possible conditions could exist:

� R0 is a file mark (data field length equals zero).

� The record number of this record is less than or equal tothe record number of the previous record read (indicatingduplicate or out-of-sequence records).


��

Explanation: Home address (HA) and record zero (R0) wereread without error, but were not in standard format. Thefollowing possible conditions could exist:

� Bits 0–5 of the HA flag byte are not zero.

� The cylinder or the head address is not correct.

� The R0 count field record number is not zero.

� The R0 record has a key field.

� The R0 record data field is not 8 bytes.

The record zero field is: flag/cylinder/head.

The home address field is: cylinder/head/record/key/data_length.


MPSTVSC30 MPSTVSC33


��

Explanation: An error occurred when reading this track, butwhen the records on the track were re-read, one at a time, theerror did not recur.


��

Explanation: The maximum number of retries specified by the� ��parameter has been reached without retry being successful.� ��terminates scanning of the current record and proceedsto the next track to be scanned.


��

Explanation: The track is an assigned alternate track and thedefective mate to which this track is assigned is listed.


��

Explanation: An error occurred attempting to obtain the defectskip data for this track. �� is the retry count for�� .

� For a 3350 type device��is��

� For a 3380 type device��is��


MPSTVSC34 MPSTVSC36


��

Explanation: The following possible conditions could exist:

� The home address (HA) or record zero (R0) record couldnot be read.

� The number of permanent errors that occurred whilereading data records exceeded the number specified by the�� parameter.

Scanning of that track terminates and scanning of the next trackbegins.


��

Explanation: The number of errors encountered whileexecuting�� has exceeded the maximumallowed by the�� parameter and testing terminates.


��

Explanation: A status of unit exception was received on a readmultiple CKD command. Unit exception on CKD DASDindicates an end of file mark was encountered. On a readmultiple CKD command, the end of file mark should betransferred to the system as part of the data.


MPSTVSC37 MPSTVSC52


��

Explanation: An invalid track format was detected and nofurther testing will be attempted. Invalid track format bypasses��checking and immediately skips to the next track.


��

Explanation: This track of a 3350 type device was scanned andthe defect skip information was read from home address (HA)and printed.

� ��specifies the location of the first defect on the track,��

specifies the location of the second defect on the track, and��

specifies the location of the third defect on the track


��

Explanation: This track of a 3380 type device was scanned andthe defect skip information was read from home address (HA)and printed. ��is a decimal value.

� ��specifies the location of the first defect on the track,��

specifies the location of the second defect on the track, and . . . � ��specifies the location of the seventh defect on thetrack


��

Explanation: The defect skip data for this track is not availabledue to errors. This message is preceded by message��

which describes the error.


MPSTVSC60 MPSTVSC62


��

Explanation: A Sense ID command (X’E4’) was issued to thetest device. The data, if any, returned by this command isdisplayed in this message. This message indicates��

��if:

� The test device command rejects this command.

� The first byte of data returned is not ��.

� The number of bytes returned is other than seven.

� An I/O error occurs.

If an I/O error, other than command reject occurs, it is reportedby message� ��.

The Sense ID data is printed as:

� ��—The control unit type (2 bytes).

� ��—The control unit model (1 byte).

� ��—The device type (2 bytes).

� ��—The device model (1 byte).


��

Explanation: The device for��has no valid CEcylinder.


��

Explanation: The device for��has no defect skipinformation available. Parameter forced off.


MPSTVSC63 MPSTVSC91


��

Explanation: The��command has beenprocessed and� ��terminates.


��

Explanation: The�� parameter was specified, butthe device is not defined.

Solution: If the first device defined is not the device to be used,specify the correct address or DD name.

��

Explanation: The�� parameter specified does nothave a path available.

Solution: Select another device.

��

Explanation: The�� parameter specified is notenabled.

Solution: Enable the device and try again.

��

Explanation: Parameter (��) is either coded incorrectly or isinvalid for the��command for the� ��function.


MPSTVSC96 MPSTVSC99


��

Explanation: The��command�� was issued to��.


��


Solution: None required. ��and�� are the onlyvalid��parameters.

��

��

��

Explanation: Program check failed.


219 Chapter 19. MPSTVTM

Chapter 19. MPSTVTM

Terminal Control Unit Verification (VTERM) Messages



The following messages are issued for Terminal Control UnitVerification:

MPSTVTM00 MPSTVTM04


��

Explanation: The terminal control unit verification test hasstarted.


��

Explanation: The test device must be defined as a type 5 DDcard.

Solution: Redefine the test device.

��

Explanation: The memory allocation for a 4k I/O buffer failedand the function terminates.

Solution: Increase memory or reduce the number of concurrenttasks that are running.

��

Explanation: The full pattern ripple display test has started.


��

Explanation: The individual character display test has started.


MPSTVTM05 MPSTVTM09

221 Chapter 19. MPSTVTM

��

Explanation: The data read from the screen buffer was notwhat was expected. The data at byte��should have been��.

Solution: Repeat the test using a different monitor. If theproblem persists, the controller is in error. This is a severe errorindicator.

��

Explanation: This message is displayed on the console.

Solution: Look at the test monitor and confirm the screencontents.

��

Explanation: The user indicated that the previous display wasincorrect and the function terminates.


��

Explanation: The user indicated that the previous display wascorrect and the function continues.


��

Explanation: An I/O error occurred and the test terminates.


MPSTVTM10 MPSTVTM14


��

Explanation: The user has been prompted to enter a singlecharacter on the test device.

Solution: User enters the prompted character at the testterminal.

��

Explanation: The user entered character��on the test deviceand character��is now being displayed.


��

Explanation: The terminal control unit verification test hasbeen terminated.


��

Explanation: The LMU must be disconnected from itscontroller and replaced with a standard 3278 terminal beforebeginning this test series.

Solution: Attach the 3278 terminal and/or ensure that thecorrect location was entered in the device definition.

��

Explanation: An invalid key was pressed or an invalidcharacter was entered for the test sequence.

Solution: Enter a valid LMU character. Valid characters consistof upper case alphabet, numbers 0–9, and the characters < > ( ) ?and blank. Or, press��F3� to terminate the test.

223 Chapter 20. MPSTWRC

Chapter 20. MPSTWRC

Write-Read Cartridge (WRCART) Messages



The following messages are issued for Write-Read Cartridge:

MPSTWRC00 MPSTWRC02


��



��



��

Explanation: Device �� at address��with volumeserial number��configured without error.


MPSTWRC03 MPSTWRC03


��

��

��

��

��

��

MPSTWRC04 MPSTWRC04


��

Explanation: The summary for this execution of��fordevice��at address��with volume serial number��is printed.

� The number of passes executed and the number of recordsand tape marks processed is listed along with the totalnumber of compare, sequence, temporary, and permanentread and write errors.

� The total elapsed time is the time used for all passes.

� The total bytes transferred, written, and read are also listed.

� If the�� parameter was specified, the number ofcontrol units detected (��) functions for read andwrite temporary, erase gap, and read and write transienterrors are listed.




��

Explanation: No test devices were configured for thisexecution of��.


MPSTWRC05 MPSTWRC07


��

Explanation: A��for a portion of memory to be usedfor data comparison failed. Data comparison cannot be done.

Solution: For data comparison, increase the size of the regionor partition where MPST is executing and then re-execute.

��

Explanation: The�� parameter specified a value of lessthan 28 or greater than the maximum size allowed. The� ��parameter was changed to reflect the correct range for��.





��





MPSTWRC08 MPSTWRC08


��


� ��—The test device DD card is not atype 5 DD card.



� �� —A�� for a20K I/O buffer failed. Increase the size of the region orpartition in which MPST is executing.


� �� —No device has beendefined for this DD name.

� �� —An open for the device failed.

� �� —The cartridge volumemounted on this device contains a valid OS tape label.Testing cannot be done on this device.

� �� —Device characteristics readdo not match the DD type specified.

� �� —Unable to get sense data from the device.

� �� —The test device DD carddoes not define a cartridge device.

Solution: Verify that the test devices are correctly defined,online and available.

MPSTWRC09 MPSTWRC13


��"�� !��"��

Explanation: �� parameter detected but��was notdefined. Volume serial number��will be ignored.


��"�� $��#��

Explanation: If the block size specified by the�� parameter is less than 4098, the time to execute��tocompletion may be very long.


��"��




��"��

Explanation: ��has detected that a��command wasentered at the operator’s console. Testing on test device��

at address��with volume serial number��has beenstopped.


��"��



MPSTWRC14 MPSTWRC15


��

Explanation: The��parameter requested a larger blocksize than the device can handle. The block size has beenchanged to the correct��for this device.





��

Explanation: ��commands issued to configure the devicewere rejected.

Solution: Verify that the device has the current level ofmicrocode.

MPSTWRC19 MPSTWRC19


��

��

Explanation: This message identifies the tape drive that iscreating the cartridge.

� The drive reading the cartridge is identified by ��

and drive address ��.

� The drive that created the cartridge is identified by�� , drive address ��, control unit serial number�� , tape drive physical address ��, and tapedrive logical address ��.

� The time is specified by hour:minute:second (��)and the date is specified by month:day:year (��).They identify when the write pass started.

� ��is the number of records per file.

If this device is a Model 3490E, the characters ’3490E’ willfollow� ��.


MPSTWRC20 MPSTWRC21


��

��

Explanation: This message identifies the tape drive that createdthe cartridge being read.

� The drive reading the cartridge is identified by ��

and drive address ��.

� The drive that created the cartridge is identified by�� , drive address ��, control unit serial number�� , tape drive physical address ��, and tapedrive logical address ��.

� The time is specified by hour:minute:second (��)and the date is specified by month:day:year (��).They identify when the write pass ended on the creatingdrive if the current pass is a read backward.

� �� is the number of records per file.


��

Explanation: Incorrect status was received for an I/O operationto device�� at address��during a��pass. Theactual status received was��and the command executed was��.


MPSTWRC22 MPSTWRC25


��

Explanation: A read forward pass is being executed on the testdevice� ��at address��but the BOT label on thecartridge is not a BOT label that��writes on a testvolume. Testing on the device terminates.


��

Explanation: A data record was expected but an EOT label wasread. The tape mark separating the data records and the EOTrecord was missed on a read forward pass of the cartridge on testdevice� ��at address��with volume serial number��. Testing on the test device terminates.


��

Explanation: The cartridge on test device� ��at address��with volume serial number��is missing the EOTlabel that��writes on a test volume. Testing on thedevice terminates.


��

Explanation: The number of blocks read (��) does notcompare with the number of blocks written ( ��) as listed inthe EOT label for the cartridge on test device� ��at address��with volume serial number��. This is the equivalentof an��. Testing on the test device continues.


MPSTWRC26 MPSTWRC29


��

Explanation: During a read backward pass on the cartridge ontest device��at address��with volume serial number��, the first record read was not the EOT label as expectedor the EOT record was not found after skipping a maximum ofthree tape marks. Testing on the test device terminates.


��

Explanation: A read backward pass is being executed on testdevice��at address��with volume serial number��. The EOT label was read successfully but the nextrecord on the cartridge was not the tape mark preceding the EOTrecord. Testing on the device terminates.


��

Explanation: A data record was expected but a BOT label wasread on a read backward pass of the cartridge on test device��at address��with volume serial number��.(The tape mark separating the data records and the BOT recordwas missed.) Testing on the device terminates.


��

Explanation: The cartridge on test device��at address��with volume serial number��is missing the BOTlabel that��writes on a test volume. Testing on thedevice terminates.


MPSTWRC30 MPSTWRC33


��

Explanation: The last pass executed on test device��ataddress��with volume serial number� ��was not awrite pass, a read forward pass, or��is active and��was not specified. A read backward pass cannot beexecuted and testing on the test device continues.


��

Explanation: A record was read on test device��ataddress��with volume serial number� ��that was notthe length expected. ��expected record number��

to have��bytes but��bytes were received.


��

Explanation: An exchange point was reached for test device��at address��.

Solution: Reply with any character when the cartridge volumeshave been exchanged and the drive is made ready.

��

Explanation: An open for test device��at address��failed after the cartridge volumes were exchanged. Testing onthe device terminates.


MPSTWRC34 MPSTWRC37


��

Explanation: The first record on the cartridge, mounted on testdevice��at address��, after an exchange point was nota BOT label record written by the� ��function. Testing onthe device terminates.


��


at address��with volume serial number��.� ��expected�� but read�� , where��and��are either��or�� .


��

Explanation: The ID fields (the first and last eight bytes) donot match for record��on test device��at address��with volume serial number��.

� ��is the first eight bytes of the record.

� ��is the last eight bytes of the record.


��

Explanation: A short record was read on test device��ataddress��with volume serial number��. A dump ofthe record follows this message.


MPSTWRC38 MPSTWRC40


��


at address��with volume serial number��mounted. ��expected record� ��but received record��.


��

Explanation: The actual data read from a record did not matchthe expected data for that record.


��


at address��. The cartridge was written in ICRC format andthe drive is not capable of ICRC.


MPSTWRC41 MPSTWRC42


��

��

��

��

��




��



MPSTWRC43 MPSTWRC43


��

��

��

��

��

Explanation: A read forward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read forward pass iscontained within this message.

If��is active, the counts for��functions are listed;otherwise, they are all zero.


MPSTWRC44 MPSTWRC45


��

��

��

��

Explanation: A read backward pass has been completed fordevice��at address��with volume serial number��. The summary report for the read backward pass iscontained within this message.


��

Explanation: A read backward pass has started for device��at address��. The cartridge was written in ICRCformat and the drive is not capable of ICRC.


MPSTWRC50 MPSTWRC50


��












MPSTWRC51 MPSTWRC51


��

��

Explanation: A temporary error has occurred on test device��at address��with volume serial number�� at��











MPSTWRC52 MPSTWRC52


��

��

Explanation: A permanent error has occurred on test device�� at address��with volume serial number��.� �� indicates the date and time the erroroccurred. ��indicates an error condition of either ��or��.


� �� —The number of bytes transferred at thetime of the error.

� �� —The number of times the operation hasbeen retried.

� �� —The channel command being executed.



� � ��—The CPU ID of the CPU on which the erroroccurred.



MPSTWRC52 MPSTWRC52


� ��is a message describing the error. Somepossible messages and their meanings are:


� ��—The event control block (ECB) completioncode was not 7F (no error) or 41 (permanent error).Any other ECB code is a fatal error.


� �� —Read error recovery failedto recover from a temporary read error. The error isnow a permanent error.

� �� —Write error recoveryfailed to recover from a temporary write error. Theerror is now a permanent error.

� �� —The error occurredduring read error recovery. �� is the commandwhich failed during retry.


� �� —The error occurredduring write error recovery. �� is the commandwhich failed during retry.


MPSTWRC53 MPSTWRC56


��

Explanation: Following a sequence error,��attempts toget back in sync by resetting the record expected based upon therecord just processed. If the record read is more than eight off ofthe record expected, the error is too great to correct in thismanner.


��

Explanation: The�� command issued to device��at address��with volume serial number� ��failed.


��

Explanation: An error occurred on device��at address��with volume serial number� ��. The ERPA code of��is unsupported.


��

Explanation: The buffered log overflowed for device��ataddress��with volume serial number� ��. The logcounters have been added to the statistics.


MPSTWRC57 MPSTWRC60


��

Explanation: The buffered log data is read at the end of eachpass for device��at address��with volume serialnumber��. The log counters have been added to thestatistics.


��



��

Explanation: A unit check was posted due to end of data beingdetected on the cartridge tape. This is an excepted error. Thetype of pass ( ��) is��for a write pass,��for a readforward pass, or��for a read backward pass.


��

Explanation: When a cartridge tape in ICRC format is readbackward by device��at address��with volume serialnumber��, this message is posted. FSC of X’4411’.


MPSTWRC61 MPSTWRC63


��

Explanation: A pass has been started on test device�� ataddress��with volume serial number��. The type ofpass (�� ) is��for a read forward pass,��for a readbackward pass, or�� for a write pass.


��

Explanation: A pass has ended on test device�� ataddress��with volume serial number��. The type ofpass (�� ) is��for a read forward pass,��for a readbackward pass, or�� for a write pass.

The start and end date and times, as well as the elapsed time forthis pass, are listed.


��

Explanation: This message always follows message� ��.


MPSTWRC64 MPSTWRC97


�� #�� !! �� !�� %��"�� $��

Explanation: A cartridge tape written in 3480–2 XF format ismounted on device��at address��and the device doesnot support 3480–2 XF format.


�� #�� &�� !�� $�� $��!��&��

Explanation: The�� of the actual record is greater thanthe maximum block size specified (��) via the�� parameter or the default length if�� was not specified.


�� #��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the��command for the��function.


�� #�� "��%��#��

Explanation: The��command�� was issued to��. The valid��commands for��follow thismessage.


�� #�� #�� !�� %��



MPSTWRC98 MPSTWRC98


��




251 Chapter 21. MPSTWRD

Chapter 21. MPSTWRD

Write-Read Disk (WRDISK) Messages



The following messages are issued for Write-Read Disk

MPSTWRD00 MPSTWRD02


��



��


Solution: Re-enter the command using the correct parameter.

��

��

Explanation: ��has successfully configured test device��at address��.

� If the device has the DASD fast write (DFW) feature, then��will be��or�� .

� If the device is an Iceberg or Nordique device, then��will be��and STK and the product name willbe listed.


MPSTWRD03 MPSTWRD03


��

��

��

Explanation: The summary for this execution of�� fordevice��at address��with volume serial number��is printed. Each track tested by�� was tested anaverage of�� times. �� is calculated by dividing thenumber of times any track was selected for testing by thenumber of tracks to be tested.

The� ��table lists the number of recordsprocessed (both reading and writing) and the number of errorsencountered for each head tested. The head number is listed indecimal and hexadecimal.

The� ��table lists the number of errorsfor each error type for all heads. ��errors are errors whichare not format 0 through 8. ��errors are errors wheredata read did not match the data written.


MPSTWRD04 MPSTWRD08


��

Explanation: No test devices were configured for thisexecution of�� .

Solution: Verify that the test devices are correctly defined andonline and available.

��

Explanation: The block size specified by the��parameter is larger than the maximum allowed for test device��. The block size will be set to the maximum allowed forthis device.


��

Explanation: An error occurred on device��at address��with volume serial number��and the� ��parameter was specified. A dump of the track follows thismessage.


��


� ��—A 3390 controller witha 3390 device attached and the device characteristicinformation indicates that the problem is that the F5 factor,a division for the formula, is zero.

� �� —The test device DDcard for��is not a type 2, 3 or 4 DD card. Verify thatthe DD card is coded correctly.

MPSTWRD08 MPSTWRD08


� ��—A read devicecharacteristics command was issued to the device and anerror was encountered.

� ��—A sense command was issued to thedevice and an error was encountered.

� ��—A sense �� command was issued tothe device and an error was encountered.

� ��—A sense subsystemstatus command was issued to the device and an error wasencountered.

� ��—More systemmemory required for�� to run with this manydevices.

� ��—There is no DD card for��. Verify that the DD card is coded correctly.

� �� —The DD card specified for testdevice��is a DD type 1 (zero space allocated). TheDD type must be 2, 3 or 4.

� ��—An open for the device failed. Verify thatthe DD card is coded correctly.

� ��—The device typespecified on the�� DD card does not match thedevice type obtained from the read device characteristicscommand.

� ��—The test device DD card for��does not define a DASD device. Verify that theDD card is coded correctly.


MPSTWRD09 MPSTWRD13


��

Explanation: The��parameter or��command wasspecified and too many devices were requested.

Solution: The maximum number of defined devices is eight.

��

Explanation: The I/O limit specified by the��parameter has been reached for device� ��at address��with volume serial number��. Testing has terminated onthat device but continues on any other devices.


��

Explanation: ��has detected that a��command wasentered at the operator’s console. Testing on all devices,including� ��at address��with volume serial number��, has been stopped.


��

Explanation: Testing on test device� ��at address��with volume serial number��has been terminated. Eitherthe number of permanent errors exceeds the maximum allowedby the��parameter or an unrecoverable I/O error hasoccurred.

Solution: None required. Testing continues on all otherdevices.

MPSTWRD15 MPSTWRD18


��

Explanation: No errors were detected by��while testingthe device at address��with volume serial number��.


��

Explanation: Correctable/temporary errors were detected by��while testing the device at address��with volumeserial number��. This message does not indicate aproblem that requires immediate attention.


��

Explanation: Errors were detected by��while testingthe device at address��with volume serial number��.

Solution: This message indicates problems that should beinvestigated as soon as possible. The printer output should beretained and given to CS Software Support.

��

Explanation: Correctable data checks were detected by��while testing the device at address��with volumeserial number��.


MPSTWRD19 MPSTWRD33


��

Explanation: ��detected no problems while testing thedevice at address��with volume serial number��.


��

Explanation: An error occurred while trying to fill the trackwith records. This error prevents further testing on the track andtesting on this track is terminated. However, this track may beselected for testing again.

This track is located on device��at address��andvolume serial number��.


��

Explanation: An error occurred while attempting to write awrite count, key, or data record.


��

Explanation: An error occurred while attempting to read awrite count, key, or data record.


��

Explanation: An error occurred while attempting to update arecord with a write key and data command.


MPSTWRD34 MPSTWRD80


��

Explanation: An error occurred while attempting to read anupdated record.


��

Explanation: An unrecoverable error occurred. Anunrecoverable error is a channel error, intervention required,command reject, or a device error other than unit check.


��

Explanation: An error occurred on test device��ataddress��with volume serial number��and themaximum number of retries specified by the��parameterhas been reached without retry being successful.


��

Explanation: Bad parameter passed in program.


��

Explanation: Either the parameters��or��included device��and that device does not support theDASD fast write (DFW) feature.


MPSTWRD81 MPSTWRD85


��

Explanation: Device��is not connected to a 3390 typecontroller with the cache feature.


��

Explanation: Device��at address��with volumeserial number��had a failure issuing DFW commands.


��

Explanation: The DASD fast write (DFW)��of thedevice at address��is now either��or��.


��

Explanation: Either the sense subsystem status commandfailed or a�� parameter was issued to device��andits DFW��failed to��.


��

Explanation: The 3390 type control for device��does notsupport the DASD fast write (DFW) feature.


MPSTWRD86 MPSTWRD97


��

Explanation: On a 3390 type control for device��the ��is either:

� �� , or

� �� .

NVS stands for nonvolatile storage.


��

Explanation: The parameter (��) is either coded incorrectlyor is invalid for the��command for the��function.

Solution: Re-enter the command using the correct parameter.

��

Explanation: The��command��was issued to��. The valid��commands for��follow thismessage.


��



263 Chapter 22. MSAE

Chapter 22. MSAE

MPST Stand-Alone Executive (MPSTSAE) Messages



The following messages are issued for the MPST Stand-aloneExecutive:

MSAE000 MSAE004


��

Explanation: This message, including copyright notice, isissued when MPSTSAE successfully loads.


��

Explanation: MPSTSAE has loaded and is ready to processcommands.

Solution: Enter MPSTSAE commands.

��

Explanation: MPSTSAE is executing on a VM virtualmachine.


��

Explanation: MPSTSAE is executing on an AP/MP system.The number of processors configured is ��.


��

Explanation: MPSTSAE is unable to determine the one secondBCT instruction count for the CPU. Time dependent testingcannot be performed.


MSAE005 MSAE009


��

Explanation: The CPU time-of-day clock is either incorrect ornot working.

Solution: To continue, reset the time-of-day clock.

��

Explanation: The time-of-day (TOD) clock must be enabled tocontinue MPSTSAE operation.

Solution: Press the switch on the CPU that enables the TODclock.

��

Explanation: The CPU interval timer is not operational.


��

Explanation: The interval timer must be enabled.

Solution: Enable the interval timer; then, enter any keyboardcharacter to continue MPSTSAE operation.

��

Explanation: The storage areas being used by MPSTSAE are:

� �� —The size of the main storage area.

� ��—The size of the MPST dynamic area.

� ��—The high address used by MPST SAE.


MSAE010 MSAE017


��

Explanation: MPSTSAE is operating in XA, ESA or 370mode.


��

Explanation: The MPSTSAE task, �� , has abended.This message displays if the��command is used tohalt operation. If a printer is currently defined, a dump of themain storage area is printed.

Solution: If this message is displayed and a��

command was not issued, contact CS Software Support. Aprogram error has occurred.

��

Explanation: An I/O error has occurred.

� ��—The CPU number.



� � ��—The SIO condition code.

� �� —The CSW unit and channel status andresidual byte count.

� �� —The cylinder and headaddress and the record number (if DASD).

� ��—The sense data (if unit check is � in theunit status).


MSAE018 MSAE019


��

Explanation: An I/O error occurred when MPSTSAEattempted a NOP command to a device. The message precedingthis one (��) describes the error.

Solution: Reply to the message, enter one of the following:

� ��to ignore the message and continue.

� ��to retry the operation.

� ��to cancel the function attempting to use the device.

��

Explanation: The program being run attempted to��anundefined DD card� ��.

Solution: Check the current device definition or the��

control card.

MSAE020 MSAE020


��

��

��

��

��

Explanation: If more than 10 I/O operations are performed ona test device, this message is issued (only to the console) whenthe function ends and the test device is closed.

� Operation time—The time between a request for an I/Ooperation (EXCP) and when the operation is posted ascompleted (ECB).

� Queue time—The time an I/O operation remains queuedby the I/O supervisor due to a channel, control unit, ordevice busy condition.

� CCW time—The time between the last SIO, SIOF, orSSCH instruction to when the channel is received for theCCW chain. When MPSTSAE is run on a VM/370 virtualmachine, the VM control program (CP) is included in theCCW values.


MSAE095 MSAE099


��

Explanation: A buffer log overflow occurred on the IPL/loaddevice.


��

Explanation: An error occurred on the MPSTSAE IPL device.




� ��—The CSW unit and channel status andresidual byte count.

� ��—The cylinder and headaddress and the record number (if DASD).

� ��—The sense data (if unit check is �� in theunit status).


��

Explanation: The program module cannot be found on the IPLdevice.

Solution: Contact CS Software Support.

MSAE109 MSAE111


��

Explanation: During program load MPSTSAE could notresolve references (1–7).


��

Explanation: The test device at address��on CPU��has reported environmental sense data. This data could bestatistical or logging mode data.


� � �� —The device address.

� � �� —The sense data (if unit check is �� in theunit status).


��

Explanation: An unexpected I/O interrupt was received fromthe test device at address��on CPU��.



� ��—CSW unit and channel status.

� � �� —The sense data (if unit check is �� in theunit status).


MSAE112 MSAE115


��

Explanation: A buffered log full status was received from the4305 test device at address��on CPU��. Each of theeight 8–byte buffered log entries are printed.




� ��—The eight 8–byte buffered log entries.


��

Explanation: A recoverable machine check interrupt wasreceived from CPU �� and ignored by MPSTSAE. Bits 0–64of the machine interrupt code from main storage address hex E8are printed.


��

Explanation: An external interrupt from CPU��wasreceived and ignored by MPSTSAE. �� is the externalinterrupt code from main storage address hex 86.


��

Explanation: The test device at address��on CPU�� isnot ready. �� is the sense data (if unit check is �� in the unitstatus).


MSAE116 MSAE117


��

Explanation: An unexpected status was received when an ISOwas done to the test device at address��on CPU��. ��is the unit and channel status bytes of the stored CSW.


��

Explanation: The test device at address��on CPU��has failed to present device end, control unit end, or channel endstatus within the MPSTSAE timeout period. For tape devicesthe timeout period is 2 minutes; for all other devices the timeoutperiod is 1 minute.

�� is the last status received by MPSTSAE for the testdevice. �� could be:

� ��—Device busy (CC=1 with BUSY) on the last SIO.

� �� —An I/O operation was started and channel end and/ordevice end status was not received.

� ��—Channel busy (CC=2) on the last SIO.

� ��—Control unit busy (CC=1 with STM and BUSY) onthe last SIO.

� ��—No I/O operation is in progress or pending.

� ��—The device is not ready.


MSAE118 MSAE119


��

Explanation: The MPSTSAE missing interrupt handler hasgenerated a pseudo I/O interrupt for a hung I/O operation. Thepseudo I/O interrupt has both the interface control check and thechannel control check set in the channel status byte of thechannel status word (CSW).

Solution: Message��describes the hung I/O operation.

��

Explanation: An unknown message has been queued.


MSAE120 MSAE120


��

Explanation: A SIM record was logged from the test device ataddress��.


� ��—The date and time of the SIM.

� ��

� ��—The device code.

� ��—The device type and modelnumber.

� ��—The controller type and modelnumber.

� ��—The error code.

� ��—The severitycode, SIM type, and the SIM repeat.

� � �� —The manufacturer’s idand the plant id.

� �� —The serial number for the plant.

� ��—The SIM id.

� �� —The reference codes.

� ��—The message code.

� �� —The message modifiers.

� �� —The raw sense bytes.


MSAE161 MSAE171


��

Explanation: The SYSIN device being configured has nophysical paths enabled.

Solution: Enable a path to the device and reissue the��command.

��

Explanation: The��command just issued has completed.

� If the SYSIN device is successfully accessed, the��

is the device address and the device type. If this is a tapedevice, �� is the file number.

� If the SYSIN device has been varied offline, the ��

is��.


��

Explanation: A SYSIN device was already defined. The��command just issued was ignored


��

Explanation: Because MPST was running when the��

command was issued, the command was ignored.


��

Explanation: The status of the start I/O fast option isdisplayed.


MSAE172 MSAE211


��

Explanation: The current state of the missing interrupt handleris displayed in response to an��command.


��


command.

� If block multiplexing is enabled, control register��

is set to��.

� If block multiplexing is disabled, control register ��

is set to��.


��

Explanation: The��command was issued and��

status is displayed.


��

Explanation: Because MPST was running when the� ��



��

Explanation: Because MPST was running when the� ��



MSAE221 MSAE225


��

Explanation: The LMU(2) is not online.

Solution: Correct the problem and reissue the��[�]command.

��

Explanation: The��[�] command just issued has completed.

� If the LMU(2) device is successfully accessed, the�� is the device address and the device type.

� If the LMU(2) device has been varied offline, the ��

is��.


��

Explanation: An LMU(2) device was already defined. The��[�] command just issued was ignored

Solution: Enter an��[�]�� command and then an��[�]��command to change the LMU(2) devices.

��

Explanation: Because MPST was running when the��[�]command was issued, the command was ignored.


��

Explanation: Because MPST was running when the��



MSAE226 MSAE232


��

Explanation: A��command was issued but no printeris configured.

Solution: Enter the��command to assign a printer; then,reissue the�� command.

��

Explanation: A��command was previously issued buthas not yet continued processing. The second��

command is ignored


��

Explanation: A��command was issued, but the printdevice assigned (using the��command) is not valid. To use��the printer type must be a 1403, 3203, or a 3211.

Solution: Enter the��command to assign a printer; then,reissue the�� command.

��

Explanation: A� ��command was issued while MPST wasnot running and the command was ignored.


��

Explanation: A� ��command was issued and MPSTterminates as soon as the command is detected. The exact timethat MPST terminates depends upon the function currentlyexecuting.


MSAE233 MSAE236


��

Explanation: A second��command was issued whileMPST was running and the command was ignored.


��

Explanation: A��command was entered and the mainprogram was not running.


��

Explanation: A��command is pending and awaitsprocessing by the main program.


��

Explanation: A��command was entered and theprevious command is still pending.

Solution: Re-enter the��command.

MSAE237 MSAE245


��

Explanation: A�� command was entered and the mainprogram is stopping.


��

Explanation: A��command was issued while MPSTwas not running and the command was ignored.


��

Explanation: MPST was cancelled by either a��

command or by an MPSTSAE abend processing


��


��command.

� ��—The binary device number assigned to thesubchannel.

� ��—The subchannel id (SID).

� ��—The channel path identifiersdefined for this subchannel.


MSAE246 MSAE252


��


��command. ��is the subchannel identification and��

is the condition code for the store subchannel (STSCH)instruction. If the code is��, the subchannel information blockis displayed following this message.


��


��command.


� �� —The subchannel id (SID).


��

Explanation: A�� printer��command was issuedwhile MPST was running and the command was ignored.MPST cannot be running when the�� command is issued.

Solution: Stop MPST operation and reissue the��command.

��

Explanation: A�� printer��command was entered butthe printer was already defined.


MSAE253 MSAE255


��

Explanation: An I/O error has occurred during printerdefinition.

� �� —The device address.






��

Explanation: While attempting to verify that the printer devicewas operational, an I/O error occurred. The��printer��command fails.


��

Explanation: The printer device is offline (SIO conditioncode=3).

Solution: Correct the problem and reissue the��command.

MSAE256 MSAE259


��

Explanation: The last�� command was successfullyprocessed.

� If the print device is successfully accessed, the �� isthe device address and the device type.

� If the print device was varied offline, the �� is ��.


��

Explanation: A��command was issued but no printer isconfigured.

Solution: Use the��command to assign a printer; then,reissue the��command.

��

Explanation: The entry, specified in the��command, hasbeen logged on the printer.


��

Explanation: This message is issued in response to a��command.


MSAE260 MSAE263


��

Explanation: A�� command was issued but no printeris configured.

Solution: Use the�� command to assign a printer; then,reissue the��command.

��


��command. The current Julian date and the time is displayed.


��


��command when MPST is not running. The current Julian dateand the time is displayed.


��

��

��

Explanation: This message is issued either in response to a��command or as a result of a��command.MPST is currently running and the current state of any testdevices opened by MPST is shown.

� �� —The device address.

� �� —The volume serial number.

� �� —The number of I/O operations completed on thedevice.

MSAE264 MSAE264


� � � ��—The number of SIO, SIOF, or SSCH instructionsdone to the device.

� � �� —The number of SIO or SIOFinstructions that received channel busy.

� � �� —The number of SIO or SIOFinstructions that received control unit busy.

� � �� —The number of SIO or SIOFinstructions that received device busy.

� �� —�� is the last status received byMPSTSAE for the test device. �� could be:

� �� —Device busy (CC=1 with BUSY) on the lastSIO.

� ��—An I/O operation was started and channel endand/or device end status was not received.

� ��—Channel busy (CC=2) on the last SIO.

� ��—Control unit busy (CC=1 with STM andBUSY) on the last SIO.

� ��—No I/O operation is in progress or pending.

� ��—The device is not ready.


��


��command. If any reply messages are outstanding, the replyID number and the text of the message are displayed.


MSAE265 MSAE268


��

Explanation: A��command was issued and the devicewas not available. The��the device was not available:

� ��

� ��

� ��

� ��


��

Explanation: A�� (write tape mark) command was issuedand the device was not available. The��the device wasnot available:

� ��

� ��

� ��

� ��


��

Explanation: Display monitor has started.


��

Explanation: Display monitor has stopped.


MSAE269 MSAE272


��

Explanation: A�� command, specifying anMPSTSAE device, was issued. �� does not traceMPSTSAE devices and the command is ignored.


��

Explanation: The�� command was issued to anundefined device. �� will begin tracing all I/O to thisdevice once it has been defined.


��

Explanation: This message is issued in response to anMPSTSAE��command.


��


��command.

� ��—The CSECT name.

� ��—The offset into the CSECT.

� ��—The verify or replace data.


MSAE274 MSAE275


��

Explanation: The message issued as part of the “MAP DATA”storage display. ��is the address of the main storage data,�� is the data in hex, and �� is the data in a printableformat.


��


��command when no devices are defined.


MSAE276 MSAE281


��

��


�command. The current test device definitions are listed.

� ��—The DD name for this device definition.

� ��—The processor and device address.

� �� —The device type.

� ��—The DD card type.

� ��—The volume serial number of the DASD or tapevolume mounted on the device.

� ��—The 1–44 character data set name or*NONE*.

� ��—The first track of the test data set, if DASD,specified as cccc.hhhh (c=cylinder, h=head).

� ��—The last track of the test data set, if DASD,specified as cccc.hhhh (c=cylinder, h=head).

� ��—The number of tracks in the test data set.


��

Explanation: An invalid command (��) was entered and thecommand was ignored.


MSAE282 MSAE291


��

Explanation: This message is issued when a��commandwas entered without a selection parameter. The menu for��

follows the first line of this message. This message is followedby message��.


��

Explanation: This message is issued when a��commandwas entered without a selection parameter. This message ispreceded by message��.

Solution: Refer to message��and enter the desired helpselection or�� to terminate the��command.

��

Explanation: The help selection, chosen when responding tomessage��, follows this message.


��

Explanation: A previous��command is still beingprocessed. The��command just issued was ignored

Solution: Enter the� ��command to display theoutstanding Help selection reply messages.

��

Explanation: An invalid parameter (��) was entered or arequired parameter was omitted and the entire command wasignored.

Solution: Enter��and correct the problem.

MSAE292 MSAE295


��

Explanation: A��command was issued but device��

has not been configured and the command is ignored.


��

Explanation: A��command was issued but nointervention required condition exists for device��and thecommand is ignored.


��

Explanation: In response to a��command device endwas posted for device��.


��


��command. An entry for each configured CPU is shown.

� ��—The number of the CPUs.

� �� —The one second BCT count in hex.

� ��—The CPU address in hex.

� ��—The CPU id data.

� ��—The internal MPSTSAE flags.

� ��—The address of the prefix storage area (PSA) forthe CPU.


MSAE296 MSAE302


��

Explanation: A command to assign a device (�� , ��, etc.)was entered and that device address is already in use.

Solution: If possible, assign a different address to the device.

��


�command.

� ��—The size of the CPU real memory.

� � ��—The area MPST uses.

� �� and ��—The boundaries of the data area (D/A)MPST uses.

� —The fixed task.

� �� —The size of each fixed task area.


��

Explanation: This message displays the return code from the��command entered while running VM/370.


��

Explanation: If no devices were defined, this message is issuedduring the device definition phase of��commandprocessing


MSAE303 MSAE303


��

��

Explanation: This message is issued during the devicedefinition phase of the��command The current test devicedefinitions are listed.

� ��—The DD name for this device.

� �� —The processor and device address.

� ��—The IBM device type.

� �—The DD card type (0–6).

� �� —The volume serial number of the DASD or tapevolume mounted on the device.

� ��—The 1–44 character data set name or*NONE*.

� �� —The first track of the test data set, if DASD,specified as cccc.hhhh (c=cylinder, h=head).

� �� —The last track of the test data set, if DASD,specified as cccc.hhhh (c=cylinder, h=head).

� �� —The number of tracks in the test data set.


MSAE304 MSAE305


��

Explanation: This message follows either message��

or��.


� �to edit (delete or add) existing test device definitions.

� ��to prompt the operator for each new entry.

� ��to delete all current device definitions and enter newdefinitions.

� ��to use the current device definitions.

��

Explanation: This message displays the format in which a testdevice definition is entered.

� ��—the DD name for this device (UUT01 – UUT08).

� ��—the channel path id ( �) and the device address(��). The CHPID is optional.

� �� —the IBM device type.

� �� —the device definition type (0–6).


MSAE306 MSAE311


��

Explanation: This message requires a response.


� Test device definition��.

� ��to terminate the device definition entry.

��

Explanation: The last test device definition was rejected.

Solution: The message preceding this one explains the reasonfor the rejection.

��

Explanation: Test device definition��was accepted byMPSTSAE.


��

Explanation: The last test device definition contained aninvalid DD name.

Solution: Correct the DD name.

��

Explanation: The last test device definition contained aninvalid device address.

Solution: The device addresss must be 3 or 4 hexadecimalcharacters and the process address must be 0–3.

MSAE312 MSAE321


��

Explanation: The last test device definition contained aninvalid device type.

Solution: The device type must be a valid IBM device type:2305–2, 3330–1, 3330–11, 3350, 3380, 3420, TAPE, 3480,3490, 3590, 4420, 1403, 3211, 3203, 3800, 4245, 4245, 4248, or��.

��

Explanation: The last device definition contained an invalidDD type.

Solution: The DD type must be a single digit from 0–6.

��

Explanation: The last test device definition contained aduplicate DD name from a previously defined DD card ordevice. The DD name cannot be� � ��,� � �,� � ��, � ��, or� � ��.


��

Explanation: A duplicate device address was specified duringthe device definition phase. The device address cannot be theaddress of MPSTSAE, IPC, console, SYSIN, or print device.


��

Explanation: A� � ��command was issued for the testdevice during device definition. This information is displayedfor each configured processor of a multi-processor system.



MSAE322 MSAE323




� �� —The sense data (if unit check is �� in theunit status).


��

Explanation: MPSTSAE is running on a multi-processorsystem and the CPU address hasn’t been specified for the testdevice definition.


� �, �, �, or � to specify the CPU address.

� ��to request the��command (message��).

� �to cancel the device definition.

��

Explanation: This message is issued during deviceconfiguration when MPSTSAE is operating in XA mode. Thebinary device number is assigned to SID.


� � ��—The subchannel id (SID).


MSAE324 MSAE325


��

Explanation: A��command was issued to device addrduring device configuration. This information is displayed foreach configured CHPID for the device when MPSTSAE isoperating in XA mode.

� ��—The channel path identifier.






��

Explanation: MPSTSAE is operating in XA mode and theCHPID was not specified for a test device definition.

Solution: Respond to the message, enter one of the following:

� The channel path identifier to be used (it must be one ofthe id’s displayed in message��).

� � �to specify all defined channel path identifiers for use.

� ��to request the��command (message��).

� ��to cancel the device definition.

MSAE331 MSAE333


��

Explanation: The device definition editor is active.

� If you responded��(edit) to message� ��, themessage is “�� ...”

� If you responded��(prompt) to message� ��, thebracketed messages are displayed.

Solution: Respond to the message.

� For the message “�� ...” respond

� ��to add an additional test device definition to theexisting set of device definitions.

� ��to delete a current test device definition.

� ��to have the default test devices listed.

� ��to terminate the device definition editor.

� For the bracketed messages respond to the individualprompts.

��

Explanation: The maximum number of device definitions (8)are already defined. No additional test device definitions areallowed.

Solution: Delete one or more existing device definitions beforeadding additional test device definitions.

��


Solution: Enter device definitions.

MSAE334 MSAE338


��

Explanation: The test device definition added using the devicedefinition editor was accepted.


��

Explanation: The test device definition being added by thedevice definition editor was rejected.

Solution: The message preceding this one explains the reasonfor the rejection.

��


Solution: Enter the DD name or the device address of the testdevice to be deleted.

��

Explanation: Either the DD name or the device address enteredin response to message��is not currently defined. Notest device was deleted.


��

Explanation: The test device definition (��, ��) wasdeleted from the currently defined test devices.


MSAE339 MSAE342


��

Explanation: The response to message�� was��.


� To select a default DD set, enter the DD set number (00through 10).

� To display all of the default DD sets, enter��.

� To display the details for a DD set, enter��. ��is the number of the DD set.

� To terminate default DD set selection, enter��.

��

Explanation: The response to message�� requested DDset��. The DD set was either not found or was empty.

Solution: Select a different DD set.

��

��

��

Explanation: The response to message�� was�� .The available DD set numbers are displayed.


��

Explanation: The response to message�� was� ��. The details for DD set��are displayed.


MSAE381 MSAE400


��

Explanation: Processing has started on the device definitionphase of the MPSTSAE��command


��

Explanation: Processing has ended on the device definitionphase of the MPSTSAE��command


��

Explanation: MPST execution began on �� at�� .


��

Explanation: MPST completed execution on �� at�� with a return code of��.


��

Explanation: The��requires��(million) bytesof memory to run.

Solution: Increase the size of the virtual machine to��bytes.

��

Explanation: Insufficient main storage was available for thetables associated with the processing of type 2 DD cards.

Solution: If you are running MPSTSAE under VM/370,increase the storage size of your virtual machine.

MSAE401 MSAE404


��

Explanation: An invalid extent description was found in theDSCB at �� while processing a type 2 DD card.MPSTSAE treats this pack as if no free space was available.

� ��—The four digit cylinder address.

� ��—The four digit head address.

� ��—The two digit record address.


��

Explanation: An I/O error occurred when MPSTSAEattempted to read the volume label of a CKD DASD test device.The volume label is cylinder 0/head 0/record 3. The messagepreceding this one (��) describes the error.

Solution: Refer to message ��. Enter��to ignore themessage and continue,��to retry the operation, or��to cancelthe function attempting to use the device.

��

Explanation: The volume mounted on the CKD DASD devicebeing configured does not contain a volume label record oncylinder 0/head 0/record 3. The label record must have a 4-bytekey field containing ’VOL1’ and an 80-byte data field startingwith ’VOL1’.


��

Explanation: The volume mounted on the CKD DASD devicebeing configured does not contain a valid VTOC format 4 DSCBon the first record of the VTOC.


MSAE405 MSAE409


��

Explanation: MPSTSAE has determined that the test data setextent limits are invalid.

Solution: Redefine the starting track and the size of the testdata set to be within valid cylinder and head limits for the testdevice.

��

Explanation: An I/O error occurred reading the VTOC.Allocation of the test device fails.


�� !��

Explanation: Zero tracks are allocated for DD types 3, 4, or 6.DD types 3 or 4 must have one or more tracks allocated forMPSTSAE.


��

Explanation: Either the type 3, 4, or 6 data set does not exist orthe format 1 data set control block (DSCB) for the data set isinvalid.


��

Explanation: The volume mounted on the test device musthave a valid VTOC to locate a DD type 3, 4, or 6 data set.


MSAE410 MSAE412


��

Explanation: The CKD DASD volume being configured doesnot have any unallocated tracks. If the volume has a valid labeland VTOC, only DD types 0, 1, 3, 4, and 6 are allowed. If thevolume does not contain a valid label or VTOC, DD types 0, 1,2, 3, 4, and 6 are allowed.


��

Explanation: If DD type 2 is used, the reply to this messagedetermines the type and amount of space allocated byMPSTSAE to the test data set.


� ��to allocate one or more full cylinders of space.

� ��to allocate one or more tracks of space.

� ��to allocate one or more specific tracks.

� � ��to have MPSTSAE display a list of the free spaceavailable.

� ��to cancel the device definition in progress.

��


reply to message��.

Solution: Enter either the number of cylinders to allocate (� to��) or��. If there is no VTOC and the reply is��, theentire volume is allocated.

MSAE413 MSAE416


��

Explanation: This message is issued in response to a�� or��reply to message��.

Solution: Enter the number of tracks to allocate (� to ).

��

Explanation: This message follows message��if thereply to message��was��.

Solution: Enter the starting cylinder and head number for thespace requested.

��

Explanation: The requested DASD space is not available.

� If the volume mounted on the test device has a validVTOC, message��is repeated.

� If the volume mounted on the test device does not have avalid VTOC, message��is issued.


�� "�#$��"��"��!�� "!�� "��"��



� Enter�"�to force the allocation of the space requested.

� Enter��to cancel the test device definition in progress.

MSAE417 MSAE421


��

Explanation: This message follows message��if thereply to message��was�� and the reply to message��was��.

Solution: Enter the starting cylinder and head number in hexfor the space requested.

��

Explanation: This message follows message��if thereply to message��was��and the reply to message��was��.

Solution: Enter the starting cylinder number in hex for thespace requested.

�� !��


reply to message��.


� Enter��to list the next 14 extents of free space.

� Enter��to reissue message��.

�� !�� !�

Explanation: An I/O error occurred when MPSTSAEattempted to read the volume label of a tape test device. Thevolume label, for either IBM or ASCII, is the first record on astandard labeled (SL) tape. The message preceding this one(��) describes the error.

Solution: Refer to message �� and reply to ��:

� Enter��to ignore the error and continue.

� Enter��to retry the I/O operation.

� Enter� �to cancel the test device definition in progress.

MSAE422 MSAE425


��

Explanation: Customer data on the test device may bedestroyed. This message precedes message��.

Solution: Refer to message��.

��

Explanation: This message follows message��andrequires a response.

Solution: Refer to message��and reply to��:

� To write on the test device, enter “oktowrite”.

� Any reply other than “oktowrite” cancels the test devicedefinition in progress.

��

Explanation: The VTOC of the CKD DASD volume beingconfigured contains errors. DD type 2 is not allowed if theVTOC cannot be read without errors.


��

Explanation: The VTOC of the CKD DASD volume beingconfigured has indicated that there are no unallocated tracks. Atype 2 DD card is not allowed unless there is at least oneunallocated track.


MSAE426 MSAE441


��

Explanation: The VTOC of the CKD DASD volume beingconfigured is being scanned to determine the location andquantity of free space (unallocated tracks) on the volume. Theamount of time the scanning takes is determined by the size ofthe VTOC.


��

Explanation: The reply to message� ��was incorrect.Message� ��is repeated

Solution: Respond to message� ��.

��

Explanation: During configuration a��command is issued to the device beingconfigured. Either the command failed or the characteristics arelisted.

Solution: If the command failed, check the device.

�� or��

Explanation: MPSTSAE requires the data set name, of apreviously allocated data set, to test.


� For DD type 3, enter the data set name (which must beginwith ��) or ��to accept the default.

� For a DD type 4, enter the data set name (which mustbegin with �� or ��to accept thedefault.

MSAE442 MSAE446


��



� ��to ignore the error and continue.

� ��to retry reading the label.

� ��to cancel the operation in progress.

��



� ��if the volume does not have a label.

� ��if the volume does have a label.

��



� ��if the volume does not have a VTOC.

� ��if the volume does have a VTOC.

��

Explanation: Start and end block numbers are invalid.

Solution: Re-enter start and end numbers.

��

Explanation: The VTOC has an invalid format 5 DSCB (dataset control block) and no free space can be found.

Solution: Use a different DASD device.

MSAE447 MSAE451


��

Explanation: A DSN (data set name) was entered and no tracksare allocated.

Solution: Use a different DSN.

��

Explanation: A DSN (data set name) was entered and it waseither not found or bad.

Solution: Use a different DSN.

��

Explanation: A DD type of 3 or 4 was entered and the DASDdevice does not have a label or a VTOC.

Solution: Use a different DASD device.

��

Explanation: The free space on a pack is listed for first, last,and number of entries.


��

Explanation: DD type 6 has been allocated. Only read accessis allowed.

Solution: Enter the full data set name of any previouslyallocated data set.

MSAE452 MSAE456


��



� The number of blocks.

� ��to specify all available blocks.

� ��to display message��.

��

Explanation: An I/O error occurred when MPSTSAEattempted to read a data set control block (DSCB) on the volumemounted on an FBA DASD test device.


� ��to ignore the error and continue.

� ��to retry the I/O operation.

� �to cancel the test device definition in progress.

��

Explanation: The space requested is not available. If there isany space available, message��will be displayed.


��

Explanation: The space requested is not available and there isno free space.


� ��to force space allocation.

� ��to not force space allocation. If you enter��, the devicewill not be allocated; choose a different device.

MSAE457 MSAE491


�� !��

Explanation: An FBA device is being allocated.

Solution: Enter the first block number to allocate.

�� "��!��$�%&��! �� "�� !� ��!�� !��

Explanation: If��and��are the same volume, thesame space on the same disk volume has been allocated fromtwo different paths and causes overlapping space allocations.


� $�to not accept the device definition.

� ��to accept the device definition.

�� "��

Explanation: The same space on the same disk volume hasbeen allocated from two different paths and the device definitionis not accepted.

Solution: Refer to message��.

�� #�� $��!�� "�� !��!� �� $� ��"�� !��

Explanation: Test device definitions using DD types 0, 2, and5 require the test device to be online only to the system (orVM/370 virtual machine) MPSTSAE is executing on. If the testdevice is online to more than one system, customer data can bedestroyed. Multiple systems could attempt to write/read data atthe same time to the same DASD cylinder and head location orthe same tape volume.

Solution: Reply to message��.

MSAE492 MSAE492


��



� ��if the test device being defined is known to be offline toall other systems.

� ��if the test device being defined is known to be online toother systems.

MSAE493 MSAE494


��

Explanation: An I/O error has occurred during MPSTSAE testdevice definition.





� � ��—The cylinder and headaddress and the record number (if DASD).

� ��—The sense data (if unit check is � in theunit status)


��

Explanation: An I/O error occurred when MPSTSAEattempted to read a data set control block (DSCB) on the volumemounted on a CKD DASD test device. The message precedingthis one (��) describes the error.

Solution: Refer to message��and reply to��:




MSAE495 MSAE498


��

Explanation: An I/O error occurred when MPSTSAEattempted to do a� � ��command on the test device. Themessage preceding this one (� ��) describes the error.

Solution: Refer to message�� and reply to�� :




��

Explanation: An I/O error occurred when MPSTSAEattempted to do a NOP command to the test device. Themessage preceding this one (� ��) describes the error.

Solution: Refer to message�� and reply to�� :




��

Explanation: This message displays the volser and the VTOClocation.

� ��—The volume serial number.

� ��—The location (cylinder, head and record)of the volume table of contents for the configured testdevice.


MSAE499 MSAE803


�� or� ��

Explanation: A��command (XE4) is issued to eachMPSTSAE test device during test device definition. The datareturned by this command is displayed in this message.

� ��—The control unit type.

� ��—The control unit model.

� ��—The device type.

� ��—The device model.


��

Explanation: This message indicates a program error inMPSTSAE or MPST.


��



��



MSAE804 MSAE807


��

Explanation: MPSTSAE or MPST is attempting to use thedevice at address��and the device is not online.

Solution: Correct the problem and enter on of the following

� ��to retry MPSTSAE or MPST operation.

� ��to cancel MPSTSAE or MPST operation.

��

Explanation: There is insufficient storage available to do anI/O to a device.

Solution: Increase the amount of main storage available toMPSTSAE or run MPSTSAE on a larger system.

��

Explanation: An MPSTSAE or MPST function is attemptingto access a tape device. The file number specified is invalid.

Solution: If the tape file number was obtained from anMPSTSAE reply message or an MPST function control card,re-execute the function and specify a valid tape file number.(Normally, tape file numbers range from 1 to 99.)

��

Explanation: An I/O error occurred on UCB��duringprint configuration.

Solution: The message preceding this one (��) describesthe error.

Solution: Reply to the message, and enter one of the following:

� ��for retry.

� ��for cancel.

MSAE808 MSAE809


��

Explanation: A permanent I/O error has occurred and theMPSTSAE or MPST function using the failing device iscancelled. The message preceding this one (��) describesthe error.


��

Explanation: An I/O error has occurred.

� �� —The CPU number.





� ��—The cylinder and headaddress and the record number (if DASD).



MSAE810 MSAE902


��



��



��

Explanation: An incorrect PA or PF key; other than PA1, PA2,PF1, and PF2; was used. The message appears on the input lineof a 3277, 3278, or 3279 console device.

Solution: Use the correct PA or PF key or type an MPSTSAEcommand over this message.

��

Explanation: The screen is full and there are one or moremessages waiting to be displayed. The message appears on theinput line of a 3277, 3278, or 3279 console device.

Solution: Press the PA1/PF1 or the PA2/PF2 key:

� If the PA2 or the PF2 key is used, MPSTSAE clears thescreen and leaves the console in FRAME mode.

� If the PA1 or the PF1 key is used, MPSTSAE clears thescreen, places the console in ROLL mode, and continues.

MSAE903 MSAE905


��

Explanation: The first non-blank character of the lastMPSTSAE command entered was��, and that reply number isnot currently outstanding.

Solution: Enter the��command to display thecurrent, outstanding reply number.

��

Explanation: The first non-blank character (��) of the lastMPSTSAE command entered was ignored because theMPSTSAE internal command buffer is full.

Solution: Reissue the rejected command after MPSTSAE hasprocessed the queued commands in the internal buffer.

��

Explanation: The data entered was more than the maximumline length of 72 bytes.

Solution: Re-enter the data or accept a truncated line.

MSAE940 MSAE940


��

��

Explanation: A��command has been specified andthis message displays on an SIO, SIOF, or SSCH.

� � —The device being traced.


� ��—The channel address word (370 mode), or thechannel program address (XA mode).

� �� —The address in main storage.


� ��—The channel status word, if condition code 1 wasposted on start.

� ��—The CCW chain and up to 48 bytes of data perCCW.

� �� —Any hex data.

� �� —There were more than 48 bytesof data and only the first 48 bytes are displayed.

Note: Under XA the entire ORB is also displayed.


xxxxxxxx

MSAE941 MSAE941


��

��

��

��

Explanation: A��command has been specified. Thismessage is printed because an interrupt has occurred. Under XAthe entire IRB is also displayed.

� ��—The device being traced.


� ��—The channel status word, if condition code 1 wasposted on start.

� ��—Any hex data.

� ��—The CCW chain and up to 48 bytes of data perCCW.

� �� —The address in main storage.

� Possible�� are:

� �� —The suppressincorrect length (SLI) flag was�� in this CCW.Since this was not the last CCW in the chain that wasexecuted, it is impossible to determine exactly howmuch data has been transferred.

� �� —There are more than 48bytes of data. Only the first 48 bytes are displayed.

� �� —The suppress transfer(skip) flag was�� in this CCW. No data has beentransferred.

� �� —Because the residual bytecount (RBC) in the CSW is the same as the bytecount in the CCW no data has been transferred.


MSAE942 MSAE952


��

Explanation: Message��indicated a unit checkcondition and MPSTSAE issued a sense command to theaddressed device. This �� displays the sense information.


��

Explanation: The print queue is full and at least one messagehas been lost, but no MPST output is lost.

Solution: The probable cause of this problem is the printer. Ifpossible, correct the problem.

��

Explanation: An invalid device type is configured as theprinter device.


��

Explanation: An I/O error has occurred on the printer device.

� �� —The CPU number.

� �� —The printer device address.

� � ��—The ECB completion code.





MSAE953 MSAE954


��

Explanation: An unrecoverable I/O error has occurred on theMPSTSAE printer output device. The MPSTSAE print task hasturned��parallel print to route all output messages to theconsole device. The message preceding this one ( ��)describes the error.

Solution: To restart hard copy printing, correct the problemwith the printer output device or use another printer.

Note: The printer output device cannot be varied on more thanonce. Vary the printer output device offline and then vary theprinter (back) online.

��

��

��

Explanation: A��command was issued. This messageprints the UCS loaded (��) and tests the ability of the printeroutput device to skip to the top of the form and to space properlyfor single, double, and triple space.


xxxxxxxx

MSAE955 MSAE956


��

Explanation: A��command was processed.

� For 1403 printers, the UCS name loaded replaces��

and the third line is not printed.

� For 3211/3203 printers, this message is issued in responseto either:

� ��with no parameters (used to display currentbuffer contents), or

� ��loading the values displayed into thebuffers.


��

Explanation: A��command was processed for a 6100printer output device. The command sequence��

� �� was issued and completedsuccessfully. The default WCGM and translate table have beenloaded. A default FCB has been loaded matching the paperlength setting on the operator’s panel.


327 Index

Index

AABEND Codes, 2

Abnormal End Codes, 2

Attention Interrupt, 61

CCCWtrace, 15

Channel Command Word Trace, 15

CKDMAP, 19

Control Card Editor, 5

Count–Key–Data Map, 19

DDEFINE, 47

GGenerate Stand–Alone Programs, 53

GENSAPGM, 53

LLIBLOOK, 109

LIBMOUNT, 91

Library Look, 109

Library Mount Function, 91

Library Storage Module Exerciser, 63

LSMEXER, 63

MMPST Main Processing, 117

MPST Stand–alone Executive, 263

MPSTCCE messages, 5

MPSTCCW messages, 15

MPSTCKM messages, 19

MPSTCPY messages, 25

MPSTDEF messages, 47

MPSTGSA messages, 53

MPSTINT messages, 61

MPSTLEX messages, 63

MPSTLIB messages, 91

MPSTLOC messages, 109

MPSTMAIN, 117


MPSTMAN messages, 117

MPSTRLB messages, 129

MPSTSAE, 263

MPSTTIP Messages, 151

MPSTTMC messages, 171

MPSTTRK messages, 157

MPSTTSC messages, 177

MPSTVSC messages, 201

MPSTVTM messages, 219

MPSTWRC messages, 223

MPSTWRD messages, 251

MSAE messages, 263

RRandom Locate Block, 129

Return Codes, 1

RLB, 129

SStand–alone Executive, 263

TTape Copy, 25

Tape Independent Protocol Set, 151

Tape Monitor and Control , 171

Tape Scan, 177

TAPESCAN, 177

Terminal Control Unit Verification, 219

TIPS, 151

TMC , 171

Track Dump, 157

TRKDUMP, 157

VVOLSCAN, 201

Volume Scan, 201

VTERM, 219

WWRCART, 223

WRDISK, 251

Write–Read Cartridge, 223

Write–Read Disk, 251

Reader’s Comment Form

Manual Name: MPST Messages & Codes Manual, Version 2.04 PN: 112151207

Please check or fill in the items: adding explanations/comments in the space provided.

Which of the following terms best describes your job?

� Field Engineer � Manager � Programmer � Systems Analyst

� Engineer � Mathematician � Sales Rep. � Systems Engineer

� Instructor � Operator � Student/Trainee � Other (explain below)

How did you use this publication?

� Introductory text � Reference Manual � Student/Trainee � Instructor text

� Other (explain)

Did you find the material easy to read and understand? � Yes � No (explain below)

Did you find the material organized for convenient use? � Yes � No (explain below)

Specific criticisms (explain below):

Clarifications on pages

Additions on pages

Deletions of pages

Errors on pages

Explanations and other comments:

Note: Staples can cause problems with automated mail sorting equipment. Please use pressure sensitive orother gummed tape to seal this form. If you would like a reply, please supply your name and address on thereverse side of this form.

Thank you for your cooperation. No postage stamp is necessary if mailed in the U.S.A.

FOLD HERE AND TAPE DO NOT STAPLE FOLD HERE AND TAPE

NO POSTAGENECESSARY

IF MAILEDIN THE

UNITED STATES

FIRST CLASS MAIL PERMIT NO. 2 LOUISVILLE, CO

BUSINESS REPLY MAIL

POSTAGE WILL BE PAID BY ADDRESSEE

MANAGER, WWCS STRATEGIC TOOLSSTORAGE TECHNOLOGY CORPORATION

ONE STORAGETEK DRIVELOUISVILLE CO 80027–9984

If you would like a reply, please print:

Your Name:

Company Name:

Street Address:

Department:

TO COMPLY WITH POSTAL REGULATIONS, FOLD EXACTLY ON DOTTED LINES AND TAPE (DO NOT STAPLE)

MS 4361

CU

T A

LON

G T

HIS

LIN

EC

UT

ALO

NG

TH

IS L

INE

multi-platform subsystem test - oracle · 2010-12-29 · multi-platform subsystem test messages and...

Documents