Home

(MSP) Configuration and Administration Guide

1. Affinity Separation 2 0 0 0 eect cence eens Affinity Head Of Chain 0 20 0 cece eens User Policy Influence on Affinity Separation 0 000000 eae Drive Prioritization tia a A aa Miele Reg A te Ges Deferring Mounts a laa E ar es Library Subsystem Selection 0 c cece eee teen eee Chapter 5 SMC Message Handling oo0 oooooorcrannaan OVETVICW ii a A ds iia a User Directed Message Handling 0 cece eens Message Handling Policies 2 0 0 ccc eee ene ees MSP POLICIES vaste d taeda Noga hs bia Glos ane ot eae ot diac a ey SMC Policies ita nba fod ded Rede ah Gellert sal are aah ak Tape Management System Support 0 0 cee eee ence SMC Swap Processing 0 0 aa a tenet nen n ens HSC Mount Related Messages 0 0c cece cece eee eens Managing HSC Mounts from the SMC Client 02 0 00 00 eee Chapter 6 Commands and Control Statements 000 cece eee eee OVELVICW 52 ay bhi ey ee rat BOS Ah ate Oe Retard al Mal at Sad ay Rha aa Issuing SMC Commands ccc ccc eee en ene nes Issuing SMC Commands Using the MSP Modify Command Issuing SMC Commands Using the SMC Command Prefix Specifying SMC Commands in the SMCPARMS or SMCCMDS Data Set vi SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B 17 18 19 19 21 21 22 23 25 27 27 28 28 28 28 29 30 30 31 32
2. The client communication monitor subtask feature provides periodic validation of active communication paths for all non disabled TapePlexes This feature is enabled using the MONitor parameter on the TCPip command Chapters 2 6 Support for the Sun StorageTek T10000 and T10000B tape drives Chapter 6 Appendix B Support for the Sun StorageTek T9840D tape drive Chapter 6 Appendix B Message changes and additions Chapter 9 Revision A The SMC TAPEREQ control statement replaces the HSC TAPEREQ control Chapter 6 statement Appendix B The SMC TREQDEF operator command replaces the HSC TREQDEF command and control statement Chapters 3 6 The new SMC UNITATTR command replaces the HSC UNITDEF command Chapters 3 6 and UNITATTR control statement It is used to set the model type for nonlibrary Appendix B drives and IGNORE as the model type for drives to be excluded from allocation The requirement has been removed for the SMC to be initialized before the HSC Chapter 3 The new SMC DRIVEMAP command allows you to map device addresses used on the HSC server to the addresses used on the SMC client Chapters 2 6 The new SMC LOG command allows logging of XML payloads sent and or received to local and remote library subsystems and servers Chapter 6 What s New xiii 312614001 Rev B The new SMC MOUNTDEF command is used to specify message handling and mount dismount policies
3. About this Guide xix 312614001 Rev B Single Optional Choice If the first item is positioned on the line below the base line a single choice of items in the stack is optional Defaults Default values and parameters appear above the base line In the following example if a value is not specified with the command the Default Value is used Default Value Some keyword parameters provide a choice of values in a stack When the stack contains a default value the keyword and the value choices are placed below the base line to indicate that they are optional and the default value appears above the keyword line In the following example if the keyword is not specified with the command the Default Value is used gt Default Value keyword f vaTue2 Value3 xx SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Repeat Symbol A repeat symbol indicates that more than one choice can be made or that a single choice can be made more than once The repeat symbol shown in the following example indicates that a comma is required as the repeat delimiter Keywords All keywords are shown in uppercase or in mixed case When keywords are not case sensitive mixed case implies that the lowercase letters may be omitted to form an abbreviation Variables Italic type is used to indicate a variable Alternatives A bar is used to separate alternative parameter values Delimiters
4. Chapter 6 Commands and Control Statements 123 312614001 Rev B UNITAttr Command The SMC UNITAttr command specifies device addresses and allows the user to define the model types for nonlibrary drives This command can also be used to set MODEL IGNORE for device addresses not available for the host IEY Notes The SMC UNITATTR command replaces the HSC UNITDEF command and UNITATTR control statement It is used to set the model type for nonlibrary drives and IGNORE as the model type for drives to be excluded from allocation SMC does not support a UNITDEF command Each UNITATTR command is parsed and processed independently HSC nonlibrary and MODEL IGNORE UNITATTR statements are no longer returned to SMC on a configuration query Therefore if you use UNITAttrs to bypass devices for allocation or to define the device type of nonlibrary drives you must define these UNITATTR commands to the SMC subsystem Syntax LIst gt UNITAttr ADDRess devnun o o devnum range OFF L hodet R devnum 1ist Command Name UNITAttr initiates the UNITAttr command Parameter Descriptions ADDRess specifies the device numbers to be processed by the UNITAttr command LIst lists the UNITAttr model information for the device numbers specified by the ADDRess parameter MOdel specifies the model type of the transport to be assigned the device numbers specified by the ADDRess parameter model type indica
5. Message Level 0 Explanation During initialization the SMC subsystem detected an error System Action The SMC subsystem terminates User Response Look for SMC related messages in the SYSLOG or job log Associated messages may be but are not limited to SMC0002 SMC0004 SMC0006 SMC0008 SMC0010 or SMCOO11 Invalid format or missing keywords for the CCCCCCCC command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command CCCCCCCC that contained either too many or too few keywords in the command line System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command 146 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0023 SMC0024 SMC0025 SMC0023 SMC0025 CCCCCCCC command successfully processed at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The CCCCCCCC command was successfully validated and processed by the SMC System Action None User Response None SSSS subsystem initialization complete Message Level 0 Explanation The SMC initialization process is complete The SMC is ready to begin normal operations System Action None User Response None No CCCCCCCC control block entries to list Message Level 0 Explanation One of the following occurred e Command CCCCCCCC was specified with the LIST k
6. TAPEREQ DEVTpref Requests device preferencing for a particular allocation request The use of device preferencing is restricted to Sun StorageTek 36 track class transport models 4490 9490 and 9490EE Note The following rules apply when using the MEDia MODel and RECtech parameters in conjunction with DEVTpref e The MODel parameter must include the models specified in the DEVTpref parameter e The RECtech parameter must include valid values for each model specified in the DEVTpref parameter e The MEDia parameter must include valid values for each model specified in the DEVTpref parameter Note Device preferencing is managed by the SMC If DEVTpref is specified and the list of devices includes 36 track and other devices e g 18 track the SMC preferences 36 track drives first followed by other types in the list Refer to the SMC Configuration and Administration Guide for more information modell Specifies the transport model number of the preferred device These transports are given a higher selection probability than the alternate transport model model2 Optionally specifies the transport model number of the first alternate device It must be separated from the model by either a comma or a blank model3 Optionally specifies the transport model number of the second alternate device It must be separated from model2 by either a comma or a blank If model3 is omitted the transport model number not specified by model
7. flow diagrams conventions XiX H help technical support xxvi HSC mount related messages 54 HTTP Server description 6 messages 195 IBM International Business Machines Inc operating system messages 205 initialization SMC 21 intentionally failing a job 31 intercepted messages IBM operating system messages 205 tape management system messages 207 introduction SMC 1 J JES allocation affinity separation 44 deferring mounts 49 drive exclusion 29 drive prioritization 48 exclusion levels 32 37 intentionally failing a job 31 scratch requests 37 SMC interaction with other software 219 specific requests 32 job intentionally failing 31 L LIBrary command 76 library subsystem selection 49 library defined 2 LIst command 79 LOG command 81 M message handling SMC 51 messages 54 descriptions 140 format 139 195 HTTP server 195 intercepted 205 209 messages intercepted by HSC 205 SMC listing 141 SMC system 139 StorageTek HTTP Server 196 tape management system messages 207 utility 193 variable definitions 140 minimum exclusion level 30 Modify command MSP 58 MOUNTDef command 84 mounts managing from the SMC client 55 MSGDef command 87 MSGJob command 90 MSP START Command 25 O one local and one remote 15 one local and one remote with multiple paths 17 operator commands issuing 58 ALLOCDef 60 ALLOCJob 67 CMDDef 71 DRIVemap 73 LIBrary 76 LIst 79 LOG 81 MOUNTDef 84 MSGDef 87 M
8. library A single Sun StorageTek hardware configuration normally represented by a single HSC Control Data Set CDS Note that a library may contain multiple Automated Cartridge Systems ACSs and Virtual Tape Storage Subsystems VTSSs drive exclusion The SMC function of excluding drives for an allocation request based on SMC exclusion criteria See Chapter 4 SMC Allocation in a JES Environment for more information about this term drive prioritization The SMC function of influencing selection of a particular drive based on allocation criteria including volume location See Chapter 4 SMC Allocation in a JES Environment for more information about this term 2 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Use the following table to identify the SMC 6 1 replacement for a command control statement macro or specific parameter that was previously provided by the HSC HSC 6 0 Component Parameter SMC 6 1 Replacement Page TAPEREQ control statement TAPEREQ control statement 101 TREQDEF command and control TREQDEF command 119 statement UNITATTR control statement UNITATTR command 124 nonlibrary and IGNORE only UNITDEF command UNITATTR command 124 ALLOC command ALLOCDEF command DEFER DEFER Note Default ON 63 SPECVOL EXTVOLESOT 64 ZEROSCR ZEROSCR 64 AMPND NOAMPND MOUNTDEF command startup exec parameter AUTOPENDMOUNT 85 MNTD command MOUNTDEF command VOLWATC
9. ss amp SUN microsystems StorageTek Storage Management Component SMC MSP software Configuration and Administration Guide Part Number 312614001 Revision B Version 6 1 Sun Microsystems Inc www sun com Part No 312614001 February 2009 Rev B amp Sun microsystems Storage Tek Storage Management Component SMC MSP Software Configuration and Administration Guide Version 6 1 Copyright 2009 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A All rights reserved U S Government Rights Commercial software Government users are subject to the Sun Microsystems Inc standard license agreement and applicable provisions of the FAR and its supplements Sun Sun Microsystems the Sun logo and Sun StorageTek are trademarks or registered trademarks of Sun Microsystems Inc in the U S and other countries UNIX is a registered trademark in the U S and other countries exclusively licensed through X Open Company Ltd Products covered by and information contained in this service manual are controlled by U S Export Control laws and may be subject to the export or import laws in other countries Nuclear missile chemical biological weapons or nuclear maritime end uses or end users whether direct or indirect are strictly prohibited Export or reexport to countries subject to U S embargo or to entities identified on U S export exclusion lists including but not limi
10. 37 44 44 44 48 49 49 51 51 51 52 52 52 53 53 54 55 57 57 58 58 58 59 SMC Commands that Specify JOBname STEPname and PROCstep 59 SMC Command and Control Statement Descriptions 000 cece nee aso 60 ALEOCDef Command ta aaa as abil Heda a ead ds 60 ALLOCIob Command autista toyed ete tad wate and isa das 67 CMBPDef Command isinsi seats atte ae el hn bathe alee look ane a aes 71 DRIVemap Command omi eepe Gale siege Gast deen Gee eee ARE Wea ie a 73 LiBrary Command uta tios ara dijes beheaded 76 ElstCommand a oa 79 LOG Command 0 EE A A ea dah bab aus AAA 81 MOUNTDef Command ooo 84 MsSGDet Command d T ese Papas id 87 MSGJob Command ooo 90 READ Command ta A A Ueber PA cen tad 93 RESYNChronize Command coco 95 SER Ver COMME a Rn Py LSA Le 96 TAPEREQ Tape Request Control Statement 0 0 eee eee eee 101 PCP rp Command 2 o each a a nde Sane eda ea 112 TRace Command ii A A A ele and ea ane base eens 114 TREQDe f Commands esenee ete aes Ge A EE 119 WEXie Command sai Adel neko dial bie tae se pee hed ed trea be eae 121 UNITA Command estad etal dt helt ate ES Rita 124 USERMs COMMON A ia 126 Chapter 7 Recovery Procedures o oocooocococcccn eee eee eee eee eee 127 OVERVIEW E A anes Sea bates thing oe A erected eda Gtk E 127 SMC Recovery Procedures JES 2 0 eect teen ene e nen ens 127 Inactive SMC Active Library Subsystem 0 00 127 Active SMC Inac
11. SERVER NAME REMPATH LIBRARY SHRLIB HOST MSPB In this scenario if the HSC is active on host MSPA the SMC communicates with the local HSC as described in Scenario 1 Ifthe HSC on MSPA is inactive the SMC on MSPA communicates with the remote HSC on MSPB as described in Scenario 2 Primary And Alternate Path Selection Hierarchy To A Single Library With A Local Path The path utilized by the SMC in this scenario 1s dependent upon the following factors e Whenever a local path is enabled to a library the SMC attempts to use it e Ifa local path to a library is not enabled or the local HSC is inactive the SMC attempts to communicate with the first defined remote SERVER path Once successful communication is established for a remote SERVER it becomes the active path All subsequent requests use the active path unless the local path becomes active or the remote SERVER path becomes unavailable e Ifaremote SERVER path becomes unavailable the SMC attempts to use the next available SERVER in the order the SERVer commands were entered In this example when HSC is active on host MSPA the SERVER path defined to MSPB is not used However if the HSC on MSPA becomes unavailable the SMC attempts to send its requests to the library using the REMPATH SERVER definition When the HSC on MSPA becomes active again the SMC automatically adjusts to use the HSC on MSPA Note See Client Server Drive Address Mapping on page 18 for additional requirem
12. The VTSS is a Sun StorageTek RAID 6 hardware device with microcode that enables transport emulation The RAID device can read and write tape data from to disk and can read and write the data from to a real tape drive RTD Virtual Telecommunications Access Method VTAM IBM host resident communications software that serves as a common interface for communications VM See virtual machine volume A tape cartridge data carrier that is mounted or dismounted as a unit volume serial number VOLSER An identifier of a physical volume W WolfCreek 9360 The high performance LSM with a smaller capacity than the standard LSM Z ZCART An extended enhanced cartridge that uses a thinner media to provide twice the capacity of the enhanced capacity ECART cartridge This cartridge has a length of 2200 feet and can be used only on TimberLine 9490EE 36 track transports Numerics 802 3 See IEEE 802 3 3270 IBM synchronous block mode half duplex terminals preferred for use with IBM 370 and related types of machine 3270 protocol A telecommunications protocol that supports networks of 327x CRTs on IBM mainframes 3274 Terminal control unit used on the ACS for processor to LMU communications 3480 IBM s 18 track half inch cartridge tape drive model 3490 IBM s 36 track half inch cartridge tape drive model 3590 IBM s newest cartridge tape drive model that support
13. UXB1 function code X XX not valid for message MMMMMMMM Message Level 4 Explanation The SMC detected that the action code returned for a message mount dismount or swap did not match the action for an SMC default message System Action All data returned by this invocation of UXO1 is ignored User Response Correct the UX01 to return a function code compatible with the message Chapter 9 SMC Messages 165 312614001 Rev B SMC0098 SMC0101 SMC0098 UX 1 drive XXXX1 does not match message drive XXXX2 using UX 1 drive Message Level 4 Explanation The device address returned from UX01 does not match the address specified in the message System Action The device address returned from UX01 is used in the message processing User Response Ensure that UX01 is functioning as desired SMC0099 Drive XXXX not a library drive Message Level 4 Explanation A user exit 01 returned a drive XXXX which is not a library or virtual drive System Action All data returned by this invocation of UXO1 is ignored User Response Ensure that UX01 is functioning as desired SMC0100 Invalid UXB1 drive XXXX Message Level 4 Explanation A user exit 01 returned an invalid drive address of XXXX which is not defined as a valid tape device on this system System Action All data returned by this invocation of UX01 is ignored User Response Correct the UX01 SMC0101 Invalid UX 1 or TAPEREQ subpool SSSSSSSSSSSSS from LIBRARY LLLLLLLL
14. and continue logging STArt specifies that logging is to be started APPend specifies that when logging is started data is appended to the current LOG file If not specified then data is added to the LOG file from the beginning of the log file and any data currently in the log file is lost APPend can only be specified when START is also specified STOp specifies that logging is to stop Current LOG settings are preserved Chapter 6 Commands and Control Statements 83 312614001 Rev B MOUNTDef MOUNTDef Command The SMC MOUNTDef command is used to control message processing 1 e mount dismount options previously controlled by the HSC MNTD command HSC input parameters and LIBGEN options These options control the automation of pending mounts delete disposition at dismount time whether messages are produced when a library volume is mounted outside the library and when mount messages are rolled off of the console Syntax gt gt MOUNTDef ON AUTOPendmount 0FF OFF DISMSCRReaT LoN L DISMSCRVSrE Lon gt rae le JE VOLWatch ON ROLLmsg OFF Command Name MOUNTDef initiates the MOUNTDef command Parameter Descriptions List optionally lists current SMC MOUNTDef settings This is the default if no parameters are specified It cannot be specified with any other parameter OFF optionally resets all MOUNTDef settings to original SMC default settings It cannot be s
15. automatically redriven IS Notes e The communication monitor subtask eliminates the need to specify the FAIL or INITFAIL parameters on the SERVer command If specified these parameters are ignored The communication monitor subtask does not attempt to re establish communication with disabled server paths See Chapter 6 Commands and Control Statements for more information about the SMC TCPip and SERVer commands Sun StorageTek HTTP Server for MSP The Sun StorageTek HTTP Server for MSP provides the middleware to allow communication between the SMC client and a remote HSC subsystem server The HTTP server executes as a separate subsystem on the MSP host where the remote HSC subsystem resides The HTTP Server is not required on a host where only the SMC is executing IS Notes Refer to the NCS Installation Guide for information about installing and configuring the Sun StorageTek HTTP server The Sun StorageTek HTTP server is also included with the Virtual Storage Manager VSM GUI product However for performance reasons it is recommended that you do not use the same instance ofthe HTTP server for both SMC server programs and VSM GUI programs To execute multiple HTTP server subsystems on a single host they must each listen on a unique PORT number Allocation and Multiple Sun StorageTek Libraries If your configuration includes multiple Sun StorageTek library systems as illustrated in Scenarios 5 and 6
16. disabled activelinactive never active Requests nnnn cCCC CCCC SERVER SSSSSSSS Server status disabledlactivelinactivelnever active Message Level 0 Explanation A LIBRARY command was issued with the LIST keyword The SMC0133 multiline message lists the library status for each library defined to the SMC subsystem Refer to the LIBRARY command for parameter descriptions Optionally if the SERVER keyword was specified the server status for all servers associated with this library is also displayed Library status indicates the status of the library e disabled indicates that the LIBRARY has been disabled by an operator command e active indicates that the last communication to this library was successful e inactive indicates that a communication path to this LIBRARY is no longer active although one was previously active e never active indicates that a communication path to this LIBRARY was never successfully established Requests indicates the total number of requests configuration volume lookup mount dismount and swap that were directed to the specified LIBRARY Ifthe SERVER keyword was specified then each server path defined for this library will also be displayed along with its status System Action None User Response None No UNITATTR specified for device XXXX Message Level 0 Explanation A UNITATTR command was issued specifying device XXXX and also specifying either the LIST parameter or the OFF p
17. for job JJJJJJJJ Message Level 4 Explanation A user exit 01 or TAPEREQ specified an invalid subpool name System Action The default subpool 0 is used User Response Correct the UX01 or TAPEREQ to specify a valid subpool 166 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0102 SMC0103 SMC0104 SMC0105 SMC0102 SMC0105 Invalid UX 1 volser VVVVVV Message Level 4 Explanation A user exit 01 returned a volume serial containing invalid characters System Action The volume serial returned by this invocation of UX01 is ignored User Response Correct the UX01 to return a valid volume serial Unrecoverable mount error on device XXXX volser VVVVVV for JOB JJJJJJJJ Message Level 0 Explanation The SMC detected a volume mount error in response to an IAT5310 message for a mount requested in message IAT5210 System Action The SMC breaks the mount loop and issues a dismount to the indicated device XXXX The job remains in the MDS VERIFY queue User Response Refer to the IAT5310 message for the cause of the mount error and take corrective action Default recording technique set for device XXXX Message Level 0 Explanation During initialization of the SMC drive table a device with an unrecognized recording technique was detected System Action A recording technique is defaulted based on the UCB device type Processing continues User Response Verify that any maintenance for new de
18. or deleted for SMC Release 6 1 New Messages SMC Messages e SMC0067 e SMC0150 e SMCO160 e SMCO170 e SMCO103 e SMC0151 e SMCO161 e SMCO171 e SMC0105 e SMC0152 e SMC0162 e SMCO174 e SMC0133 e SMC0153 e SMC0163 e SMCO175 e SMC0138 e SMC0154 e SMC0164 e SMC0192 e SMC0139 e SMC0155 e SMCO165 e SMC0193 e SMC0140 e SMC0156 e SMC0166 e SMC0226 e SMCO141 e SMC0157 e SMC0167 e SMC0147 e SMC0158 e SMC0168 e SMCO149 e SMC0159 e SMCO169 Sun StorageTek HTTP Server Messages None Changed Messages e SMC0025 e SMC0086 e SMC0123 e SMC0134 e SMC0056 e SMC0087 e SMCO128 e SMC0146 SMC0063 e SMC0094 SMC0129 SMC0066 e SMCO113 e SMCOI131 SMC0067 e SMC0122 e SMC0133 Appendix E Message Change Summary 221 312614001 Rev B Deleted Messages e SMCO114 e SMCO115 222 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Glossary Terms are defined as they are used in the text If you cannot find a term here check the index A Abnormal end of task abend A software or hardware problem that terminates a computer processing task ACS id A method used in the LIBGEN process to identify ACSs by using hexadecimal digits 00 to nn ACS See Automated Cartridge System ACS library A library is composed of one or more Automated Cartridge Systems ACSs attached cartridge drives and cartridges residing in the ACSs address Coded representation of hardware id or the des
19. performed every minute but error messages are only produced once every 10 scans An mmmm value of 0 disables all non fatal or non disabling error messages issued by the communication monitor subtask However errors resulting in the disabling of a server communication path are still issued Chapter 6 Commands and Control Statements 113 312614001 Rev B TRace TRace Command The SMC TRace command enables SMC tracing using the GTF trace facility and optionally provides a snap dump of the address space before and after control block modification STOP Warning This command may impact system performance and should be used only as directed by Sun Microsystems Software Support Syntax JOBname jobname Optional Parameters MSGHnd1r Optional Parameters rana a PROCstep procstep SNAPdump BEFOre Farrer BOTH 114 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TRace Command Name TRace initiates the TRace command Parameter Descriptions LIst optionally lists current SMC trace settings for both the SMC subsystems and SMC components by job name step name and PROC step Ifno JOBname is specified all jobs with SMC components being traced are listed If JOBname is specified only those jobs with SMC components being traced whose job name matches the specified job JOBname are listed In either case all SMC subsystem components being traced are listed This i
20. specification in the SMC Start Procedure See EXEC Statement Parameters on page 23 for parameter descriptions MSP START Command Syntax gt START smc proc name AA gt MSP START Command Parameters START or S initiates the MSP START command smc proc name indicates the name of the SMC START procedure member Chapter 3 Starting the SMC 25 312614001 Rev B Chapter 4 SMC Allocation in a JES Environment Overview This chapter describes SMC allocation in a JES environment The following topics are discussed e jobs selected for SMC allocation management e drive exclusion e affinity separation e drive prioritization e deferring mounts e multiple library subsystem support e interaction with other software IS Notes e See Appendix C for differences between SMC and NCS allocation e See for Appendix D for information about SMC interaction with other software Chapter 4 SMC Allocation in a JES Environment 27 312614001 Rev B Jobs Selected for SMC Allocation Management All I O device allocations on a JES system are examined by the SMC to determine if it should process the allocation request The SMC uses the MSP subsystem interface SSI IEFJFRQ Subsystem Function Request exit to gain control during tape allocation events The SMC takes control in the JES environment for the SSI23 and SSI24 allocation functions SSI23 Dynamic Allocation During SSI23 dynamic allocation processing the
21. 195 Message Format anesan e A Ds A AS AE A AAA SEE Ea a 195 Sun StorageTek HTTP Server Message Listing 0 cece teen ene 196 Appendix A Intercepted Messages 0 0 cece eee eee eee eee 205 Fujitsu Operating System Messages 0 cece cen tenn ene nee 205 Tape Management System Messages 0 cence eee een eens 207 CA T Messages bleached seed LGR aca eek eed Ha hie hea eee a Pe edie de bard oe lose 207 CONTROL M TAPE formerly CONTROL T Messages 00 0 ce cece eee 208 Appendix B MEDia RECtech and MODel Values 0000c cece eee eee eens 209 Media Type ME Dia iit cise eka aad A aa S 209 Recording Technique RECtech 1 0 0 0 cece tne nent enn eenee 212 MODel Type MODE caia a Goaed decd titi tes 215 Appendix C Differences Between SMC and HSC 6 0 and Below 217 Allocation Differences oooocoocooor ete nen ene nent nee n eee 217 Message Handling Differences 0 0 n ene e nen n eens 218 Appendix D SMC Interaction with Other Software 000 e eee eee eee 219 Automated Operations 0 0 0 nett e been teen teen ees 219 Open Typed stun ceieg a n a ab ia bee Pee be bee 219 SAMS DISK PMS Aves ep ioctl A Sua tie wine dress 219 MSP Security Packages oi a Sew ald Bence Melts Soh so IS 219 Appendix E Message Change Summary 02 eee eee eee eee eee 221 New Messages a ad 221 SMC MESSILES HG AA A A A nace acd athe 221 Sun StorageTek HTTP Server M
22. 25 START procedure creating 22 starting SMC 21 subsystem selection 19 support technical xxvi swap processing SMC 53 syntax ALLOCDef command 60 ALLOCJob command 67 CMDDef command 71 conventions XiX LIBrary command 76 LIst command 79 MSGDef command 87 MSGJob command 90 MSP START Command 25 READ command 93 RESYNChronize command 95 SMC EXEC Statement 23 TRace command 114 UEXit command 121 USERMsg command 126 T Tape Management Extract Utility 130 Tape Management System TMS messages 207 supported 53 TAPEREQ command 101 TCPip command 112 technical support xxvi TRace command 114 TREQDef command 119 troubleshooting xxvi U UEXit command 121 UNITAttr command 124 USERMsg command 126 utility Tape Management Extract 130 V volume serial numbers defined 205 index 235 312614001 Rev B W web site SUN xxvi worldwide offices SUN xxviii 236 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Printed in U S A Sun Microsystems Inc 4150 Network Circle Santa Clara CA 95054 USA Phone 1 650 960 1300 or 1 800 555 9SUN Web sun com Go SUN S lo microsystems ARGENTINA 5411 4317 5636 AUSTRALIA 1 800 550 786 AUSTRIA 43 1 601 26 0 BALKANS 301 6188 111 BELGIUM 32 2 704 89 83 BRAZIL 55 11 51872100 BRUNEI 65 216 8333 CANADA 1 800 422 8020 GENERAL 416 964 2001 LEARNING MANAGEMENT SYSTEM SALES TORONTO CHILE 562 372 4500 COLOMBIA 571 629 2323 Czech REPU
23. 67 C CA 1 TMS messages 207 CMDDef command 71 command prefix SMC 58 commands issuing 58 ALLOCDef 60 ALLOCJob 67 CMDDef 71 DRIVemap 73 LIBrary 76 LIst 79 LOG 81 MOUNTDef 84 MSGDef 87 MSGJob 90 READ 93 RESYNChronize 95 SERVer 96 TAPEREQ 101 TCPip 112 TRace 114 TREQDef 119 UEXit 121 UNITAttr 124 USERMsg 126 configuration scenarios SMC and a single HSC library configuration with multiple remote server paths 13 SMC and a single HSC library configuration with one local and one remote path 11 SMC and a single local HSC library 7 SMC and a single remote HSC library configuration 9 SMC with two libraries 15 17 contacting Sun Microsystems StorageTek Support xxvii conventions control statements XXiV product names xviii symbols xviii syntax flow diagrams xix typographic xviii customer support XXVI customer initiated maintenance CIM xxvil D deferring mounts 49 description HTTP Server 6 SMC 1 device preferencing 109 differences SMC and NCS 4 1 and below 217 drive exclusion 2 29 drive prioritization 2 48 DRIVemap command 73 E examples ALLOCDef command 66 ALLOCJob command 70 CMDDef command 72 DRIVemap command 75 LIst command 78 80 MSGDef command 89 MSGJob command 92 READ command 94 SMC START Procedure 22 Index 233 312614001 Rev B TRace command 117 UEXit command 123 USERMsg command 126 exclusion levels scratch request 37 specific request 32 EXEC Statement SMC 23 F
24. Administration Guide 312614001 Rev B Managing HSC Mounts from the SMC Client The SMC client server architecture provides the ability to perform management of certain mount dismount exception conditions from the client console rather than from the server console Conditions handled by the SMC include the following Displaying messages on the drive and console indicating the volume and its location for manual mounts when an LSM is offline When a drive is found to be loaded with another volume during a mount request from a job in execution the dismount is forced and the mount is automatically redriven based on the UCB outstanding mount status IEY Note When a mount or dismount message is intercepted by SMC and directed to an HSC server the SLS0107D message is not issued on the server or client When a loaded drive condition is detected by the HSC for an SMC directed dismount the HSC waits one minute for the drive to unload and then terminates the dismount If the dismount is performed as part of a mount request from the SMC the loaded drive status is returned to the SMC and the SMC then redrives the mount request if the mount is still pending e When a drive or volume is in use by another process verifying that the mount is still pending periodically retrying the request and allowing the operator to cancel or retry the request at any time e When the LIBrary WTORdest Client option is selected certain WTOR messages are not
25. B Specific Volume Request Drive Exclusion Criteria For a specific volume allocation the SMC excludes drives in order from lowest exclusion level to highest based on the criteria in Table 2 The lower the level number the more important the exclusion criteria Table 2 JES Drive Exclusion Levels Specific Request Level Specific Volume Criteria 1 For non labeled NL specific volume requests exclude all virtual drives Exclude drives incompatible with the volume media Primary source external volume label Secondary source VOLATTR MEDIA parameter The volume media can be obtained from the volume label or from an HSC VOLATTR statement MEDIA parameter Keyword VIRTUALLABEL MEDRECTECH 2 For virtual volumes only exclude virtual drives that reside in a VTSS to which the VTV cannot be migrated and recalled AVAILVTSS 3 Exclude drives based on the required recording technique Source VOLATTR RECTECH parameter or volume density 1 e 9840A B and 9840C 4 Exclude drives based on user location policies Primary source TAPEREQ ESOTERIC parameter Secondary source User Exit 08 or 10 return codes VOLATTRRECTECH USERPOLICY 5 Exclude drives based on the SMC ALLOCDEF EXTVOLESOT esoteric EXTVOLESOT 6 Exclude drives based on volume location type 1 e library or nonlibrary 7 Exclude drives based on the ACS location of the volume for library volumes and the resident VTSS for virtual vo
26. E N ar a ot comedy ak N xviii Syntax Flow Diagrams ec eno desata Cee A Maeda RE ese ee aoe es xix Control Statements a da dt A alga E ANE AE os XXIV Related Publications apesna e ee tee A a Se he Be XXV Additional Information A bie BEd AR US ka A Aaa a a xxvi Sun s External Web Site 2 0 cent Raa a ae xxvi Product Publications ooooooooooorrrrrr xxvi Partners Site ii ia ah Sia A EA E tas E E E E ETE xxvi Customer SuppoTt rase ee a e ig E i E ee e e ee Oe Eee ee E xxvi Customer initiated Maintenance 0 ete enn eens xxvii Sun s Worldwide Offices colar eddie we nd ten a od aes ia a xxviii Chapter 1 Introduction 2 202 soccer irradia ve 1 What is SMC tt a A Rhee a blyallele a thd PG dele ake 1 DEMO OY o di dota dio 2 Chapter 2 SMC and Sun StorageTek Library Management oo oooooooomo 5 OVEIVIEW 10 A Bevel helene AA A ne Vaid edhe 5 SMC LIBrary and SERVer Commands 0 0 c cece eee ene eens 5 Client Communication Monitor Subtask 0 0 eee eens 5 Sun StorageTek HTTP Server for MSP 1 1 ccc ene 6 SMC Configuration Scenari0S 2 6 0 nuia ead iea daaa a i enn a eens T Scenario 1 SMC and a Single Local HSC Library Configuration 7 Scenario 2 SMC and a Single Remote HSC Library Configuration 9 Scenario 3 SMC and a Single HSC Library Configuration with One Local and One Remote alter Tate PA a ta dea a ler 11 Scenario 4 SMC and a
27. Exclusion Level 4 Ifa TAPEREQ statement specifies an esoteric for this allocation request the SMC determines the common drives between the TAPEREQ esoteric and the list of remaining eligible drives If common drives exist any drives remaining in the current list of eligible drives that are not also defined to the esoteric are excluded from consideration for this allocation Ifno TAPEREQ statement specifies an esoteric for this allocation request User Exit 02 and User Exit 10 return codes and values can define this criterion for drive exclusion The user exit return codes can direct the SMC to select library drives nonlibrary drives or a specific ACS or the user exit can return an esoteric unit name that contains customer selected drives Any drives in the current list of eligible drives that did not match the user exit return values are excluded here For example DD1 DD UNIT CART DSN amp amp TEMP1 DISP NEW PASS Assume User Exit 02 returns UX02LIB which requests library drives The drives that are not in the library are excluded from consideration for this allocation A TAPEREQ example is DD2 DD UNIT CART DSN SYS4 TR1 DATA DISP NEW KEEP The following TAPEREQ statement is defined to the SMC TAPEREQ DSN SYS4 TR1 ESOT TLIB984 RECT LONGI The drives that are not defined to the esoteric TLIB9840 are excluded from consideration for this allocation Any User Exit 02 return codes would be ignored Chapter 4 SMC Allocatio
28. For example DD1 DD UNIT CART VOL SER INACS DISP 0LD DD2 DD UNIT AFF DD1 VOL SER INACS1 DISP 0LD Assume the following e Both volume INACSO and INACS1 share common media characteristics e Volume INACSO resides in ACSO and volume INACS1 resides in ACS1 e Only ACSO contains a compatible drive If this affinity chain is not broken then volume INACS1 must be ejected from ACS1 and entered into ACSO for this job to execute which may not be possible given the geographical locations of the ACSs In this case failure at allocation time may be preferable to failure at run time By specifying the correct MINLVL value 1 e by issuing the ALLOCJob command with a MINLVL of 7 for this job the job is failed at allocation time Caution Setting the minimum exclusion level may cause jobs to fail unexpectedly UN Whenever the SMC is unable to apply an exclusion criterion at or below the minimum level the job fails allocation For example if a TAPEREQ specifies a media of STANDARD for a scratch volume and the eligible device list contains only T9840 drives when the SMC attempts to apply the policy media exclusion level all drives are excluded If the minimum level is set to 3 or higher the job fails allocation Therefore it is recommended that the default exclusion level as specified by the ALLOCDef command should normally not be set to a level greater than 2 Chapter 4 SMC Allocation in a JES Environment 31 312614001 Rev
29. If parenthesis a comma a semicolon or any other delimiter is shown with an element of the syntax diagram it must be entered as part of the statement or command unless otherwise stated Ranges e An inclusive range is indicated by a pair of elements of the same length and data type joined by a dash The first element must be strictly less than the second element e A hexadecimal range consists of a pair of hexadecimal numbers for example 0A2 0AD or 000 0FC e A decimal range consists of a pair of decimal numbers i e 1 9 or 010 094 Leading zeros are not required The decimal portion is referred to as an incremental range The character positions of the incremental portion of both range elements must match and the nonincremental characters of the first element must be identical to those of the second element About this Guide xxi 312614001 Rev B A numeric VOLSER range vol range consists of a pair of VOLSER elements containing a decimal numeric portion of to 6 digits for example ABC012 ABC025 or X123CB X277CB The decimal portion is referred to as an incremental range The following additional restrictions apply The character positions of the incremental portion of both range elements must match The nonincremental characters of the first element must be identical to those of the second element You cannot increment two portions of a range element If 111AAA is the first element you cannot
30. Levels in the SMC Configuration and Administration Guide System Action None The criteria that would have eliminated all devices is ignored User Response None Esoteric EEEEEEEE contains no known devices ignored for job JJJJJJJJ step SSSSSSSS DD DDDDDDDD Message Level 8 Explanation During execution of job JJJJJJJJ step SSSSSSSS the SMC allocation component encountered a user policy esoteric FEEEEEEE from TAPEREQ or user exit that did not contain any tape devices in the current EDL System Action The specified esoteric is ignored User Response None Chapter 9 SMC Messages 153 312614001 Rev B SMC0048 SMC0051 SMC0048 SMC0049 SMC0051 ACS ID AA contains no known devices ignored for job JJJJJJJJ step SSSSSSSS DD DDDDDDDD Message Level 8 Explanation During execution of job JJJJJJJJ step SSSSSSSS the SMC allocation component encountered an user exit policy requesting exclusion to ACS ID aa However the EDL at the current exclusion level does not include tape devices in the requested ACS System Action The ACS ID policy request is ignored User Response None No eligible libraries for job JJJJJJJJ Message Level 8 Explanation During execution of job JJJJJJJJ the SMC allocation component did not find any libraries at the correct release level System Action If ALLOCDEF FAILnoinfo is specified the SMC marks all devices ineligible Otherwise no allocation influencing is performed for
31. Parameters H Optional Parameters TMS gt zara subsys name a The keywords for the PARM parameter are positional If the PARM parameter is not specified default values are used Parameter Descriptions This section describes the values you can specify for the PARM parameter on the JCL EXEC statement TMS Specifies the CA 1 tape management system This is the default value TLMS Specifies the CA DYNAM TLMS tape management system ZARA Specifies the Zara tape management system SL specifies standard label type for the scratch volume selection This is the default value NL specifies nonlabeled type for the scratch volume selection AL specifies ANSI label type for the scratch volume selection 134 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B NSL specifies nonstandard label type for the scratch volume selection 1900001 Specifies January 1 1900 as the date This is the default date IS Note You must specify a four year format for year 2000 dates For example specify 2000001 for January 1 2000 TODAY Specifies the current system date yyyydddl Specifies a single date in four year format This date becomes the from date The to date is the current system date which is not specified All dates must be specified in Julian notation year day yyyydddl yyyyddd2 Specifies a range of dates in which the volumes became scratch Neither date specified can be greater than
32. SMC SMCB107 SWAP volser from XXXI to XXX2 Device XXX2 is the SMC selected device that has been determined to be compatible for the swap The SMC next suppresses the MSP KHE201D or KHE206D message and replaces the message with SMCG118 Allow swap of volser from XXX1 to XXX2 Reply Y or N or DEVICE The operator may approve the device selected cancel the swap or choose a different device Ifthe operator selects a different device the SMC accepts the device with no further compatibility checking If the reply is Y or a new device MSP issues the following message KHE2021 PROCEED WITH SWAP OF XXX1 TO XXX2 If XXX1 is a library owned device the dismount of the volume is automated If XXX2 is a library owned device the mount of the volume is automated Note Ensure that your MSP security package e g RACF TopSecret is configured to grant SMC the necessary authority to respond to MSP swap messages KHE201D and KHE206D HSC Mount Related Messages Certain mount related messages may still be issued by the HSC due to error conditions SLS0088D is issued when due to an error condition a repeated mount for the same volume is required SLS1075D is issued when a dismounted volume encounters an I O or other type of error In addition the following HSC messages are replaced by SMC messages e SLS43061 and SLS4308I are replaced by SMC0106 e SLS4310D is replaced by SMCO110 54 SMC 6 1 MSP Configuration and
33. SMC directs the allocation of each DD to the appropriate library based on TAPEREQ statements user exits specific volume locations and scratch subpools 6 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC Configuration Scenarios This section provides several scenarios for SMC in local remote and multiple library configurations Scenario 1 SMC and a Single Local HSC Library Configuration In this scenario the SMC and HSC execute on the same MSP host as illustrated in the following figure MSP Initiator Address space SMC Address space HSC Address space a Local Library Figure 1 NCS Local Library Configuration Chapter 2 SMC and Sun StorageTek Library Management 7 312614001 Rev B This configuration utilizes three address spaces e the Initiator Address Space from which allocation and mount events originate e the SMC Address Space which intercepts those events e the HSC Address Space to which SMC sends requests for drive and volume data and mount requests This local configuration does not require the Sun StorageTek HTTP server nor does it require any LIBrary or SERVer commands In this scenario the SMC automatically detects the local HSC subsystem by scanning the MSP Subsystem Communication Vector Table SSCVT chain The SMC then routes requests to subsystems on the same host using MSP EX facilities for cross address space communic
34. START keyword However there was no SMCLOG DD in the SMC subsystem startup JCL System Action The LOG command is ignored User Response Add an SMCLOG DD to the SMC subsystem startup JCL then restart the SMC subsystem SMC0159 Logging started stopped Message Level 0 Explanation A LOG command has been issued with the START or STOP keyword System Action SMC logging is started or stopped User Response None 186 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0160 SMC0161 SMC0162 SMC0163 SMC0160 SMC0163 Invalid or overlapping range XXXX1 XXXX2 for keyword ADDRESS of the UNITATTR command Message Level 0 Explanation A UNITATTR command has been issued specifying a device range XXXX1 XXXX2 where XXXX is larger than XXXX2 System Action The UNITATTR command does not process this device range User Response Reissue the command specifying a valid range Restoring all default settings for the CCC CCC command Message Level 0 Explanation The CCC CCC command has been issued with the OFF parameter All SMC values have been restored for the SMC subsystem System Action None User Response None CCC CCC object successfully added updated deleted Message Level 0 Explanation The CCC CCC command has been successfully processed System Action None User Response None DRIVEMAP settings CLIENT XXXX1 XXXX2 SERVER XXXX34 XXXX4 Message Level 0 Expl
35. Subsystem Communications Vector Table SSCVT for the SMC is reset This parameter may correct a situation in which the SMC was terminated abnormally It can be specified with WARM or COLD D Warning Using this parameter when an SMC subsystem is active and functional causes unpredictable results MSTR specifies that the SMC start under the MSTR subsystem instead of under JES When specifying this parameter you must also perform one of the following actions Start the SMC subsystem using SUB MSTR on the MSP Start command e Add the SMC subsystem to the SUBSYSxx subsystem table using the keyword format IEY Note If you wish to run the SMC under the master MSP subsystem the PROCLIB containing the SMC START procedure must be present in the PROCLIB concatenation for the master address space This concatenation is defined in SYS1 PARMLIB MSTJCLxx under DD KDJPDSI 24 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Executing the SMC START Procedure The MSP START command is used to initialize the SMC software When this command is issued the SMC subsystem initialization routine is invoked This routine determines what parameters are in effect performs any cleanup necessary and begins normal processing Parameters associated with PARM on the EXEC statement of the SMC Start Procedure can also be supplied via PARM on the MSP START command The PARM specification on the MSP START command overrides the PARM
36. all drives excluded at that level are restored to the list of eligible drives e processing continues at the next level of exclusion In this case all drives that were excluded by this criterion are now restored to the list Processing continues at level 7 Chapter 4 SMC Allocation ina JES Environment 41 312614001 Rev B Exclusion Level 7 The SMC ALLOCDef command parameter ZEROSCR determines whether or not to include drives in ACSs that do not contain any scratch cartridges of the required type ZEROSCR OFF the default indicates to include drives in all ACSs whether they contain scratch cartridges or not ZEROSCR ON excludes drives in ACSs that do not contain any scratch volumes but leaves all ACSs containing scratch volumes eligible for allocation For example DD1 DD UNIT CART DSN MY NEW DATASET DISP NEW KEEP Assume that ZEROSCR OFF has been specified and two ACSs have scratch counts as follows ACSO has 400 and ACSI has 0 Drives in ACSO and ACSL1 remain eligible for the allocation Another example is DD2 DD UNIT CART DSN MY OTHER DATASET DISP NEW KEEP Assume ZEROSCR ON has been specified and three ACSs have scratch counts as follows ACSO has 400 ACS1 has 500 ACS2 has 0 Drives in ACSO and ACS1 remain eligible ACS2 drives are excluded from consideration because ACS2 does not contain any scratch volumes 42 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Exclusion Le
37. before the SMC has received the message the SMC ignores the WTO and the message is not displayed at the console If you plan to use an automated operations system and are unsure about how it intercepts messages contact the product vendor Although these messages may be suppressed that is prevented from displaying in the console by using AOF functions the text of these messages should not be changed The use of other WTO exits to change the display characteristics or the text of these messages is not supported by the SMC Volume serial numbers ser as specified in messages from the operating system are defined as follows SCRTCH a public scratch volume is to be mounted nonspecific request PRIVAT a private scratch volume is to be mounted nonspecific request VVVVVY volume serial number to be processed specific request Appendix A Intercepted Messages 205 312614001 Rev B Messages that contain VOLSERs with more than six characters or any character except A Z 0 9 crosshatch Y yen character and optional trailing blanks are ignored by the SMC Table 6 Intercepted Operating System Messages Message ID Description JBB068A U dddd ser JBB101A M dddd ser JBB111E D dddd ser JBB114E D dddd JBB135A U dddd ser JBB400A M dddd ser JBB401A F dddd ser JBB501A M dddd ser labtyp JBB501E M dddd ser labtyp JBB502E n ddd
38. but the exit was already in the specified state System Action None User Response Verify the exit number you are trying to alter UEXIT nn not valid at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A UEXIT command was issued for a user exit number not valid for this configuration System Action None User Response Verify the user exit number for your configuration Cannot resolve HOST name HHHHHHHH at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A SERVER command was issued using the HOST keyword specification However the SMC could not resolve the IP address using the specified HOST name System Action The SERVER command is ignored User Response Enter the correct HOST name or use the IPADDRESS keyword instead Chapter 9 SMC Messages 175 312614001 Rev B SMC0128 SMC0128 SMC0128 Library error Job JJJJJJJJ transaction T7TTT LIBRARY LLLLLLLL SERVER SSSSSSSS Interface error CCC CCC Fatal comm error CCC CCC Comm error nnn of nnn CCC CCC Comm error limit nnn exceeded CCC CCC Initialization error nnn CCC CCC Response from HTTP server follows RRR RRR Message Level 4 Explanation The SMC encountered an interface or communication error attempting to communicate with a library subsystem or server The SMC0128 multiline message first lists the jobname transaction type and libraryname associated with the error If the communication erro
39. cartridge slots SL8500 The Sun StorageTek high performance library scalable from 29 terabytes to 70 petabytes with up to 70 000 tape slots T9840A The StorageTek access centric cartridge transport capable of reading and writing 9840A cartridges T9840B The StorageTek access centric cartridge transport capable of reading and writing T9840B cartridges T9840C The StorageTek access centric cartridge transport capable of reading and writing T9840C cartridges T9840D The StorageTek access centric cartridge transport capable of reading and writing T9840D cartridges T9940A The StorageTek capacity centric cartridge transport capable of reading and writing 60GB T9940A cartridges T9940B The StorageTek capacity centric cartridge transport capable of reading and writing 200GB T9940B cartridges T10000 The StorageTek high capacity cartridge transport capable of reading and writing 120GB or 500GB T10000 cartridges T10000B The StorageTek high capacity cartridge transport capable of reading and writing 240GB or 1TB T10000 cartridges Glossary 231 312614001 Rev B Index A affinity separation 44 allocation affinity separation 44 deferring mounts 49 drive exclusion 29 drive prioritization 48 exclusion levels 32 37 intentionally failing a job 31 minimum exclusion level 30 scratch requests 37 SMC interaction with other software 219 specific requests 32 ALLOCDef command 60 ALLOCJob command
40. characters in length System Action Processing continues The entire multi line is ignored User Response Ensure that the command data set has the correct syntax Chapter 9 SMC Messages 157 312614001 Rev B SMC0062 SMC0066 SMC0062 Command CCCCCCCC with parameter PPPPPPPP is not allowed from consolelat line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command or a command parameter that is not supported for the indicated command origin For example the READ command is not supported if encountered during processing of another READ command System Action The command is ignored User Response Issue the command from a valid command origin SMC0063 MSGDEF settings CCCC CCCC Message Level 0 Explanation A MSGDEF command has been issued with the LIST keyword The SMC0063 multiline message lists the current settings for the SMC subsystem Refer to the MSGDEF command for parameter descriptions System Action None User Response None SMC0066 ALLOCDEF settings CCCC CCCC Message Level 0 Explanation An ALLOCDEF command has been issued with the LIST keyword The SMC0066 multiline message lists the current settings for the SMC subsystem Refer to the ALLOCDEF command for parameter descriptions System Action None User Response None 158 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0067 SMC0069 SMC0070 SMC0067 SMC0070
41. command defines the appearance of SMC system messages and controls which messages are displayed and suppressed Syntax MSGDef UPPER 8 casec mxeo L vc L ever OFF ON ccnomterr A h gt a ON OFF Command Name MSGDef initiates the MSGDef command Parameter Descriptions LIst optionally lists current default SMC message settings This is the default if no parameters are specified It cannot be specified with any other parameter OFF optionally resets all MSGDef values to original SMC default settings It cannot be specified with any other parameter CASE optionally specifies the message case Valid values are UPPER or MIXED If no value is specified the default value UPPER is used Chapter 6 Commands and Control Statements 87 312614001 Rev B MSGJob LVI optionally specifies the default level used to control which SMC messages are displayed and suppressed level indicates the default level Valid values include the following 0 Display error messages only 4 Display error and warning messages from the SMC subsystem 8 Display all SMC subsystem messages and allocation job log warning messages This is the default value if the MSGDef parameter is not specified If no value is specified the default value of 8 is used Note Levels higher than 8 are used for diagnostic purposes and should only be specified as directed by Sun Microsystems Software Support ECHOmnterr optionall
42. data set containing TAPEREQ control statements that are currently loaded Information includes e data set name e member name e identifying string if the data set contains an OPTion TITLE statement e date and time parameters were loaded Chapter 6 Commands and Control Statements 119 312614001 Rev B UEXit DATASET or DSN specifies the name of the data set containing the TAPEREQ control statements to be processed and optionally an OPTion TITLE statement dsn the data set name This data set can be a fixed length 80 byte sequential data set or a fixed length 80 byte member of a PDS If the data set name includes a member name you must enclose the dsn in quotes For example DATASET YOUR PDS DSN MEMBER VOLume specifies the volume serial number of the DASD volume on which the data set resides This parameter is optional Specify the VOLume parameter if the data set is not cataloged volser the volume serial number for the definition data set UNIT specifies the unit name where the definition data set is located This parameter is optional Specify the UNIT name if the data set is not cataloged unitname the unit name If the definition data set is not cataloged and the unitname is omitted a unit name of SYSALLDA is the default HOSTID specifies the hostid from which to execute this control statement This parameter is valid only for use in PARMLIB to allow multiple systems to share a parmlib member conta
43. e monitor SMC activity e diagnose and correct SMC problems See Chapter 10 Sun StorageTek HTTP Server Messages for information about messages issued by the Sun StorageTek HTTP Server for MSP Message Format Messages are displayed on the console in the following format SMCnnnn message text where e SMC identifies the Storage Management Component SMC e nnnn is the four character message number e message text is the actual text displayed on the job log or system log Chapter 9 SMC Messages 139 312614001 Rev B Message Descriptions This chapter provides a description for each SMC message In addition to the message number and message text this description includes the following Message Level The message level represents a message category Using the MSGDEF or MSGJOB operator command the message level is specified in order to control which categories of messages are issued See MSGDef Command on page 87 for more information Explanation The explanation describes the message System Action The system action describes how the SMC reacts when a message triggering event occurs User Response The user response describes how the user should respond to the message In many cases no response is required Variable Definitions Italicized text indicates variable data that is replaced by actual values when messages are issued Message specific variable data is symbolized as follows Table 5 Variable Data Defin
44. each JES processor independently controls its job input scheduling and output processing 226 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B L LAN See local area network LCS See Library Control System LCU See Library Control Unit LIBGEN The process of defining the configuration of a library to the HSC library An installation of one or more ACSs attached cartridge drives also known as transports volumes cartridges placed into the ACSs host software that controls and manages the ACSs and associated volumes and the library control data set that describes the state of the ACSs library cartridge transport See transport library complex A library complex consists of one HSC Control Data Set CDS and may contain up to 256 Automatic Cartridge Systems ACSs each of which may contain up to 24 Library Storage Modules LSMs library control component Software that controls the mounting and dismounting of cartridges in an ACS library control platform The hardware and software that provides the proper environment for the Library Control System library control processor Properly configured computer hardware that supports the operation of the Library Control System Library Control Software A library control component the client system interface and library utilities Library Control System LCS The library control platform and the Library Control
45. entered in the following format F started task name command name parameter The following example illustrates the MSGDef command F SMC1MSP MSGDEF LVL 4 IEY Notes The started task name and command name must be separated with a comma Spaces are not allowed between the subsystem name and command name e Parameters and values can be separated with any number of spaces and may optionally include an equal sign Values may also be included in parentheses The following are all equivalent commands F SMCIMSP MSGDEF LVL 4 F SMC1MSP MSGDEF LVL 4 F SMCIMSP MSGDEF LVL 4 Issuing SMC Commands Using the SMC Command Prefix SMC operator commands can be issued using an SMC command prefix This prefix is defined using the SMC CMDDef command See CMDDef Command on page 71 for more information about this command 58 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Specifying SMC Commands in the SMCPARMS or SMCCMDS Data Set SMC operator commands can be specified in the SMCPARMS or SMCCMDS data set These commands are automatically processed at startup See Control Statements on page xxiv for syntax conventions used when specifying commands in the SMCPARMS or SMCCMDS data set The SMCCMDS data set can be reprocessed while the SMC is active using the READ operator command The following is a sample SMCCMDS member entry MSGDEF CASE MIXED LVL 4 TREQDEF DSN MY PARMLIB TREQ
46. in an allocation event at common allocation time SSI24 subsystem function its first step is to narrow down the list of eligible drives to those that best support the allocation request This step is called drive exclusion Like the HSC device separation process the SMC drive exclusion process does not take into account the status of drives e g offline busy when selecting drives that are eligible for the allocation request If all drives compatible with the allocation request are unavailable the job goes into allocation recovery The SMC performs drive exclusion by building a list of drives contained in the initial EDL and then by following a step by step process using an ordered list of exclusion criteria to remove drives from this list Before any drives are removed from consideration for the allocation the SMC first determines whether a job step can be allocated For example JOB1 JOB STEP1 EXEC PGM DD1 DD UNIT 3499 DD2 DD UNIT 349 DD25 DD UNIT 349 Assume STEP1 is requesting twenty five 3490 drives If the MSP EDL contains twenty four 3490 drives in its lists of eligible devices MSP cannot allocate the required drives for the job In this instance the SMC issues message SMC0042 which indicates the job cannot allocate before SMC modification and allows the job to fail allocation Once the SMC determines a job step can be allocated the SMC begins excluding drives based on an ordered list
47. issued on the HSC server but are sent directly to the client console instead The operator response to the message is then transmitted back to the server as SMC redrives the mount or dismount to the server The following HSC mount dismount WTOR messages are currently supported with this option e SLS0134 e SLS0905 e SLS2126 e SLS2905 e SLS2984 e SLSO109 e SLS4084 Refer to the HSC Messages and Codes Guide for more information about these messages Chapter 5 SMC Message Handling 55 312614001 Rev B Chapter 6 Commands and Control Statements Overview ALLOCDef ALLOCJob CMDDef DRIVemap LIBrary LIst LOG MOUNTDef MSGDef MSGJob READ RESYNChronize SERVer TAPEREQ control statement TCPip TRace TREQDEF UEXit UNITAttr USERMsg This chapter provides information for the following SMC commands and control statements Chapter 6 Commands and Control Statements 57 312614001 Rev B Issuing SMC Commands SMC operator commands can be issued using the following methods e Issuing SMC commands using the MSP Modify command e Issuing SMC commands using the SMC command prefix Specifying SMC commands in the SMCPARMS or SMCCMDS data set s Issuing SMC Commands Using the MSP Modify Command The following information is included when an SMC command is issued using the MSP Modify F command MSP Modify command F e SMC started task name command name e parameters optional or required SMC commands are
48. of criteria Table 2 on page 32 and Table 3 on page 37 list these criteria and show the order the exclusion process follows The lower the criteria level the higher its importance Thus level 2 is considered more important than level 6 Chapter 4 SMC Allocation in a JES Environment 29 312614001 Rev B Minimum Exclusion Level By default level 2 is the minimum exclusion level that is the desired minimum level of allocation exclusion for both specific and scratch volume processing However if necessary the ALLOCDef and ALLOCJob commands can reset the minimum exclusion level refer to Chapter 6 Commands and Control Statements for descriptions of these commands In the first step of drive exclusion the SMC determines if the job can be allocated at the minimum drive exclusion level If not enough drives remain eligible at the minimum exclusion level the SMC issues message SMC0043 which indicates the job is not allocatable at the minimum exclusion level The SMC then excludes all devices causing the job to fail allocation For example JOB2 JOB STEP1 EXEC DD1 DD UNIT 3499 VOL SER 984601 DISP OLD DD2 DD UNIT 3494 VOL SER 9840M02 DISP 0LD DD3 DD UNIT 3494 VOL SER 984M03 DISP 0LD In this system environment assume that twenty 3490 type drives have been configured Only two of those twenty are actually T9840 drives Ifall three volumes require a separate T9840 tape drive then not enough T9840 drives exist fo
49. on how the SMC selects among multiple library subsystems to determine an owner for each allocation request i e each DD in a job step may have a different library subsystem owner Chapter 4 SMC Allocation in a JES Environment 49 312614001 Rev B Chapter 5 SMC Message Handling Overview The SMC intercepts specific MSP and Tape Management System TMS messages related to mount dismount and swap operations When the intercepted message includes a drive defined to an HSC library subsystem the SMC directs the owning library subsystem to perform the requested operation Messages that are intercepted by the SMC are listed in Appendix A Intercepted Messages on page 205 User Directed Message Handling If the SMC does not currently support the Tape Management System at your installation you can still direct the SMC to intercept the specific messages issued by your TMS Use the USERMsg operator command to define these additional messages See USERMsg Command on page 126 for more information User Exit 01 allows you to change or enhance actions taken on intercepted messages and can direct the SMC to perform actions on messages that are not in the intercepted message list The SMC calls the library subsystem user exit for each intercepted message This includes the default messages listed in Appendix A Intercepted Messages and all messages defined using the USERMsg command rs Notes Only messages inte
50. or model2 is assumed to be the second alternate device The following table shows the alternate device order if only model is entered Table 4 Alternate Device Default Value Preferred Device First Alternate Second Alternate model 1 Device model2 Device model3 4490 9490 9490EE 9490 4490 9490EE 9490EE 4490 9490 Entering DEVTpref 9490 4490 is functionally equivalent to DEVTpref 9490 4490 9490EE Chapter 6 Commands and Control Statements 109 312614001 Rev B TCPip SCOPE Specifies whether device preferencing should be performed across the entire library complex single or multiple ACS or at the individual LSM level The SCOPE parameter may be used in an attempt to reduce pass thru events SCOPE is valid only when the DEVTpref parameter is specified on the same TAPEREQ statement LIBrary Specifies that all of the preferred models in the ACS are to be given a higher selection probability than all of the alternate models while maintaining the ability to automate tape mounts LIBrary is the default value In a multiple ACS configuration the way that the SMC processes SCOPE LIBrary depends on the following The ability to automate the mount The type of request specific versus scratch A specific volume request is confined to the ACS where the volume resides so that the mount can be automated The transports in all other ACSs and all nonlibrary transports are marked ineligible for selecti
51. or freed successfully Job JJJJJJJJ is the task currently attempting to acquire or free the resource but cannot because another task holds the resource System Action Jobname JJJJJJJJ may not be processed correctly User Response Contact Storage Technology technical support Chapter 9 SMC Messages 163 312614001 Rev B SMC0089 SMC0093 SMC0089 Unable to start subtask CCCCCCCC Message Level 0 Explanation During initialization the indicated SMC subsystem task could not be successfully attached System Action The SMC subsystem terminates User Response Look for related MSP or SMC messages in the SYSLOG or SMC job log SMC0090 Unable to restart subtask CCCCCCCC Message Level 0 Explanation During subsystem processing the indicated SMC subsystem task abended and could not be restarted System Action Processing continues However subsystem processing or command facilities may be affected User Response Stop and restart the SMC subsystem If the indicated subtask is SMCOCMD use the MSP CANCEL command to terminate the subsystem SMC0091 Could not allocate job JJJJJJJJ step SSSSSSSS after applying all exclusion levels backing up until allocatable Message Level 8 Explanation The indicated job step would not allocate when all exclusion criteria were applied to all DDs in the step This means that the remaining set of drives is insufficient for each DD to be assigned a unique drive System Action The SMC backs
52. out exclusion criteria on selected DDs in the step until the set of remaining drives is sufficient to allocate to all DDs in the step User Response None SMC0093 TCPIP TCPNAME CCCCCCCC ADSNAME CCCCCCCC Message Level 0 Explanation A TCPIP LIST command was issued The current values of the TCPNAME and ADSNAME are displayed If the SMC is using the default settings default is displayed System Action None User Response None 164 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0094 SMC0095 SMC0096 SMC0097 SMC0094 SMC0097 MOUNTDEF SETTINGS CCCC CCCC Message Level 0 Explanation A MOUNTDEF command has been issued with the LIST keyword The SMC0094 multiline message lists the current settings for the SMC subsystem Refer to the MOUNTDEF command for a description of keywords and their meanings System Action None User Response None UX91 function code UX 1RPLY not supported Message Level 4 Explanation The function code return of UXOIRPLY reply to a WTOR message is not supported by SMC System Action None The user exit is ignored User Response None Invalid UX 1 function code X XX Message Level 4 Explanation A user exit 01 returned an invalid function code of X XX System Action All data returned by this invocation of UXO1 is ignored User Response Correct the UX01 to return only function codes documented in the NCS User Exit Guide
53. parameter Chapter 6 Commands and Control Statements 73 312614001 Rev B LiBrary For example CL AA0 AA2 SE BA0 BA2 is valid CL AA0 AA2 SE BAO BA BA2 is invalid 74 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B LiBrary Example In the following example the DRIVemap command maps a set of client drive addresses BAO BAF to a set of server drive addresses AA0 AAF DRIVemap CLient BA BAF SErver AAB AAF Chapter 6 Commands and Control Statemenis 75 312614001 Rev B LiBrary LIBrary Command The SMC LIBrary command defines a specific Sun StorageTek tape hardware configuration normally represented by a single CDS IS Notes LIBrary and SERVer commands are required to access remote HSC libraries Ifa LIBrary command is specified then all libraries must be explicitly defined e Ifthe LIBrary command is not specified the SMC uses active HSC subsystems defined in the host s SSCVT chain The LIBrary command can also be used to list libraries that the SMC tries to communicate with and report their status Syntax LIBrary NAme name ENable Server Fane name __________wroraest DIsable Local subsys parms Client SERVerlist NAme name Local subsys parms LOCENAble LOCDISable LOCSUBsys subsysname 76 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B List Command Name LIBrary initiates
54. previously provided by the HSC Chapters 3 5 6 The SMC ALLOCDEF command includes the following new parameters DEFER FETCHMSG EXTVOLESOT and ZEROSCR Chapters 3 6 The SMC LIBrary command includes a new STATus parameter used to list current status active inactive disabled for all libraries or a single named library For an active library the status lists the name of the current server or local subsystem Chapter 6 The SMC READ command includes a new HOST parameter used to specify that a READ command only be processed for a specific host Additionally the SMC READ command can now be issued from either the console or a file Chapter 6 The SMC SERver command is revised as follows The new INITFail parameter can be used to specify the number of failures before communication is established before the specified server path is disabled or placed out of service The FAil limit default for the SMC SERver command is changed from 10 to 0 Rules for the hostname value HOst parameter are changed Chapter 6 SMC LIBRARY WTORDEST processing now applies to both local and remote servers Chapter 6 SMC MSGDEF ECHOMNTERR processing now applies to both local and remote servers Chapter 6 ALLOCDEF FAILNOINFO processing now applies to either specific volume allocations only or to all allocations Chapter 6 SMC exclusion level 1 for specific requests is updated to exclude all virtua
55. processing an affinity chain the drive exclusion process examines each allocation in the chain separately up to and including the minimum exclusion level The chain is always separated when the minimum exclusion level processing results in lists of eligible drives for two or more members of the chain that do not contain common drives For example DD1 DD UNIT CART DSN MY STK1R DATASET DISP 0LD DD2 DD UNIT AFF DD1 DSN MY LONGI DATASET DISP 0LD DD specifies a data set on 9840 or T9840B media and DD2 specifies a data set on longitudinal media Drive exclusion level 1 for specific volumes creates a list of eligible drives for each DD according to volume media required The two lists do not contain a common drive As a result DD1 and DD2 no longer represent one drive allocation but two separate allocation requests At this point the SMC breaks the affinity chain between them Affinity Head Of Chain For SMC affinity chain processing the head of the affinity chain containing only scratch or only specific volumes is the first DD statement in the chain If an affinity chain contains both scratch and specific volumes the first specific volume is the head User Policy Influence on Affinity Separation After the minimum level of drive exclusion and affinity separation completes user policy influences the remaining affinity separation decisions Further affinity chain processing decisions are based on the first value found betw
56. regarding SMC exclusion levels IS Notes e Setting MINLVL 0 indicates that the job will not be failed by the SMC even if the device and specific volume are incompatible MINLVL 0 may be used to force SMC to allow allocation to succeed when a foreign tape cartridge has the same volume serial number as an existing library or virtual volume e Increasing minlevel has no effect unless message SMC0045 or SMC0091 has been issued for a specific job step Chapter 6 Commands and Control Statements 61 312614001 Rev B ALLOCDef SEPL vl optionally specifies the exclusion level at which affinity and GDG chains are separated IS Note If HSC allocation previously specified UNITAFF NOSEP and GDGALL NOSEP the default SMC exclusion tables can specify SEPLvI 3 in order to preserve existing behavior for scratch affinity chains with different media types MIN do not separate chains beyond the minimum level MAX separate chains for conflicting exclusion criteria whenever sufficient drives are available This is the default value seplevel indicates a separation level between the minimum and maximum levels When sufficient drives exist the SMC attempts to separate chains at this level See Chapter 4 SMC Allocation in a JES Environment for more information regarding SMC exclusion levels IS Note The seplevel value cannot be less than the minlevel value FAILnoinfo optionally specifies whether the SMC fails a job step duri
57. routine but the load failed System Action The utility processing terminates with a return code of 8 User Response Ensure that a load library containing the appropriate SLUDR routine for your tape management system 1s available to the SMCUDBX utility though a JOBLIB STEPLIB or MSP LINKLIST library Error opening file DDNAME DBTMS DBEXTFIL Explanation Explanation The SMCUDBX program or tape management extract program was unable to open the tape management data base file or extract file System Action System Action The utility processing terminates with a return code of 8 User Response User Response Correct the execution JCL to provide the required DD statement Error processing ZARA interface for subsystem SSSS Explanation The user requested an extract from the ZARA tape management system with subsystem ID CCCC A detailed description of the error follows the message System Action The utility processing terminates with a return code of 8 User Response Correct the indicated error and resubmit the job Unexpected return code XXXX from TMS interface Explanation An unexpected return code XXXX was received from the TMS extract routine System Action The utility processing terminates with a return code of 8 User Response If user modifications have been made to the TMS extract routine correct the routine Otherwise contact Sun Microsystems Software Support for assistance Chapter 9 SMC Messages 193 3126
58. settings and job name step name and PROC step exceptions in the order of evaluation This is the default if no parameters are specified It cannot be specified with any other parameter OFF optionally removes MSGJob overrides Ifno other parameters are specified MSGJob overrides are removed for all jobs If only JOBname is specified MSGJob overrides are removed for ALL MSGJob entries for that job name If JOBname STEPname and PROCstep are specified MSGJob overrides are removed only for the specified entry The global MSGDef is not affected by this parameter 90 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B READ JOBname optionally specifies a job name jobname indicates the job name The value entered must be one to eight characters in length An asterisk can be used as a wildcard when included as the last character In this case the message level is set for all jobs whose job names match the characters preceding the asterisk STEPname optionally specifies a step name It is only valid when JOBname is also specified may be JOB stepname indicates the step name The value entered must be one to eight characters in length This parameter is only valid if JOBname is also specified PROCstep optionally specifies a PROC step It is only valid when JOBname and STEPname are also specified procstep indicates the PROC step The value entered must be on
59. specify 112AAB for the second element Ifa VOLSER range contains more than one decimal portion any portion is valid as the incremental range For example A00B00 the largest range that can be specified is A00B00 through A99B99 A0B0CC the largest range that can be specified is AOBOCC through A9B9CC 000XXX the largest range that can be specified is OOOXXX through 999XXX xxii SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B An alphabetic VOLSER range vol range consists of a pair of VOLSER elements containing an incremental portion of 1 to 6 characters for example 000AAA 000ZZZ or 9AAA55 9ZZZ55 This portion is referred to as an incremental range The following additional restrictions apply The character positions of the incremental portion of both range elements must match The nonincremental characters of the first element must be identical to those of the second element You cannot increment two portions of a range element If 111AAA is the first element you cannot specify 112AAB for the second element The alphabetic portion of the VOLSER range is defined as being from character A to Z To increment multi character sequences each character increments to Z For instance ACZ is part of the AAA AMM range Examples are A00A0 A99A0 9AA9A 9ZZ9A 111AAA 111ZZZ 999AM8 999CM8 A3BZZ9 A3CDE9 AAAAAA AAACCC CCCNNN DDDNNN increments VOLSERs A00A0 through AO9AO then A1
60. status of the server active indicates that this server is the current path through which the specified library will be accessed never active indicates that communication was never attempted on this path or was attempted but never succeeded inactive indicates that another server path is active or that the last communication attempt on this path failed disabled indicates that the SERVER has been disabled by a discovered incompatibility by reaching the FAIL limit or by an operator command e Messages indicates the number of logical messages volume lookup requests mounts dismounts on this server path e Retries indicates how many message retries have been attempted e Init errors indicates the current count of number of errors for an inactive server e Errors indicates the total number of errors on this server System Action None User Response None Chapter 9 SMC Messages 171 312614001 Rev B SMC0116 SMC0118 SMC0116 SMC0117 SMC0118 Cannot find LIBRARY LLLLLLLL for SERVER SSSSSSSS at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A SERVER command was issued with a LIBRARY name that was not previously defined System Action The SERVER is not added or updated User Response Specify a LIBRARY command to define the library then specify the SERVER command Cannot change LIBRARY name for existing SERVER SSSSSSSS at line nnnn of SMCCMDS SMCPARMS Message Level 0 Expla
61. the ADSNAME value for a specific TCP IP stack on an MSP host ADSNAME is the jobname of the TCP IP startup job Refer to the IBM 112 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TRace publication TCP IP for MSP Application Programming Interface Reference for more information about ADSNAME name indicates the ADSNAME value MONitor optionally specifies the communication monitor subtask scan interval and communication monitor subtask message interval nnnn indicates the monitor scan interval in seconds The communication monitor wakes every nn seconds to perform library communication validation Specify a value between 10 and 9999 or OFF The default is 60 OFF disables the communication monitor subtask It is recommended that you preserve the default setting of 60 to enable a monitor scan every minute A value that is too low can potentially degrade performance when inactive libraries exist A value that is too high can delay a return to the primary server if PREFPRIMARY ON is specified or delay the redriving of mounts when there is no allocation or mount activity but a communication path becomes available mmmm optionally indicates the monitor scan interval in number of scans Communication error messages are displayed according to this interval The default is 10 The default MONITOR 60 10 setting specifies a monitor scan interval of 60 seconds and a monitor message interval of 10 scans A scan 1s
62. the following example the USERMsg command is used to list message identifiers for messages included in the customer defined message table USERMsg LI 126 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Chapter 7 Recovery Procedures Overview This chapter describes recovery procedures used when the SMC or a library subsystem becomes inactive SMC Recovery Procedures JES This section describes recovery procedures for the following problem scenarios Inactive SMC Active library subsystem e Active SMC Inactive library subsystem e Automating mount requests for inactive libraries e Lost MSP mount requests for active libraries Inactive SMC Active Library Subsystem When the SMC fails while a library subsystem remains active the following functions are not performed e allocation processing e automation of mount dismount swap messages When this occurs re start the SMC Common allocations can be postponed by holding the job queue or purging all initiators Refer to the appropriate Fujitsu publication for more information about JES operator commands If the SMC MOUNTDef AUTOPendmount ON option was specified outstanding mount messages are re driven Chapter 7 Recovery Procedures 127 312614001 Rev B Active SMC ES Inactive Library Subsystem When a library subsystem fails or is terminated volumes and drives owned by that subsystem become unknown to SMC The following fu
63. the prior SMC subsystem of the same name was an incompatible version The COLD start parameter was not specified System Action Initialization continues but in COLD start mode the SMC subsystem CVT is rebuilt User Response None SMC0008 Not running from an authorized library SMC subsystem terminating Message Level 0 Explanation The SMC subsystem initialization module SMCBINT was executed from an unauthorized library System Action The SMC subsystem terminates User Response Ensure that the SMC link library is APF authorized 142 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0009 SMC0010 SMC0011 SMC0012 SMC0009 SMC0012 Job JJJJJJJJ JOBnnnn active at termination Message Level 4 Explanation The SMC subsystem received the MSP stop P command but there is an active job JJJJJJJJ in tape allocation The SMC0012 message was issued previously but the job allocation has not completed after waiting one minute System Action Termination continues No allocation influencing is performed for JOBnnm User Response None Unable to acquire storage for CCCCCCCC return code XXXX Message Level 0 Explanation During initialization the SMC subsystem could not acquire sufficient storage for the specified dynamic control block or module CCCCCCCC System Action The SMC subsystem terminates User Response Ensure that there is sufficient CSA storage available Refer to Fuj
64. the specified WAIT time is greater than 600 seconds REtry specifies the number of retries to be attempted for any single request before the task is allowed to resume and a failure recorded nnnn indicates the number of retries The default is 3 FAil optionally specifies the number of failures after communication is established before the server path is disabled or placed out of service Note The FAil limit count only applies after successful communication has been established on this SERVER path nnnn indicates the number of failures The default is 0 If 0 is specified the named SERVER is never automatically disabled due to communications errors Specify this value when there are no backup SERVER paths to a named LIBRARY After successful communication is established with a LIBRARY the error severity and SERVER FAil count are used to determine whether a SERVER path should be automatically disabled INITFail optionally specifies the number of failures before communication is established before the server path is disabled or placed out of service Note The INITFail limit count only applies before successful communication has been established on this SERVER path nnnn indicates the number of failures The default is 0 If 0 is specified the named SERVER is never automatically disabled due to communications errors Chapter 6 Commands and Control Statements 99 312614001 Rev B TAPEREQ Examples In the fo
65. to invoke the Scratch Extraction utility to process the CA DYNAM TLMS VMF for all tapes scratched in 2003 yourstd JOB card STEP EXEC PGM SMCUDBX PARM TLMS 2083001 2003365 STEPLIB DD DISP SHR DSN your SMCLINK DD DISP SHR DSN your SLUDRxxx LINKLIB DBTMS DD DISP SHR DSN your tlms database DBEXTFIL DD DISP NEW KEEP DSN scratch extract file SPACE TRK 5 1 UNIT SYSDA STDOUT DD SYSOUT Figure 10 Sample JCL for Scratch Extraction Utility 136 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Sample Output Output resulting from the execution of the Scratch Extraction utility includes e Messages associated with error conditions resulting from an unsuccessful attempt to execute scratch extraction processing e Messages indicating errors or actions occurring during processing An output data set containing Scratch Update utility control statements Figure 11 shows sample output from the SMCUDBX utility SMCUDBX 6 1 8 SMC TMS DB SCRATCH EXTRACT Page 44001 TIME 15 26 41 Date 2003 98 14 Total records extracted for scratch volumes 977 Figure 11 Scratch Extraction Utility Sample Output Messages Chapter 8 SMC Tape Management Extract Utility 137 312614001 Rev B Chapter 9 SMC Messages Overview This chapter provides information about SMC messages This information is provided to help system programmers and operators e initialize the SMC
66. value esoteric USEREXIT specifies an esoteric to be used to allocate a specific external volume when the use specvol user exit return code is specified If the specific volume user exit returns the use specvol return code for this DD then any drives in the specified esoteric that intersect with the original esoteric will be selected for allocation This is the default value if esoteric is specified esoteric ALL specifies that whenever an external volume is allocated the drives in the specified esoteric are to be selected ZEROscr specifies whether the SMC is to exclude the drives in one or more ACSs from the list of eligible drives when a scratch mount is requested in a multiple ACS environment OFF indicates that all drives in all ACSs are to remain eligible for selection This is the default value ON indicates one of the following e Ifscratch subpools are not being used and one or more ACSs contain zero scratch volumes then drives in those ACSs will be excluded from the list of eligible devices e Ifa scratch subpool is being requested either though TAPEREQ or User Exit 04 and one or more ACSs contain zero scratch volumes in the requested subpool then drives in those ACSs will be excluded from the list of eligible devices 64 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCDef VTVMAXvol optionally specifies whether the SMC sets the volume count for a new allocation to 25
67. was received within the time limit System Action The SMC continues processing without waiting for the acknowledgment User Response None SMC0175 ES SMC0192 SMC0193 Communication initialized on LIBRARY name SERVER name Message Level 8 Explanation The SMC has successfully communicated with the specified LIBRARY for the first time Additionally if the communication path selected was a remote SERVER then the SERVER is also displayed System Action Processing continues User Response None Note This message is produced each time communication switches from one server to another or communication is re established after an error Specific volume lookup failure s during job JJJJJJJJ Message Level 4 Explanation During execution of job JJJJJJJJ the SMC could not complete a volume lookup request for one or more specific volumes System Action The SMC continues processing the request using available policy information User Response If other policy information is not sufficient to allocate the specific volume investigate whether FAILNOINFO SPECIFIC should be specified Scratch volume lookup failure s during job JJJJJJJJ Message Level 8 Explanation During execution of job JJJJJJJJ the SMC could not complete a volume lookup request for one or more scratch volumes System Action The SMC continues processing the request using available policy information User Response If other policy information i
68. 0A0 through A99A0 increments VOLSERs 9AAQA through 9AZ9A then 9BA9A through 9ZZ9A increments VOLSERs 111AAA through 111AAZ then 111ABA through 111ZZZ increments VOLSERs 999AM8 through 999AZ8 then 999BA8 through 999CM8 increments VOLSERs A3BZZ9 through A3CAAQ then A3CABO9 through A3CDE9 increments VOLSERs AAAAAA through AAAAAZ then AAAABA through AAACCC increments VOLSERs CCCNNN through CCCNNZ then CCCNOA through DDDNNN Caution This is a very large range About this Guide xxiii 312614001 Rev B Lists Blanks The number of volumes in an alphabetic VOLSER range depends on the number of elements in the incrementing portion of the VOLSER range For an A to Z range in each character position the number of volumes can be calculated by 26 to the power of the number of positions that are being incremented A Z 26 26 AA ZZ 26 676 AAA ZZZ 263 17 576 AAAA ZZZZ 264 456 976 AAAAA ZZZZZ 265 11 881 376 AAAAAA ZZZZZZ 266 308 915 776 A list consists of one or more elements If more than one element is specified the elements must be separated by a comma or a blank space and the entire list must be enclosed in parentheses Keyword parameters and values may be separated by any number of blanks Control Statements The standard syntax conventions for control statements are as follows The only valid control statement information area is from column 1 to column 72 Columns 73 80 are ignored Parameters may be s
69. 10SA See BMC s INCONTROL for OS 390 and z OS Message Manual 208 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Appendix B MEDia RECtech and MODel Values This appendix provides values for MEDia RECtech and MODel parameters These parameters are used to specify transport and media characteristics They are specified in various NCS commands and control statements including the SMC TAPEREQ control statement Media Type MEDia The Media type is used to specify the desired type of media to be used for a data set It is specified in various NCS commands and control statements including SMC TAPEREQ control statement e SMC UNITAttr operator command HSC VOLATTR control statement The following table describes valid MEDia types IS Note e The SL8500 library supports the T9840A T9840B T9840C T9840D T9940B and T10000 media types and recording techniques e The SL3000 library supports the T9840C T9840D and T10000 media types and recording techniques Table 8 Media Types Media Type Description LONGItud Indicates standard or enhanced ECART capacity cartridges Standard Indicates a standard capacity cartridge Synonyms include CST MEDIA1 STD 1 3480 A standard capacity cartridge can be used on any longitudinal transport 1 e 4480 4490 9490 or 9490EE However if the data is written on the tape in 36 track the data cannot be read by an 18 track 4
70. 14001 Rev B Chapter 10 Sun StorageTek HTTP Server Messages Overview This chapter provides information about Sun StorageTek HTTP server messages See Chapter 2 SMC and Sun StorageTek Library Management for more information about the HTTP Server Message Format Messages are displayed on the console in the following format SMCnnnn_ message text where e SMC identifies the Storage Management Component SMC e nnnn is the four character message number e message text is the actual text displayed on the job log or system log Chapter 10 Sun StorageTek HTTP Server Messages 195 312614001 Rev B SKY001I SKY0131 Sun StorageTek HTTP Server Message Listing The following HTTP Server messages are listed numerically sKY001I name Server version starting on system running MSP level Explanation This is the HTTP server startup message SKY002E Error binding server socket terminating Explanation The server cannot bind to the specified network port The server shuts down SKY0031 name ready to accept requests Explanation The server name is ready for normal operation SKY004E Error opening server socket terminating Explanation The server cannot open a socket connection to the required network port The server shuts down SKYO05E Server select failed rc ret err msg Explanation An error occurred while listening for a client connection SKYOO6I TCP IP connection terminated Explanation The client connection wa
71. 480 transport ECART Indicates an enhanced capacity cartridge Synonyms include E ECCST ETAPE Long MEDIA2 3490E An ECART cartridge can be used only on 36 track transports 1 e 4490 9490 and 9490EE and is identified by a two tone colored case ZCART Indicates an extended enhanced capacity cartridge A ZCART cartridge can be used only on TimberLine 9490EE 36 track transports ZCART can be abbreviated as Z Appendix B MEDia RECtech and MODel Values 209 312614001 Rev B Table 8 Media Types Continued Media Type Virtual Description Indicates a VTV Virtual Tape Volume mounted on a VTD Virtual Tape Drive HELical Indicates a helical cartridge A helical cartridge can be used only on RedWood transports The following subtypes and abbreviations specify a helical cartridge DD3 indicates any DD3A DD3B or DD3C helical cartridge DD3A or A indicates a helical cartridge with a 10GB media capacity DD3B or B indicates a helical cartridge with a 25GB media capacity DD3C or C indicates a helical cartridge with a 50GB media capacity The seventh position in the external label is encoded with the cartridge type i e A B or C STK1 Indicates any T9840 cartridge STKIR Indicates a T9840 data cartridge STK1R can be abbreviated as R T9840 cartridge media capacities are 20GB T9840A and T9840B 40GB T9840C or 75GB T9840D STK1U Indicates a T9840A T9840B or T
72. 5 during MVS converter interpreter IDAX processing when the JCL or SMC DFSMS ACS routine esoteric contains at least one virtual device OFF do not adjust the volume counts for virtual allocations This is the default value ON if the JCL or IDAX substituted esoteric contains virtual devices for a scratch allocation then set the volume count to 255 Chapter 6 Commands and Control Statements 65 312614001 Rev B ALLOCJob Example In the following example the ALLOCDef command sets the minimum level of allocation exclusion to 4 and specifies that unit affinity and GDGALL chains are separated based on levels 1 4 It also specifies that when a user exit returns use specvol the allocation should be directed to drives in the esoteric SACSO ALLOCDEF MINLVL 4 SEPLVL MIN EXTVOL SACS USEREXIT 66 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCJob ALLOCJob Command The SMC ALLOCJob command is used to override SMC default allocation parameters by job name step name and PROC step Syntax ALLOCJOb JOBname jobname STEPname stepname PROCstep procstep Lavras 2 MAX mts serti AM level sep Note BYPass cannot be specified with the MINL vl or SEPLvl parameter It is only valid when JOBname is also specified Command Name ALLOCJob initiates the ALLOCJob command Parameter Descriptions LIst optionally lists current default allocation sett
73. 614001 Rev B In this scenario assume there are two separate libraries each defined by a different CDS SMC eliminates the need for LibraryStation in an MSP only environment The SMC can communicate directly with the remote HSC using the Sun StorageTek HTTP server Allocation and mount requests originating in an Initiator Address Space on MSPA are intercepted by the SMC on MSPA These requests are then sent to either the local HSCL executing on the same host or to the remote HSCR executing on the remote host MSPB The following example illustrates the LIBrary and SERVer commands for the SMC on MSPA LIBRARY NAME LCLLIB LOCSUBSYS HSCL LIBRARY NAME REMLIB SERVER NAME REMPATH LIBRARY REMLIB HOST MSPB LIBrary commands are required to define both the local and remote libraries See SMC Library Subsystem Selection on page 19 for information on how the SMC selects among multiple library subsystems to determine an owner for each allocation request 1 e each DD in a job step may have a different library subsystem owner 16 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scenario 6 SMC with Two Libraries One Local and One Remote with Multiple Paths In this scenario multiple libraries are configured with multiple paths as illustrated in the following figure Client Servers MSPA MSPB TCP IP stack HSCR Address space Initiator Address space SMC CGI
74. 614001 Rev B SERVer Command Name SERVer initiates the SERVer command Parameter Descriptions LIst optionally displays status information for all library server paths This is the default if no parameters are specified NAme optionally specifies a server path for which status is displayed name indicates the server path NAme optionally specifies the communication path or route to the server name indicates an identifier for the path parameters This name is reported in any communication error messages The following rules apply e The value must be one to eight characters in length The first character must be an alpha character The last character must be either an alpha character or digit e Any character between the first and last must be either an alpha character digit or hyphen ENable optionally enables the specified server path to be selected for allocation or mount requests DIsable optionally disables the specified server path If this is the only path to the library the library is unavailable for allocation or mount requests Chapter 6 Commands and Control Statements 97 312614001 Rev B SERVer LIBrary optionally specifies the library name associated with an actual ACS hardware configuration The LIBrary parameter must be specified when a new server is defined name indicates the library name This name is reported in any library error messages The following rules apply The
75. 63 SPECVOL EXTVOLESOT 64 ZEROSCR ZEROSCR 64 AMPND NOAMPND MOUNTDEF command startup exec parameter AUTOPENDMOUNT 85 MNTD command MOUNTDEF command VOLWATCH VOLWATCH 86 MOUNTMSG ROLLMSG 86 SLILIBRY macro MOUNTDEF command DELDISP DISMSCRReal DISMSCRVirt 85 NNLBDRV UNITATTR command 124 Note User exits 1 2 8 9 and 10 are managed and invoked by the SMC The SMC UEXit operator command is used to define the module that is invoked for a specific user exit It also allows you to enable or disable a user exit User exits are now documented in the NCS User Exit Guide What s New xv 312614001 Rev B About this Guide Audience This guide provides administration and configuration information for the Sun StorageTek Storage Management Component SMC software It is intended for storage administrators system programmers and operators responsible for configuring and maintaining the SMC software at their site Organization of This Guide This guide contains the following chapters Chapter 1 Introduction describes the SMC product its general features and functions Chapter 2 SMC and Sun StorageTek Library Management describes typical SMC configuration scenarios and provides an introduction to the SMC LIBrary and SERVer commands as well as the Sun StorageTek HTTP Server for MSP Chapter 3 Starting the SMC describes how to initialize the SMC software Chapter 4 SMC Allocation in a JES Envi
76. 9840C cleaning cartridge STK1U can be abbreviated as U STK1Y Indicates a T9840D cleaning cartridge STK1Y can be abbreviated as Y STK2 Indicates any T9940 cartridge STK2P Indicates a T9940 data cartridge STK2P can be abbreviated as P T9940 cartridge media capacities are 60GB T9940A or 200GB T9940B STK2W Indicates a T9940 cleaning cartridge STK2W can be abbreviated as W T10000T1 or Tl Indicates a full capacity 500GB T10000A or ITB T10000B cartridge T10000T1 can be abbreviated as T1 T10000TS or Indicates a smaller capacity 120GB T10000A or 240GB T10000B cartridge TS T10000TS can be abbreviated as TS T10000CT or Indicates a T10000 cleaning cartridge CT T10000CT can be abbreviated as CT 210 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B When this parameter is not specified a default is chosen based on the value of the RECtech parameter The following table shows default values used if MEDia is omitted Table 9 Media Type Defaults MEDia RECtech Entered Default 18track Standard 36track 36Atrack 36Btrack LONGItud 36Ctrack ZCART LONGItud LONGItud DD3 Helical DD3 STKIR STK1R34 STK1R35 STKIR STKIRA STK1RA34 STKIRA35 STKIRB STK1RB34 STKIRB35 STKIRAB STKIRAB34 STKIRAB35 STKIRC STK1RC34 STKIRC35 STKIRD STKIRDE STKIRDN STK1RD34 STK1RD35 STKIRDE4 STKIRDES STK2P STK2P34 STK2P35 STK2P STK2PA ST
77. B SMC0131 SMC0132 SMC0131 SMC0132 Cannot use LIBRARY SUBSYSTEM CCCCCCCC returned from user exit not active or disabled not in initial EDL Message Level 4 Explanation A user exit returned a library or subsystem name but the specified name was invalid or the referenced library had no defined drives in the Eligible Device List from the JCL System Action The library or subsystem name returned from the user exit is ignored Other data from the exit such as subpool is honored User Response Verify that the specified SUBSYSTEM or LIBRARY is active or correct the exit to specify a valid SUBSYSTEM or LIBRARY name Mount retry limit exceeded for volser VVVVVV device XXXX from LIBRARY LLLLLLLL SERVER SSSSSSSS Message Level 4 Explanation When SMC mount or mount TAPEREQ retrieval processing determines that an MSP mount is still pending and should be retried it waits before attempting the retry After the mount or mount policy retrieval retry limit is reached the SMC0132 message is displayed System Action The SMC will not continue to process the mount request after this message is issued User Response Investigate the cause of the HSC mount problem After resolving the problem issue the SMC RESYNChronize REStart command or the HSC MOUNT command if necessary 178 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0133 SMC0134 SMC0133 SMC0134 LIBRARY LLLLLLLL Library status
78. BLIC 420 2 33009311 DENMARK 45 4556 5040 e EGYPT 00 202 570 9442 FINLAND 358 9 525 561 e FRANCE 33 1 41 33 17 17 GERMANY 49 89 460 08 2788 GREECE 30 01 6188101 HONG KONG 852 2877 7077 HUNGARY 361 202 4415 INDIA 91 80 229 8989 INDONESIA 65 216 8333 IRELAND 353 1 668 4377 ISRAEL 972 9 9710500 ITALY 39 02 9259511 JAPAN 81 3 5779 1820 Korea 82 2 3453 6602 MALAYSIA 603 2116 1887 e MIDDLE East 00 9714 3366333 Maico 525 261 0344 NETHERLANDS 31 33 4515200 New ZEALAND 0800 786 338 e North West AFRICA 00 9714 3366333 Norway From Norway 47 22023950 To Norway 47 23369650 PAKISTAN 00 9714 3366333 PEOPLE s REPUBLIC OF CHINA 8610 6803 5588 PHILIPPINES 632 885 7867 POLAND 48 22 8747848 e PORTUGAL 351 21 413 4000 e RUSSIA 7 095 935 8411 SAUDI ARABIA 00 9714 3366333 SINGAPORE 65 216 8300 SOUTH AFRICA 27 11 256 6300 SPAIN 34 902 210 412 SRI LANKA 65 2168333 SWEDEN 46 8 631 22 00 SWITZERLAND 41 1 908 90 50 GERMAN 41 22 999 0444 FRENCH TAIWAN 886 2 25185735 e THAILAND 662 344 6855 TURKEY 90 212 335 22 00 UNITED KINGDOM 44 1276 416 520 UNITED STATES 1 800 422 8020 VENEZUELA 582 905 3800 VIETNAM 65 216 8333 WORLDWIDE HEADQUARTERS 1 650 960 1300 SU N THE NETWORK IS THE COMPUTER 2006 Sun Microsystems Inc All rights reserved Sun Sun Microsystems and the Sun logo are trademarks or registered trademarks of Sun Microsystems Inc in the United
79. C attempts to communicate with MSPC Once successful communication with MSPC is established the active path is not changed even if the server on MSPB becomes available Either of the following methods can be used to change the active path from MSPC to MSPB Disable the REMPATH2 server using the following command SERVER NAME REMPATH2 DISABLE The SMC automatically attempts to communicate with the first server in the list REMPATH1 Issue the RESYNChronize REStart command See RESYNChronize Command on page 95 for more information See SMC Drive Type Information Synchronization on page 19 for information about how the SMC acquires drive type information from the HSC 14 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scenario 5 SMC with Two Libraries One Local and One Remote In this scenario the SMC can coordinate allocation and mount requests among multiple library hardware configurations as illustrated in the following figure Client Server MSPA TCP IP stack SMC Address space Initiator Address space HSCL Address space on MSPB Remote CDS HSCR Address space CGI Routines SMC Address space StorageTek HTTP SERVER TCP IP stack Local Library Figure 5 NCS with Two Libraries One Local and One Remote with Multiple Paths Chapter 2 SMC and Sun StorageTek Library Management 15 312
80. C subsystem System Action Allocation influencing continues for the job User Response Correct the user exit x SMC U1899 ABEND at CCCCCCCCn Message Level 0 Explanation An SMC task has abended in module CCCCCCCC at abend sequence number n System Action If the abend occurs in the address space of a tape allocation job the SMC subsystem does not influence the job s allocation If the abend occurs in the SMC started task address space a restart of the SMC subsystem may be required User Response Look for SMC or Fujitsu related messages in the SYSLOG or job log Save the associated logs dump data set and JCL and contact Sun Microsystems Support MSGJOB LVL nn for DEFAULT SETTING JOBNAME JJJJJJJJ STEPNAME SSSSSSSS PROCSTEP PPPPPPPP Message Level 0 Explanation A MSGJOB command was specified with the LIST keyword Each unique job job step and PROC step entry found in the MSGJOB queue is displayed in a separate SMC0054 message followed by the SMC defaults in a final SMC0054 message nn indicates the message level and any messages at that indicated level or lower are produced on that job s job log in JES System Action None User Response None Chapter 9 SMC Messages 155 312614001 Rev B SMC0055 SMC0057 SMC0055 ALLOCJOB BYPASSed MINLVL nn SEPLVL MIN MAX nn for JOBNAME JJJJJJJJY STEPNAME SSSSSSSST PROCSTEP PPPPPPPP SNAPDUMP DDDDDD PPPPPPPP Message Level 0 Explanation An ALLOCJOB comma
81. C0037 Invalid SMC startup parameters subsystem terminating Message Level 0 Explanation During initialization the SMC subsystem initialization program detected an error processing the execution parameter string System Action The SMC subsystem terminates User Response Look for SMC related messages in the SYSLOG or job log Associated messages may be but are not limited to SMC0032 SMC0033 SMC0034 or SMC0035 150 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0038 SMC0039 SMC0040 SMC0038 SMC0040 Another SMC system SSSS is already active Message Level 0 Explanation During initialization the SMC subsystem initialization program detected a different SMC subsystem SSSS already active on the system System Action The initializing SMC subsystem terminates User Response Only one SMC can be active on a system at a time e IfSMC SSSS is active and is preventing the current SMC from initializing terminate SMC SSSS IfSMC SSSS was terminated abnormally and is not truly active restart the current SMC subsystem with the RESET execution parameter Identically named subsystem SSSS is already active Message Level 0 Explanation During initialization the SMC subsystem initialization program detected an identically named subsystem SSSS already active on the system System Action The initializing SMC subsystem terminates User Response Start the SMC with a different subsystem na
82. DISP parameter of the HSC LIBGEN SLILIBRY macro OFF Retain the virtual volume as nonscratch when MSP indicates delete disposition in the dismount message This is the default setting ON Scratch the virtual volume when MSP indicates delete disposition in the dismount message Chapter 6 Commands and Control Statements 85 312614001 Rev B MSGDef VOLWatch specifies whether the SMC issues a message when a library volume is to be mounted on a nonlibrary drive OFF Do not issue a message when a library volume is to be mounted on a nonlibrary drive ON Issue a console message when a library volume is to be mounted on a nonlibrary drive The message identifies the VOLSER that must be ejected from the library to satisfy the mount ROLLmsg specifies whether mount messages handled by the SMC are allowed to roll off the operator console before mount requests are satisfied ON Mount messages are allowed to roll off the console screen before mounts are satisfied This is the default setting IS Note You can limit the rolling of specific mount messages e g TMS007 by presetting the messages xxxxRCDC Request to Change Descriptor Codes flag word xxxxRBFB1 The SAMPLIB includes a sample MPF USEREXIT to preset the xxxxRCDC flag OFF Mount messages remain on the console screen until mount requests are satisfied 86 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B MSGDef MSGDef Command The SMC MSGDef
83. ECH 36B MEDIA ECART VOL000 requires a 9490 drive and if TLACSO contains both 9490 and 9490EE drives the 9490EE drives are excluded from consideration for this allocation IS Note If your environment contains drives that support different densities for the same media such as a combination of T9840A and T9840C drives it is recommended that you set the default MINLVL to 3 so that jobs will fail rather than allocating volumes to a drive with an incompatible density Chapter 4 SMC Allocation in a JES Environment 33 312614001 Rev B Exclusion Level 4 Ifa TAPEREQ statement specifies an esoteric unit name for this allocation request the SMC verifies the esoteric unit name is defined to MSP If the esoteric passes this test any drives in the original EDL that are not also defined to the esoteric unit name are excluded from consideration for this allocation For example DD2 DD UNIT CART VOL SER TRMM01 DSN SYS4 TR1 DATA DISP OLD The following TAPEREQ statement is defined to SMC TAPEREQ DSN SYS4 TR1 ESOT TLACS1 RECT LONGI The drives that are not defined to the esoteric TLACS1 are excluded from consideration for this allocation Ifno TAPEREQ statement specifies an esoteric for this allocation request User Exit 08 or 10 return codes and values can define the criteria for drive exclusion at this level The user exit return codes can direct the SMC to select nonlibrary drives a specific ACS or the user exit can return an e
84. EDIA USERPOLICY Exclude drives based on the media of available scratch volumes in subpool Primary source TAPEREQ SUBPOOL parameter Secondary source User Exit 02 subpool values Tertiary source scratch subpool 0 SUBPOOL Exclude drives based on available scratch location type i e library nonlibrary or virtual LOCTYPE Exclude drives based on the SMC ALLOCDef command ZEROSCR parameter Exclude drives based on the requested recording technique Primary source TAPEREQ RECTECH parameter ZEROSCRATCH POLRECTECH Keywords associated with each exclusion level are specified in the exclusion criteria displayed in mes sage SMC0046 The MINLVL parameter value default level 2 on the ALLOCDef or ALLOCJob command applies to both scratch and specific volume requests Even though level 2 has no meaning for scratch level 2 is con sidered the default minimum level Chapter 4 SMC Allocation in a JES Environment 37 312614001 Rev B Exclusion Level 1 The SMC excludes virtual drives if the volume label type requested is NL nonlabeled This is the only required criterion Refer to the VTCS documentation for more information about virtual volumes The SMC excludes all drives defined with the SMC UNITATTR MODEL IGNORE Exclusion Level 2 For virtual allocation requests the SMC excludes virtual drives that reside in a VTSS to which the VTV cannot be migrated and recalled Refer to the VTCS doc
85. G file Outgoing requests and incoming responses can be logged from both local and remote libraries This command is intended to be used primarily as directed by Sun Microsystems support personnel In addition you may specify command parameters to control the following e length of the log data line written independently of the SMCLOG DCB attributes whether log data is appended to an existing file e handling of SMCLOG EOF conditions Note EOFRESTART used to restart logging at SMCLOG EOF simply restarts the log at EOF and does not wrap the log i e all data prior to EOF is lost Syntax OFF alas cia STArt Pore STOp Chapter 6 Commands and Control Statements 81 312614001 Rev B MOUNTDef Command Name LOG initiates the LOG command Parameter Descriptions LIst optionally lists current SMC LOG settings This is the default if no parameters are specified It cannot be specified with any other parameter OFF optionally resets all LOG settings to original SMC default settings and stops SMC logging if started It cannot be specified with any other parameter SEnd specifies whether the SMC logs request data sent to a library subsystem or server OFF do not log requests sent to a library subsystem or server to the LOG file This is the default value ON log requests sent to a library subsystem or server to the LOG file REcv specifies whether the SMC logs response data received from a li
86. H VOLWATCH 86 MOUNTMSG ROLLMSG 86 SLILIBRY macro MOUNTDEF command DELDISP DISMSCRReal DISMSCRVirt 85 NNLBDRV UNITATTR command 124 Note User exits 1 2 8 9 and 10 are managed and invoked by the SMC The SMC UEXit operator command is used to define the module that is invoked for a specific user exit It also allows you to enable or disable a user exit User exits are now documented in the NCS User Exit Guide Chapter 1 Introduction 3 312614001 Rev B Chapter 2 SMC and Sun StorageTek Library Management Overview This chapter describes sample SMC configuration scenarios and provides an introduction to the SMC LIBrary and SERVer commands as well as the Sun StorageTek HTTP Server for MSP The SMC provides the interface between Fujitsu s MSP EX operating system and Sun StorageTek HSC library control systems These library control systems can operate in several ways e The HSC can operate on the same local MSP host as the SMC e The HSC can operate on a remote MSP host e A combination of local and remote library control systems can be used In a complex configuration where you wish to define remote HSC systems or enable simple server switching by defining multiple server paths to one or more libraries you must use the SMC LIBrary and SERVer operator commands and the Sun StorageTek HTTP Server for MSP SMC LlBrary and SERVer Commands In a configuration including both local and remote libraries all libraries m
87. JOB TRACE JOB TESTJOB In the following example the TRace command specifies that tracing is disabled for all SMC initiator processes and SMC subsystem subtasks TR OFF In the following example tracing is enabled for SMC initiator allocation and message handling processes for any job with jobname ABC TR JOBN ABC ALLOC MSGHN In the following example tracing is enabled for the SMC subsystem command component TR SUBSYS CMD Chapter 6 Commands and Control Statements 117 312614001 Rev B UEXit In the following example tracing is disabled for all SMC subsystem subtasks TR SUBSYS OFF In the following example tracing is disabled for all jobs whose job name begins with PROD TR OFF JOB PROD 118 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B UEXit TREQDef Command The TREQDEF command specifies and loads the definition data set containing your tape request TAPEREQ parameter statements This command may be issued from the SMCPARMS or SMCCMDS data set or it may be issued by an operator IS Note The SMC TREQDEF operator command replaces the HSC TREQDEF command and control statement Syntax DATASET dsn VOLume volser UNIT unitname HOSTID hostid DSN dsn RELOAD Command Name TREQDef initiates the TREQDef command Parameter Descriptions List lists information about the definition
88. K2PA34 STK2PA35 STK2PB STK2PB34 STK2PB35 Virtual Virtual Appendix B MEDia RECtech and MODel Values 211 312614001 Rev B Recording Technique RECtech The recording technique or RECtech is used to specify the method used to record data tracks on the tape surface for the desired data set It is used in the following NCS commands and control statements e SMC TAPEREQ control statement e SMC UNITAttr operator command HSC VOLATTR control statement IEY Notes The following table describes valid recording techniques The SL8500 library supports the T9840A T9840B T9840C T9840D T9940B and T10000 media types and recording techniques The SL3000 library supports the T9840C T9840D and T10000 media types and recording techniques e The T9940B transport supports both 3490 and 3590 image definitions However With VSM T9940B transports may only be defined as 3490 image devices With a native interface T9940B transports may only be defined as 3590 image devices Table 10 Recording Techniques Recording Technique LONGItud Description Indicates any device that records data tracks in a linear format along the length of the tape surface These devices include 4480 4490 9490 and 9490EE transports 18track Indicates a 4480 transport 36track Indicates a 4490 9490 or 9490EE transport any device that records in 36 track mode 36Atrack Indicates a 4490 t
89. KIRDE Indicates an encryption enabled T9840D transport STK1RDE4 Indicates an encryption enabled 3490E image T9840D transport STK1RDES Indicates an encryption enabled 3590 image T9840D transport STK2P Indicates any T9940 transport STK2P34 Indicates a 3490E image T9940 transport STK2P35 Indicates a 3590 image T9940 transport STK2PA Indicates a T9940A transport STK2PA34 Indicates a 3490E image T9940A transport STK2PA35 Indicates a 3590 image T9940A transport STK2PB Indicates a T9940B transport STK2PB34 Indicates a 3490E image T9940B transport STK2PB35 Indicates a 3590 image T9940B transport TIOK Indicates all T10000 transports TIOKN Indicates all non encrypted T10000 transports TIOKE Indicates all encrypted T10000 transports TIA Indicates any T10000A transport Appendix B MEDia RECtech and MODel Values 213 312614001 Rev B Table 10 Recording Techniques Continued a Description TIAN Indicates a non encryption enabled 3490E or 3590 image T10000A transport T1A34 Indicates a non encryption enabled 3490E T10000A transport T1A35 Indicates a non encryption enabled 3590 T10000A transport TIAE Indicates an encryption enabled 3490E or 3590 image T10000A transport T1AE34 Indicates an encryption enabled 3490E image T10000A transport T1AE35 Indicates an encryption enabled 3590 image T10000A transport TIB Indicates any T10000B transport TIBN Indicates a non encryption
90. MC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Customer initiated Maintenance Customer initiated maintenance begins with a telephone call from you to Sun Microsystems StorageTek Support You receive immediate attention from qualified Sun personnel who record problem information and respond with the appropriate level of support To contact Sun Microsystems StorageTek Support about a problem 1 Use the telephone and call T 800 872 4786 1 800 USA 4SUN inside the United States T 800 722 4786 Canada For international locations go to http www sun com service contacting solution html for the appropriate telephone number 2 Describe the problem to the call taker The call taker will ask several questions and will either route your call to or dispatch a support representative If you have the following information when you place a service call the process will be much easier Account name Site location number Contact name Telephone number Equipment model number Device address Device serial number if known Urgency of problem Fault Symptom Code FSC Problem description About this Guide xxvii 312614001 Rev B Sun s Worldwide Offices You may contact any of Sun s worldwide offices to discuss complete storage service and support solutions for your organization You can find address and telephone number information on Sun s ex
91. MC Client Host SMCUDBX SLUDR S a Scratch Extract File Scratch Extract File Tape Management Input File SLUDRSMC SLUCONDB MSPB HSC Server Host Figure 9 Scratch Synchronization Between SMC Client host and HSC CDS 130 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B If the client and server share a tape management system the HSC utility SLUCONDB may be run directly using the common tape management system data base as input If however the client host has a tape management system that is not accessible to the HSC host the SMC utility SMCUDBX can be used to extract scratch volumes from the tape management system using label and date parameters The SMCUDBX output can then be used as input on the HSC host to the SLUCONDB utility The SMC process supports timing synchronization by comparing the GMT time of the SMCUDBX run with the last select time of the HSC CDS volume record If the volume was selected after the SMC scratch run it is not eligible for scratch by SLUCONDB Running the SMC Scratch Extract Utility You can run the SMC scratch extract utility regardless of whether the SMC is executing on the host SMCUDBX processes the CA 1 Tape Management Catalog TMC the CA DYNAM TLMS Volume Master File VMF or the Zara database and selects the volume serial numbers for processing based on information specified on the PARM par
92. Manual Volume 1 CTT102A See CA 1 User Manual Volume 1 CTT103A See CA 1 User Manual Volume 1 CTT104A See CA 1 User Manual Volume 1 CTT105A See CA 1 User Manual Volume 1 TMS001 See CA 1 User Manual Volume 1 TMS002 See CA 1 User Manual Volume 1 TMS004 See CA 1 User Manual Volume 1 TMS005 See CA 1 User Manual Volume 1 TMS007 See CA 1 User Manual Volume 1 TMS008 See CA 1 User Manual Volume 1 TMS009 See CA 1 User Manual Volume 1 TMS010 See CA 1 User Manual Volume 1 Appendix A Intercepted Messages 207 312614001 Rev B Table 7 Tape Management System Messages CA 1 Continued Message ID Description TMSO11 See CA 1 User Manual Volume 1 TMS014 See CA 1 User Manual Volume 1 TMS015 See CA 1 User Manual Volume 1 IECTMS7 See CA 1 User Manual Volume 1 CA F810A See CA 1 Message Guide CA F813A See CA 1 Message Guide CONTROL M TAPE formerly CONTROL T Messages The following CONTROL M TAPE messages are intercepted by the SMC Refer to the appropriate BMC publication for the exact format and meaning of each message Message ID Description CTT100A See BMC s INCONTROL for OS 390 and z OS Message Manual CTT101A See BMC s INCONTROL for OS 390 and z OS Message Manual CTT102A See BMC s INCONTROL for OS 390 and z OS Message Manual CTT103A See BMC s INCONTROL for OS 390 and z OS Message Manual CTT104A See BMC s INCONTROL for OS 390 and z OS Message Manual CTT
93. PLvl parameter replaces the function of the HSC ALLOC command UNITAFF and GDGALL parameters These parameters are no longer supported If your installation previously specified UNITAFF NOSEP and GDGALL NOSEP to preserve that behavior specify a SEPLvl value of 3 on the ALLOCDef command If your installation previously specified UNITAFF SEP and GDGALL SEP no SEPLVL parameter change is required since the default SMC behavior separates affinity chains at the maximum separation level Refer to the ALLOCDef and ALLOCJob commands in Chapter 6 Commands and Control Statements for more information about setting an installation default minimum exclusion level and unit affinity separation level Chapter 4 SMC Allocation in a JES Environment 47 312614001 Rev B Drive Prioritization After drive exclusion has occurred during the SSI24 common allocation event the SMC then proceeds to assign a priority value to each remaining eligible drive IEY Note Between a common allocation event SSI24 for a tape and its tape allocation event MSP may make drives ineligible When this occurs the SMC retests the job step to ensure that it is allocatable with the remaining drives If it is not drives that were excluded by the SMC SSI24 process are reincluded until the job step is allocatable One exception to the reinclusion process occurs when the ALLOCDef MIAcompat parameter is set to ON In this case exclusion is already done so drive reinclusio
94. RT procedure DSN processes commands contained in the specified data set dataset indicates the specified data set Note If the DSN parameter specifies a member name the full data set must be enclosed in single quotes HOST optionally specifies a host name for which this READ command is valid If this parameter is specified the READ command is only processed when the specified hostname matches the MSP host If this parameter is not specified the READ command is processed regardless of the MSP host hostname indicates the hostname Chapter 6 Commands and Control Statements 93 312614001 Rev B SERVer Example Note Specification of the HOST parameter allows you to share a single SMC parameter file set across multiple MSP hosts as shown in the following example your parmlib COMMCMDS MSGDEF CASE MIXED other common SMC parameter settings READ DSN your parmlib MSP1CMDS HOST MSP1 READ DSN your parmlib MSP2CMDS HOST MSP2 your parmlib MSP1CMDS DRIVEMAP CL ABB AB7 SE BB0 BB7 your parmlib MSP2CMDS DRIVEMAP CL CB CB7 SE BB0 BB7 The file COMMCMDS contains SMC parameter settings applicable to all hosts and the READ commands with HOST specifications for your MSP hosts The file MSP1CMDS contains SMC specifications applicable only to MSP host MSP1 while the file MSP2CMDS contains SMC specifications applicable only to MSP host MSP2 In the following example the READ command is used to process com
95. Routines SMC Address space HSCL Address space StorageTek HTTP SERVER TCP IP stack Remote CDS Remote Library HSCR Address space Local Library CGI Routines SMC Address space MSPC TCP IP stack StorageTek HTTP SERVER Figure 6 NCS with a Local Library and a Remote Library with Two Server Instances This scenario is a combination of scenarios and 4 The following example illustrates the LIBrary and SERVer commands for the SMC on MSPA LIBRARY NAME LCLLIB LOCSUBSYS HSCL LIBRARY NAME REMLIB SERVER NAME REMPATH1 LIBRARY REMLIB HOST MSPB SERVER NAME REMPATH2 LIBRARY REMLIB HOST MSPC Chapter 2 SMC and Sun StorageTek Library Management 17 312614001 Rev B Client Server Drive Address Mapping SMC 6 1 and HSC 6 1 provide new facilities to allow drive addresses to be different between client and server hosts The following table provides scenarios to help you determine whether client server drive address mapping is required and what actions and facilities are required Table 1 SMC Client Server Drive Address Mapping Scenarios Scenario Drive Address Mapping Action Required Client server processing is not used None Each MSP host runs a copy of HSC Client server processing is used None Device addresses are identically defined for all hosts participating in a single client server network Client server p
96. SGJob 90 READ 93 RESYNChronize 95 SERVer 96 TAPEREQ 101 TCPip 112 TRace 114 TREQDef 119 UEXit 121 UNITAttr 124 USERMsg 126 organization of this Guide xvii P parameters 234 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCDef command 61 ALLOCJob command 67 CMDDef command 71 DRIVemap command 73 LIBrary command 77 LIst command 79 LOG command 82 MOUNTDef command 84 MSGDef command 87 MSGJob command 90 MSP START Command 25 READ command 93 RESYNChronize command 95 SERVer command 97 SMC EXEC Statement 23 TAPEREQ command 104 TCPip command 112 TRace command 115 TREQDef command 119 UEXit command 122 124 USERMsg command 126 partners web site SUN xxvi preferencing device 109 publications related xxv R READ command 93 recovery procedures 127 related publications xxv RESYNChronize command 95 S scratch requests 37 SERVer command 96 SL8500 library 209 229 SMC allocation 27 configuration scenarios 7 control statements 57 differences from NCS 4 1 and below 217 functions 1 initializing 21 interaction with other software 219 library subsystem selection 19 message handling 51 messages 139 operator commands 57 policy and drive type information synchronization 19 recovery procedures 127 starting 21 Tape Management Extract utility 129 SMCCMDS data set 59 SMCPARMS data set 59 specific requests 32 SSI23 dynamic allocation 28 SSI24 common allocation 28 START Command MSP
97. SKs FUNIT uuuu A Command Name LIst initiates the LIst command Parameter Descriptions Address specifies the address at which to begin listing SMC memory contents address indicates the address The value entered must be a valid hexadecimal address Length optionally specifies the length of SMC memory bytes to be listed length indicates the length The value entered must be a valid hexadecimal value between 1 and FFFF Memory is listed beginning at the location specified in the address parameter The default value is 100 decimal 256 CB specifies the internal SMC control block to be listed control block name indicates the control block name SMC control blocks are listed for diagnostic purposes Specify control block name only as directed by Sun Microsystems Software Support Chapter 6 Commands and Control Statements 79 312614001 Rev B LOG Example TASKs Lists the tasks in the SMC subsystem address space FUNIT Lists SMC control blocks associated with the specified unit address es uuuu indicates the unit address es In the following example the LIst command displays the given length FFF of accessible storage beginning with address 01FE0O LIST A 1FE L FFF 80 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B LOG LOG Command The SMC LOG command logs XML transactions sent and or received from library subsystems and servers to an SMCLO
98. SMC performs the same functions for dynamic allocations that the POSTSCAN C I processes for common allocations drive exclusion GDGALL affinity separation esoteric unit name replacement mount deferral SSI24 Common Allocation Exceptions Rs During SSI24 common allocation processing the SMC performs the following processes to arrive at the best set of eligible drives drive exclusion unit affinity separation defer processing when CAIRTS is set to ON EDL updated with the drive exclusion results when MIACOMPAT is set to ON The results of the drive exclusion process are not reflected in MSP control blocks until tape allocation time unless MIACOMPAT is set to ON The results of unit affinity separation are used to update MSP VOLUNIT entries in the SIOT The SMC does not influence the following types of cartridge tape allocation demand allocation i e request for a specific drive s Note The SMC does perform DEFER processing for demand allocation allocations excluded explicitly by entering the ALLOCJob command BYPASS parameter Refer to the description of this command in Chapter 6 Commands and Control Statements allocations where the list of eligible devices contains only devices that are unknown i e not virtual not library and not defined in an SMC UNITAttr command 28 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Drive Exclusion When the SMC determines an interest
99. SMSDEF settings CCCC CCCC Message Level 0 Explanation An SMSDEF command has been issued with the LIST keyword The SMC0067 multiline message lists the current settings for the SMC subsystem Refer to the SMSDEF command for parameter descriptions System Action None User Response None SMCERSLV release level LLLLLL1 does not match SMC release level LLLLLL2 Message Level 0 Explanation Module SMCERSLYV is at release level LLLLLL1 which does not match SMC release level LLLLLL2 System Action The SMC does not initialize User Response Reassemble SMCERSLY at the correct release level and restart the SMC SMC maintenance has been applied reassemble SMCERSLV Message Level 0 Explanation SMC maintenance was applied and affected the module SMCERSLY but SMCERSLV was not reassembled System Action The SMC does not initialize User Response Reassemble SMCERSLV using the correct level of SMC macros and restart the SMC Chapter 9 SMC Messages 159 312614001 Rev B SMC0074 SMC0077 SMC0074 Unsupported virtual label type for job JJJJJJJJ step SSSSSSSS DD DDDDDDDD Message Level 8 Explanation All virtual devices were previously excluded for the DD because of an unsupported label type NL A subsequent exclusion criteria requesting virtual drives could not be honored Message SMC0046 describes the criteria not honored System Action The DD is allocated to a nonvirtual drive Nonlibrary drives are preferred
100. Single HSC Library Configuration with Multiple Remote Server Paths 13 Scenario 5 SMC with Two Libraries One Local and One Remote ooooo o 15 Contents v 312614001 Rev B Scenario 6 SMC with Two Libraries One Local and One Remote with Multiple Paths Client Server Drive Address Mapping 0 00 e cece eee ees SMC Drive Type Information Synchronization 45 SMC Library Subsystem Selection nannan c ccc eee ee Chapter 3 Starting the SMC ncn ec e eke cece dee ee tee teaser ebe eee eeeteeeeee ane OVETVICW A ey a ae en ee Creating the SMC START Procedure 0 cece eee nes SMC EXEC Statements recre 000 cece eee een e eee EE Executing the SMC START Procedure 00 00 c eee eee eee eee Chapter 4 SMC Allocation in a JES Environment oocooccconoo eee COVERVICW 5355 scapes eles a A pact 4 Loa raced aca reece eta ete qc Jobs Selected for SMC Allocation Management 00 0 0 00 ee eae SSI23 Dynamic Allocation 0 0 seaun sennen renere SSI24 Common Allocation 00 0 c cece eens Exceptions te lt 6 hyde oak Psy tea a a ed aja Meal bua Wal ne Drive EXClUsiOnie sr sacs dais dada tado Minimum Exclusion Level 2 0 c eee cee eens Subsequent Levels ii ip BE ees Intentionally Failing a Job 0 00 Specific Volume Request Drive Exclusion Criteria Scratch Volume Request Drive Exclusion Criteria
101. Software Library Control Unit LCU The portion of an LSM that controls the movements of the robot library database A file or data set containing information about the location and status of the removable media volumes such as cell location scratch status Also called a control data set CDS library drive A cartridge drive in the ACS as distinct from a stand alone cartridge drive Library Management Unit LMU A hardware and software product that coordinates the activities of one or more LSMs LCUs library mode The operation of a 4480 Cartridge Subsystem as part of a 4400 Automated Cartridge System as opposed to manual mode in which the operator inserts cartridges into the transports See manual mode LibraryStation Software that allows MSP hosts to share ACS facilities with client systems Library Storage Module LSM The standard LSM 4410 a twelve sided structure with storage space for up to around 6000 cartridges It also contains a free standing vision assisted robot that moves the cartridges between their storage cells and attached transports See also PowderHorn SL8500 and WolfCreek LMU See Library Management Unit local area network LAN A network in a small local geographic area local port The designation of a given application or process among many that are available for a TCP IP capable host processor local socket The address combination of a TCP IP capable ho
102. States and other countries
103. Swap messages from the following Tape Management Systems e CA 1 CA DYNAM TLMS e AutoMedia Zara CONTROL T For tape management systems that supply a subpool the subpool is interpreted by the SMC and used as the requested subpool name unless overridden by user exit 01 ora TAPEREQ statement Related messages include e CTS002 e CTTIOIA e CTT104A e TMS002 SMC Swap Processing The SMC automates the swap process I O error or operator initiated in the same manner as HSC enhanced swap processing This eliminates the need for operators to find a compatible swap to device when DDR has chosen an incompatible device If the SMC cannot find a compatible swap to device or if all compatible devices are busy the SMC issues a message and control is returned to DDR processing with no further SMC involvement Note that enhanced swap processing is the only mode supported in SMC The SMC swap process begins when one of the following messages is issued KHE2001 SWAP XXX1 TO XXX2 1 0 ERROR KHE2031 ERROR ON XXX1 SELECT NEW DEVICE KHE2051 SWAP XXX1 1 0 ERROR If device XXX1 is known to the SMC as a library or nonlibrary device defined with an SMC UNITATTR command the SMC suppresses the message and begins the automatic swap process Chapter 5 SMC Message Handling 53 312614001 Rev B ES The SMC issues one of two messages SMC0108 No compatible drive found for SWAP processing Or when a compatible drive can be selected by the
104. TEM TASKS A PCE A TCB USE CT S PROGRAM JOBNAME JOBID LAST XXXXXXXX XXXXXXXX 00001 BB W SMCBINT JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX 00001 BM W SMCBMID JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX 00001 QM W SMCQMGR JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX B0BB1 J XXXXXXXX XXXXXXXX 00001 O W SMCOCMD JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX 00001 BL W SMCBLOG JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX 00001 QW X SMCQWRK JJJJJJJJ Jnnnn TTTTTT XXXXXXXX XXXXXXXX nnnnn QW X SMCQWRK JJJJJJJJ Jnnnn TTTTTT SMCQWRK executing tasks nn waiting tasks nn requests nn Message Level 0 Explanation An SMC LIST TASK command was issued The SMC0086 multiline message lists status of each SMC subsystem task The last line lists the number of SMCQWRK tasks currently executing waiting for work as well as the total number of requests processed System Action None User Response None EXTVOLESOT esoteric EEEEEEEE not found at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation An ALLOCDEF command was issued with the EXTVOLESOT keyword specifying EEEEEEEE However the specified esoteric name is not a valid MSP esoteric System Action The specified ALLOCDEF command is not processed User Response Reissue the ALLOCDEF command specifying a valid MSP esoteric name Unable to Lacquire release resource CCCCCCCC attempt by JJJJJJJJ XXXXXXXX1 owned by XXXXXXXX2 Message Level 0 Explanation A shared SMC resource could not be acquired
105. TEP STEP1 MINLVL 70 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B CMDDef Command CMDDef The SMC CMDDef command is used to assign an SMC command prefix Syntax LIst e ______ __ PREFix command prefix Command Name CMDDef initiates the CMDDef command Parameter Descriptions LIst optionally lists the current command prefix This is the default if no parameters are specified It cannot be specified with any other parameter PREFix optionally specifies a command prefix for the SMC subsystem IS Note This parameter may only be specified in the SMCPARMS data set command prefix indicates the desired command prefix characters The value entered must be one to eight characters in length and must meet the following requirements Valid characters include A Z 0 9 lt gt amp The command prefix cannot include a command string a command abbreviation or any string that invokes a command The command prefix cannot include a string that is a subset or superset of an existing prefix beginning with the same character The command prefix used for SMC must be different from the prefix used for HSC or any other defined subsystem Otherwise unpredictable results may occur Chapter 6 Commands and Control Statements 71 312614001 Rev B DRIVemap Example In the following example the CMDDef command is specified in the SMCPARMS data set as
106. The SMCPARMS data set is used for user configured items that cannot be changed while the SMC is active The SMCPARMS data set cannot be reprocessed using the READ command The following is a sample SMCPARMS member entry CMDDEF PREFIX B F IEY Note It is recommended that you include only the CMDDef PREFix and USERMsg ID parameter settings in the SMCPARMS data set Specify all other commands in the SMCCMDS data set SMC Commands that Specify JOBname STEPname and PROCstep SMC ALLOCJOB MSGJOB and TRACE commands that allow specification of JOBname STEPname or PROCstep are evaluated by the SMC in order of most specific to least specific job name specification Therefore commands can be entered in any order Consider the following example Two ALLOCJob commands are entered ALLOCJOB JOBNAME NOALLOC MINLVL 4 ALLOCJOB JOBNAME NOALLOC1 MINLVL 3 Regardless of the order in which these commands are entered job name NOALLOC1 is processed with MINLVL 3 because this command s job name is more specific than job name NOALLOC IS Note The above behavior does not apply to TAPEREQ statements which are always evaluated in the order in which they appear in the TREQDEF DD Chapter 6 Commands and Control Statements 59 312614001 Rev B ALLOCDef SMC Command and Control Statement Descriptions This section describes SMC operator commands and control statements Syntax parameter descriptions and examples are included for each
107. The server has started to shut down Task tttt unable to get client id Explanation An error occurred while passing a socket connection to the work task tttt Task t waiting for work Explanation The worker task is now idle after completing a request Task t shutting down Explanation Task has commenced shutting down Task t unable to allocate dir list buffer Explanation The worker task was unable to allocate a memory buffer needed for a directory listing Task t unable to open directory readme Explanation The worker task encountered an error when attempting to open a directory readme file while listing a directory Chapter 10 Sun StorageTek HTTP Server Messages 201 312614001 Rev B SKY122E SKY1301 SKY122E SKY123E SKY1241 SKY125E SKY126E SKY127E SKY128E SKY129E SKY1301 Task tt connection error with xxx xxx xxx xxx errno error_text Explanation The worker task encountered a connection error error number errno text error_text with the client at IP address xxx xxx xxx xxx Task t connection eof from XXX XXX XXX XXX Explanation For worker task the connection to client at IP address xxx xxx xxx xxx ended Task t connection terminated by peer adr Explanation The network connection to worker task t was terminated by the client with IP address adr Task t cmp abend aaa caught Explanation The abend handler for task t in component cmp intercepted a type aaa abe
108. UX02 08 HONOR Appendix C Differences Between SMC and HSC 6 0 and Below 217 312614001 Rev B 4 SMC supports the ability to specify any esoteric for substitution in a user exit or TAPEREQ provided that e Devices cannot be added to the original list of eligible drives The specified esoteric must be a valid esoteric and must contain one or more drives in common with the original list of eligible drives Customers with TAPEREQs or user exits with specified esoterics that were invalid in previous releases may experience unexpected results when these esoterics are honored by SMC 5 In SMC virtual tape is treated more like a unique device type and may be used when policies include both real and virtual drives For example if a subpool including real and virtual volumes is specified SMC allocation may select virtual drives 6 SMC ignores allocations for tape DDs when all devices in the EDL are undefined to any library subsystem This behavior allows better coexistence between Sun StorageTek software and other vendor products that influence tape allocation It is recommended that you use SMC UNITATTRs to define Sun StorageTek devices outside the library and if necessary include SMC UNITATTRs with MODEL IGNORE for nonexistent drives outside the library 7 The SMC uses SMC UNITATTRs to determine characteristics of drives outside the library 8 A single version of an allocation user exit is executed regardless of the number of li
109. XXXX Message Level 0 Explanation A UNITATTR command has been issued specifying device XXXX The device is defined to a library subsystem known to SMC The SMC obtains the device model from the library subsystem System Action The UNITATTR command does not process the device User Response None LOG settings CCCC CCCC Logging currently INACTIVE ACTIVE Message Level 0 Explanation A LOG command was issued with the LIST keyword The SMC0155 multiline message lists the current settings and status for the SMC subsystem Refer to the LOG command for parameter descriptions In addition a log status of ACTIVE indicates that logging has been started INACTIVE indicates that logging has not been started or has been stopped at EOF System Action None User Response None Chapter 9 SMC Messages 185 312614001 Rev B SMC0156 SMC0159 SMC0156 SMCLOG file is not currently opened Message Level 0 Explanation A LOG command has been issued with the STOP keyword However logging is not currently active System Action The LOG command is ignored User Response None SMC0157 SMCLOG file is already opened Message Level 0 Explanation A LOG command has been issued with the START keyword However the logging is already active System Action The LOG command is ignored User Response None SMC0158 No SMCLOG DD logging cannot be started Message Level 0 Explanation A LOG command has been issued with the
110. ameter of the JCL EXEC statement For CA 1 and CA DYNAM TLMS SMCUDBX calls the appropriate tape management system database READ routine For Zara SMCUDBX invokes the SLUDRZAR module which in turn invokes an application programming interface API to read Zara s database The data returned from these routines is used to format the SMC scratch extract file The following list describes the READ routines that are called for the CA 1 CA DYNAM TLMS and Zara tape management systems SLUDRCA1 Called to read the CA 1 TMC when CA 1 is defined as the tape management system This routine uses CA 1 macros to map the layout of the TMC SLUDRTLM Called to read the CA DYNAM TLMS VMF when CA DYNAM TLMS is defined as the tape management system This routine uses a CA DYNAM TLMS COPY member to map the layout of the VMF SLUDRZAR Called to invoke an API to read Zara s database when Zara is defined as the tape management system Chapter 8 SMC Tape Management Extract Utility 131 312614001 Rev B IS Note Both source and load module versions ofthe SLUDR tape management extract routines are provided as part of the SMC product installation Source modules are provided in the SMC SAMPLIB file and load modules are provided in the HSC SLULINK distribution library If your installation uses a different tape management system you can develop a program modeled on one of the supplied examples SLUDRCA1 SLUDRTLM or SLUDRZAR or you can write your own pro
111. amp amp ABC Similarly if the DSN parameter refers back to a previous DD statement the data set name is resolved to the referred to data set Thus the data set name referred to must be coded on the DATASET parameter in order for the TAPEREQ control statement to be processed Chapter 6 Commands and Control Statements 105 312614001 Rev B TAPEREQ RETPD Specifies the retention period and the relationship that must exist If you do not specify either RETPD or EXPDT the default value is RETPD GE 0 any expiration date will match this criterion EQ NE GT GE LT LE equal to not equal to greater than greater than or equal to less than less than or equal to retention period Specifies the retention period in days for the data set Specify the number of days as a 1 to 4 digit decimal number EXPDT Specifies the expiration date and the relationship that must exist EQ NE GT GE LT LE equal to not equal to greater than greater than or equal to less than less than or equal to expiration date Specifies the expiration date of the data set in YYDDD or YYYY DDD format 106 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TAPEREQ VOLType Specifies whether or not a nonspecific volume is being requested If VOLType is omitted the default value is either specific or nonspecific matches Specific Specifies that the request is for a specific volume IS Note Th
112. anation A DRIVEMAP command has been issued with the LIST keyword The SMC0163 multiline message lists the currently active DRIVEMAPs One line is produced for each CLIENT SERVER range System Action None User Response None Chapter 9 SMC Messages 187 312614001 Rev B SMC0164 SMC0166 SMC0164 SMC0165 SMC0166 CLIENT range XXXX1 XXXX2 not found for the OFF parameter of the DRIVEMAP command Message Level 0 Explanation The DRIVEMAP command has been issued with the OFF parameter and CLIENT parameter No matching DRIVEMAP range matching the CLIENT parameter was found System Action None User Response None Keyword CLIENT SERVER range XXXX1 XXXX2 overlaps with previous DRIVEMAP entry Message Level 0 Explanation A DRIVEMAP command was issued containing a CLIENT or SERVER range that overlaps a range specified on a previously issued DRIVEMAP command System Action The DRIVEMAP command is not processed User Response Issue the DRIVEMAP LIST command to view the list of currently active DRIVEMAP ranges Correct the DRIVEMAP command to specify a new range Or use the DRIVEMAP CLIENT XXXX1 XXXX2 OFF command to de activate the existing overlapping range and re specify the command with unique ranges Excessive READ depth at line nn of DSN DDDDDDDD Message Level 0 Explanation A READ command was issued from a file However too many command files are already open and the read command depth has been ex
113. arameter No UNITATTR was associated with the device System Action The UNITATTR command does not process this device User Response None Chapter 9 SMC Messages 179 312614001 Rev B SMC0135 SMC0137 SMC0135 SMC0136 ES SMC0137 Mount dismount message Client response WTOR message WIOR message issued by server from LIBRARY LLLLLLLL SERVER SSSSSSSS HSC mount or dismount message Message Level 4 Explanation The WTORDEST CLIENT or ECHOMNTERR ON option is in effect A mount or dismount was performed on an HSC library but did not complete successfully The SMC0135 message indicates the LIBRARY name and SERVER name where the mount or dismount was requested The SMC0136 merely echoes the HSC server mount or dismount message on the SMC client System Action None User Response Correct the problem indicated in the HSC mount or dismount message Note Messages SMC0135 and SMC0136 are issued for all mount errors if the message level is 12 or greater regardless of the WITORDEST or ECHOMNTERR setting and for all HSC mount and dismount messages if the message level is 16 or greater HSC mount or dismount WTOR message Message Level 4 Explanation A mount or dismount was performed on an HSC library with the LIBrary WTORDEST CLIENT set HSC issued a WTOR that is to be handled by the client The SMC0135 message indicates the LIBRARY name and SERVER name where the mount or dismount was requested System Action The SMC r
114. as been defined to the HSC using a SCRPOOL statement in the SLSSYSxx PARMLIB member or SCRPDEF file The library has scratch volumes defined in MYSUBPL scratch subpool The drives that are not in the library are excluded from consideration for this allocation during level 4 drive exclusion 40 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Exclusion Level 6 The generic location of available scratch volumes provides the next level of drive exclusion If the library contains no scratch volumes all library drives and virtual drives are excluded from selection leaving only nonlibrary drives eligible If the request is for a virtual scratch volume eligible virtual drives are selected based on the TAPEREQ VTSSs that cannot support the requested management class migration are excluded Lastly if the library contains scratch volumes and the request is not for a virtual volume then all virtual drives and all nonlibrary drives are excluded leaving only library drives eligible For example DD1 DD UNIT CART DSN MY NEW DATASET DISP NEW KEEP Assume that there are no SMC UNITAttr commands defined for nonlibrary drives and the library contains no scratch volumes All HSC library drives are excluded from consideration for this allocation When all drives are excluded during an exclusion level and the level is not at or below minimum level then the following occurs e messages SMC0045 and SMC0046 are issued e
115. ation Optionally you can enter LIBrary commands to define the local subsystems For example the following LIBrary command is used to define the local HSC library LIBRARY NAME LCLLIB LOCSUBSYS HSC where LCLLIB is the desired name of the local library and HSC is the local MSP subsystem name for the HSC Note When the SMC receives a LIBrary command automatic library detection is disabled and only libraries identified with LIBrary commands are known to the SMC 8 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scenario 2 SMC and a Single Remote HSC Library Configuration In this scenario the SMC communicates with a single HSC on a remote MSP host as illustrated in the following figure Client Server MSPA TCP IP stack Initiator Address space SMC MSPB Remote CDS HSC Address space CGI Routines SMC Address space StorageTek HTTP SERVER TCP IP stack Figure 2 NCS Remote Library Configuration Chapter 2 SMC and Sun StorageTek Library Management 9 312614001 Rev B In this scenario the SMC acts as a client and the HSC acts as a server The SMC Address Space intercepts allocation and mount requests from an Initiator Address Space on MSPA and sends the requests through the TCP IP stack to the designated Sun StorageTek HTTP server on a remote host MSPB The HTTP server on MSPB executes the SMC CGI rou
116. ation of a CAP by the LSM on which it resides A CAPid is of the form AAL where AA is the acs id and L is the LSM number cartridge The plastic housing around the tape It is approximately 4 inches 100 mm by 5 inches 125 mm by inch 25 mm The tape is threaded automatically when loaded in a transport A plastic leader block is attached to the tape for automatic threading The spine of the cartridge contains an OCR Bar Code label listing the VOLSER tape volume identifier Cartridge Access Port CAP An assembly that allows several cartridges to be inserted into or ejected from an LSM without human entry into the LSM cartridge drive CD A hardware device containing two or four cartridge transports and associated power and pneumatic supplies Glossary 223 312614001 Rev B cartridge tape I O driver Operating system software that issues commands for example read write and rewind to cartridge subsystems It is the software focal point for attaching a particular type of control unit An example is the Sun StorageTek CARTLIB product cartridge transport See transport cell A receptacle in the LSM in which a single cartridge is stored CGI Common Gateway Interface channel A device that connects the host and main storage with the input and output devices control units A full duplex channel has two paths that is 2 wires or one wire with signals at two frequencies A hal
117. braries defined Therefore user exit return codes such as USE LIBRARY DRIVES USE VIRTUAL DRIVES etc are not used to determine a request owner nor does the user exit return code or USE NONLIBRARY DRIVES result in the selection of a different library The preferred way to select a library owner from among multiple libraries is through esoteric substitution on TAPEREQ Alternatively user exits can be used to specify a library name or esoteric Message Handling Differences The SMC message handling component does not call user exit 01 for all console messages The USERMsg operator command allows specification of additional messages to be intercepted and passed to the library subsystem s user exit 01 For swap processing only the enhanced swap was implemented in SMC Customers previously doing custom swap processing by defaulting to HSC nonenhanced swap and intercepting IBM swap messages may need to examine their processing and possibly intercept SMC messages 218 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Appendix D SMC Interaction with Other Software Automated Operations Customers who use an automated operations product should review the SMC0110 WTOR issued during SMC swap processing for possible auto ops rule changes Open Type J The SMC allocation enhancements may not operate if you use the MSP Open Type J macro Since that macro allows you to change volume serial number
118. brary subsystem or server OFF do not log responses received from a library subsystem or server to the LOG file This is the default value ON log responses received from a library subsystem or server to the LOG file LOCal specifies whether the SMC logs local data in addition to remote TCP IP requests and responses OFF do not log data sent and received from a local library subsystem using cross memory services This is the default setting IEY Note Data sent and received over TCP IP to remote servers is logged ON log data sent and received from a local library subsystem using cross memory services in addition to data sent and received over TCP IP to remote servers 82 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B MOUNTDef LRECL specifies the line length written to the LOG file OFF use the DCB LRECL to control the maximum line length The LOG record is appended to the log date and time stamp This is the default setting nannn a value from 60 to 32767 used to limit the logical line length If the data sent or received exceeds the specified LRECL then multiple lines are written If LRECL is specified then the log date and time stamp are written as separate LOG records If this value exceeds the DCB LRECL then the DCB LRECL is used EOFREstart specifies the SMC response when the LOG file reaches End of File EOF OFF stop logging at EOF ON close and re open the LOG file at EOF
119. but was de activated by the UEXIT DISABLE keyword ABENDED indicates the user exit abended A new version must be loaded for this exit to be re activated SEQUENCE indicates how many loads have been performed for this user exit LOADED indicates when this version of the module was loaded e CHANGED indicates when this version of the module was activated or disabled System Action None User Response None Drive range mismatch between CLIENT XXXX1 XXXX2 and SERVER XXXX3 XXXX4 Message Level 0 Explanation A DRIVemap command was issued One of the specified CLient range did not match the format of the corresponding SErver range System Action None User Response Reissue the command ensuring that the CLIENT parameter and the SERVER parameter have corresponding formats and number of drives 174 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0124 SMC0125 SMC0126 SMC0127 SMC0124 ABENDED or INACTIVE UEXIT nn must be reloaded to ENABLE at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A UEXIT nn ENABLE command was issued for a user exit that had previously abended or inactivated itself via a return code System Action None User Response Use the UEXit command with the LOAD keyword to reload the exit UEXIT nn already ENABLED DISABLED at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A UEXIT nn ENABLE or DISABLE command was issued
120. cates a 3590 image T9940A transport T9940B Indicates a 3490E image T9940B transport T9940B35 Indicates a 3590 image T9940B transport T1A34 Indicates a 3490E image T10000A transport T1A35 Indicates a 3590 image T10000A transport T1AE34 Indicates an encryption enabled 3490E image T10000A transport T1AE35 Indicates an encryption enabled 3590 image T10000A transport T1B34 Indicates a 3490E image T10000B transport T1B35 Indicates a 3590 image T10000B transport TIBE34 Indicates an encryption enabled 3490E image T10000B transport TIBE35 Indicates an encryption enabled 3590 image T10000B transport Virtual Indicates a VTV Virtual Tape Volume mounted on a VTD Virtual Tape Drive 216 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Appendix C Differences Between SMC and HSC 6 0 and Below The SMC product represents a complete re architecture of the MSP interfaces for Sun Sun StorageTek tape library management systems Customers converting to SMC from HSC 6 0 or below should be aware that minor differences to allocation and message processing may be found with SMC Ina few cases Sun Microsystems recommends changes to existing HSC policies and parameters to preserve behavior consistent with older releases Significant differences are noted in this appendix Allocation Differences 1 SMC allocation is based on exclusion levels see Chapter 4 SMC Allocation in a JES Environment for a detailed descr
121. cation component detected that the job is not allocatable at the specified minimum exclusion level MINLVL System Action The job is failed by MSP or express canceled by JES User Response Correct the JCL or change the MINLVL for the specified job SMC subsystem termination in progress no allocation influence for job JJJJJJJJ step SSSSSSSS Message Level 8 Explanation During execution of job JJJJJJJJ step SSSSSSSS the SMC allocation component detected that the SMC subsystem was being terminated System Action No allocation influencing is performed for the job User Response None 152 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0045 SMC0046 SMC0047 SMC0045 SMC0047 Conflicting exclusion criteria for job JJJJJJJJ step SSSSSSSS DD DDDDDDDD Message Level 8 Explanation Messages SMC0045 and SMC0046 are always produced together See the explanation for message SMC0046 for more information System Action None User Response None CCCCCCCCCCCCCCCC would have excluded all devices not honored Message Level 8 Explanation When the SMC allocation component attempted to apply the exclusion criteria CCCCCCCCCCCCCCCC for job JJJJJJJJ step SSSSSSSS DD DDDDDDDD no devices remained in the current exclusion level EDL The SMC0045 and SMC0046 messages are always produced together For information about exclusion criteria refer to the keyword column of the JES Drive Exclusion
122. ceeded Read command depth is defined as the number of files that can be open simultaneously due to imbedded Read commands System Action The READ command is not processed User Response Restructure your command files to reduce the READ command depth 188 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0167 SMC0168 SMC0169 SMC0167 SMC0169 LIBRARY RESYNCH summary LIBRARY LLLLLLLL is disabled inactivelactive on LOCAL SUBSYS SSSS REMOTE SERVER SSSSSSSS All LIBRARY s active i of i LIBRARY s active WARNING A11 LIBRARY s inactive WARNING No LIBRARY s defined WARNING No LIBRARY s enabled Message Level 0 Explanation A RESYNCH or LIBRARY STATUS command was issued Each LIBRARY will be represented by a line in the multiline WTO displaying its status System Action None User Response None WARNING No TREQDEF command processed Message Level 4 Explanation No TREQDEF command was found in the SMCPARMS or SMCCMDS file at startup System Action TAPEREQ processing is not performed for allocation or mount requests User Response If your installation previously specified TREQDEF in HSC issue the TREQDEF command to SMC and add the TREQDEF command to the SMCCMDS or SMCPARMS file WARNING SMCCMDS SMCPARMS processing TIMEOUT startup continuing Message Level 4 Explanation During SMC subsystem startup startup command processing could not complete the indicate
123. command or statement See Syntax Flow Diagrams on page xix for syntax flow diagramming conventions ALLOCDef Command The SMC ALLOCDef command is used to specify system default parameters used within the SMC subsystem to control allocation Syntax 2 MAX ire leap nieve SELVA seplevel OFF OFF FALLO info oh MIAcompat oli SPECIFIC OFF ON CAlrts E wrer A h OFF OFF USEREXIT EXTVOLESOT A IE AA OFF VTVMAXvol Lol 60 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCDef Command Name ALLOCDef initiates the ALLOCDef command Parameter Descriptions LIst optionally lists current default allocation settings This is the default if no parameters are specified It cannot be specified with any other parameter OFF optionally resets all default allocation values to original SMC default settings It cannot be specified with any other parameter MINLvl optionally specifies the desired minimum level of drive exclusion Ifa job is not allocatable at the minimum exclusion level the SMC still excludes drives to the minimum level and allows the job to fail minlevel indicates the desired minimum allocation exclusion level Valid values are 0 8 0 indicates that the SMC will not exclude any drives even if all drives would be excluded during level 1 exclusion processing 2 is the default setting See Chapter 4 SMC Allocation in a JES Environment for more information
124. d command file System Action The SMC continues startup processing but not all startup commands may have been processed User Response None Chapter 9 SMC Messages 189 312614001 Rev B SMC0170 SMC0171 SMC0174 Request timeout SMC subsystem terminating request to subsystem SSSS aborted Message Level 4 Explanation The SMC issued a request to subsystem SSSS but no response was received within the time limit or the SMC subsystem was terminated System Action The SMC continues processing without waiting for the HSC response In addition if a request timeout is indicated the SMC SERVER path to the specified subsystem is disabled User Response Check the status of the subsystem that is not responding to SMC and correct the problem After correcting the problem enable the appropriate SERVER path Allocatability test matrix retries exceeded Message Level 0 Explanation The SMC could not determine allocatability of the job step using its test matrix in the calculated number of retries System Action Normally processing continues with SMC backing out exclusion conditions until the job step is allocatable User Response If possible rerun the job with allocation trace turned on Save trace and log output and contact Sun Microsystems Software Support ASCOMM ACK timeout for job JJJJJJJJ DS nnnn nnnn Message Level 0 Explanation The SMC replied to a request from job JJJJJJJJ but no acknowledgment
125. d ser JBB509A F dddd ser JBB512I T O ERR LBL ERR SEC VOL JBB701D M dddd VOLUME TO BE LABELED ser JBB7021 dddd VOLUME LABELS CANNOT BE VERIFIED JBB7031 dddd VOLUME IS FILE PROTECTED JDJ233A M dddd ser labtyp JDJ233D M dddd ser labtyp JDJ234E K D R dddd ser KHE2001 SWAP dddd to eeee OPERATOR I O ERROR KHE2021 PROCEED WITH SWAP OF dddd TO eeee KHE2031 ERROR ON dddd SELECT NEW DEVICE KHE2051 SWAP ddd OPERATOR I O ERROR KHE207A WRONG VOLUME MOUNTED ON dddd MOUNT ser _TA0233D Message for ASM2 206 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Tape Management System Messages CA 1 Messages The following CA 1 TMS messages are intercepted by the SMC Refer to the appropriate Computer Associates publication for the exact format and meaning of each message Table 7 Tape Management System Messages CA 1 Message ID Description CTS001 See CA 1 User Manual Volume 1 CTS002 See CA 1 User Manual Volume 1 CTS004 See CA 1 User Manual Volume 1 CTS005 See CA 1 User Manual Volume 1 CTS007 See CA 1 User Manual Volume 1 CTS008 See CA 1 User Manual Volume 1 CTS009 See CA 1 User Manual Volume 1 CTSO10 See CA 1 User Manual Volume 1 CTSO11 See CA 1 User Manual Volume 1 CTS014 See CA 1 User Manual Volume 1 CTS015 See CA 1 User Manual Volume 1 CTT100A See CA 1 User Manual Volume 1 CTT101A See CA 1 User
126. ddress The SMC does not validate a new device address To cancel the swap reply N Ifan I O error on device XXXX1 caused the swap a reply of N causes the job to fail USER defined message 1D MMMMMMMM Message Level 0 Explanation The SMC has listed the messages that were added using the USERMsg command System Action Both SMC default and USER Msg added messages are sent to user exit 01 for each library subsystem SMC processes USERMsg added messages according to the response from user exit 01 User Response None Chapter 9 SMC Messages 169 312614001 Rev B SMC0112 SMC0112 SMC0112 Cannot add duplicate message ID MMMMMMMM at line nnnn of SMCPARMS Message Level 0 Explanation The USERMsg command was issued to add a new message ID that SMC will intercept The supplied message ID MMMMMMMM is a duplicate of a message already defined to SMC System Action The message is not added User Response None 170 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0113 SMC0113 SMC0113 SERVER SSSSSSSS CCCCCCCC Status active never activelinactiveldisabled Messages nnnn Retries nnnn Init errors nnnn Errors nnnn Message Level 0 Explanation A SERVER command has been issued with the LIST keyword The SMC0113 multiline message lists the server settings and status for each SERVER defined to the SMC subsystem Refer to the SERVER command for parameter descriptions e STATUS indicates the
127. e IEY Note Refer to the NCS 6 1 Installation Guide for SMC installation procedures Chapter 3 Starting the SMC 21 312614001 Rev B Creating the SMC START Procedure An SMC START procedure must be created in the procedure library of the host system The MSP START command invokes this catalogued procedure thus activating the SMC with the specified startup parameter settings Figure 7 provides a sample SMC START procedure yourprocname PROC PRM WARM stepname EXEC PGM SMCBINT REGION 4M TIME 144 STEPLIB DD DISP SHR DSN your ncs smc6100 smclink DD DISP SHR DSN your ncs exitlib DD DISP SHR DSN your ncs sos6100 sislink SMCPARMS DD DSN parmlib_name parm_member_name DISP SHR SMCCMDS DD DSN cmd1ib_name cmd_member_name DISP SHR TISPAPPL DD DSN your tisp applnames DISP SHR PARM amp PRM Figure 7 Sample SMC START Procedure IS Note s The first four characters of yourprocname specify the SMC subsystem name unless the SSYS startup parameter is specified Sun Microsystems recommends a value of SMCx where x is any valid jobname character Due to product dependencies the HSC load library SLSLINK is required in the STEPLIB concatenation The SMCPARMS and SMCCMDS DD statements are optional Both statements are processed during initialization The SMCCMDS data set may be re processed during execution See Chapter 6 Commands and Control State
128. e 11 Table 12 SMC Client Server Drive Address Mapping Scenarios 0 00 00 cece eee eens 18 JES Drive Exclusion Levels Specific Request 0 0 cece cc eee eens 32 JES Drive Exclusion Levels Scratch Request o oooooooooororrnrca 37 Alternate Device Default Value 20 0 n ence 109 Variable Data Definitions A Bas E See ent tidal get Seda Seg E 140 Intercepted Operating System Messages 2 0 c cece cece eee eee eens 206 Tape Management System Messages CA 1 1 0 ee eee eee nee 207 Media PES A Nore Gans baa ee tak A ed siete bes iio 209 Media Type Detalla fs oaks table teak al hoe A SS 211 Recording Techniques 0 00 a a E E a n ene e nent neee 212 Recording Technique Defaults 0 00 cece teen n eens 214 Model Types ici a TT E ie wean E E EE A E E arene dais 215 Tables xi 312614001 Rev B What s New SMC Release 6 1 includes the following enhancements and modifications Enhancement Modification Publication s Primary Locations Revision B SMC exclusion level 1 for specific requests is updated to exclude all virtual Chapter 4 drives for non labeled NL specific volume requests The SMC ALLOCDef command includes the new VTVMA Xvol parameter Chapter 6 used to set the volume count for a new allocation to 255 during MVS converter interpreter IDAX processing when the JCL or SMC DFSMS ACS routine esoteric contains at least one virtual device
129. e MEDia RECtech or MODel parameters e no definition data is loaded then the MEDia and RECtech or MODel parameters are set to undefined which matches all requests Any available device is eligible for allocation Chapter 6 Commands and Control Statements 103 312614001 Rev B TAPEREQ Parameters The TAPEREQ control statement is in essence an IF THEN statement IF the Input selection criteria parameters match the current tape request variables THEN the Output media and format parameters may apply TAPEREQ input and output parameters are described in the following sections Input Parameters Note The JOBname STEPname PROGram and DATASET parameter values can include the following wild card characters or any single nonblank character any character string length zero to 8 not to exceed one qualification level For example A B matches A B and A B C but does not match A B C D a7 used only in DATASET Indicates any number of qualifiers zero or more Cannot be used with any other characters within a qualifier For example A B matches A B A B C A B C D A B C D E and so forth The TAPEREQ input selection criteria parameters include JOBname Optionally identifies the job name If JOBname is not specified the default value is jobname Specifies the name of the job for which the TAPEREQ control statement is processed The TAPEREQ control statement is used only when the specified jobname matches
130. e Request Control Statement The SMC TAPEREQ statement specifies tape request attributes These attributes define the media type and recording technique or model number used for a particular data set or group of data sets TAPEREQ statements are placed in the definition data set DDname specified by the SMC TREQDEF command SMC allocation calls on these TAPEREQ statements to help ensure that the correct media type is used to satisfy a request and that the cartridge is mounted on the appropriate device TAPEREQ statements must be placed in the definition data set they cannot be issued as an operator command IS Notes The SMC TAPEREQ control statement replaces the HSC TAPEREQ control statement See page 119 for information about the TREQDEF Command e See Chapter 4 SMC Allocation in a JES Environment for information about SMC allocation If your environment contains multiple types of 36 track drives recording technique 36Atrack 36Btrack or 36Ctrack it is recommended that you use device preferencing to manage device allocation Entering specific 36 track device types in TAPEREQ statements i e 36A 36B 36C causes the SMC to break unit affinity chains based on incompatible device types using device preferencing allows the affinity chains to be maintained Parameters from TAPEREQ lookup including SUBPool and ESOTeric always take precedence over values derived from a user exit Disabling a TAPEREQ Definition U
131. e TAPEREQ parameter never overrides the actual media type of the specific volume returned by the LCS Nonspec Specifies that the request is for a nonspecific scratch volume Output Parameters The TAPEREQ output media and format parameters include MEDia Specifies the desired type of media for a data set being created You can enter a list of media types but they must be separated by commas media type indicates the media type See Table 8 on page 209 for a list of valid media type values IS Notes e A list specifies a generic pool from which a selection is made There is no implied priority This parameter is ignored for an existing data set if the media characteristics are determined by the volume information contained in the LCS s control data set CDS e Ifthis parameter is not specified a default is chosen based on the value of the RECtech parameter See Table 9 on page 211 for default values used if the MEDia parameter is omitted To avoid problems it is recommended that all TAPEREQ statements specify MEDia and RECtech consistently Be sure to include one or both parameters on each statement If both media type and recording technique are omitted all available devices are eligible for allocation Chapter 6 Commands and Control Statements 107 312614001 Rev B TAPEREQ RECtech Optionally specifies the method used to record data tracks on the tape surface for the desired data set You can enter a list o
132. e parameter string parm exceeds the allowed length Unable to open dsname Explanation The HTTP server was unable to open the data set dsname in response to a client request abend_message_line Explanation Message number for abend reporting messages Not APF authorized cannot continue Explanation The server is not APF authorized but APF authorization is required The server shuts down Task shutdown time expired terminating tasks Explanation During HTTP server shutdown some tasks did not stop before the shutdown timeout was exceeded These tasks are forcibly terminated Cannot find server module name Explanation When the HTTP server performed its startup checks it could not find its module name 198 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SKY052E SKY0531 SKY053E SKY054E SKY0551 SKY056l SKY059E SKYO60E SKY0611 SKY052E SKY0611 Cannot find all server modules shutting down Explanation The HTTP server could not find all of its modules when it performed its startup checks The server shuts down Current active worker tasks t Explanation The current number of worker tasks for servicing requests Fatal error in main task commencing forced shutdown Explanation The server suffered a fatal error in its main task and was unable to perform an orderly shutdown Fatal error in main task attempting orderly shutdown Explanation The server suffered a
133. e to eight characters in length This parameter is only valid if JOBname and STEPname are also specified LVL optionally specifies the default level used to control which SMC messages are displayed This parameter is required when JOBname is specified level indicates the default level Valid values include the following 0 Display error messages only 4 Display error and warning messages from the SMC subsystem 8 Display all SMC subsystem messages and allocation job log warning messages If no value is specified the default value of 8 is used Note Levels higher than 8 are used for diagnostic purposes and should only be specified as directed by Sun Microsystems Software Support Chapter 6 Commands and Control Statements 91 312614001 Rev B READ Example In the following example the MSGJob command specifies that only error and warning messages are displayed for job PRODJOBI step STEP3 PROC step REPORT MSGJOB JOB PRODJOB1 STEP STEP3 PROCCREPORT LVL 4 92 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B RESYNChronize READ Command The SMC READ command is used to enter a series of commands using an input data set instead of console commands Syntax AS AA DSN dataset HOST hostname Command Name READ initiates the READ command Parameter Descriptions SMCCMDs re processes commands contained in the data set specified in the SMCCMDS DD statement of the SMC STA
134. e volume to become available or reply C to cancel the request or R to retry immediately All devices marked ineligible for job JJJJJJJJ step SSSSSSSS due to volume lookup failure Message Level 4 Explanation When SMC allocation attempted to acquire volume information a communication failure with the library server occurred The ALLOCDEF option FAILNOINFO was specified System Action The SMC marks all devices as ineligible for allocation The job is failed by MSP or express canceled by JES User Response Investigate the cause of the communication failure and resubmit the job Chapter 9 SMC Messages 183 312614001 Rev B SMC0147 SMC0151 SMC0147 PPPPPPPP1 is incompatible with PPPPPPPP2 on the TAPEREQ command line nonn of TREQDEF DSN Message Level 0 Explanation An incompatibility exists between PPPPPPPP1 and PPPPPPPP 2 at line nnnn in the data set specified on the TREQDEF command System Action The SMC continues to process the TAPEREQ statements flagging additional errors User Response Correct the errors and re issue the TREQDEF command SMC0149 TREQDEF specifications not installed reason code nn Message Level 0 Explanation The TAPEREQ statements in the data set specified on the TREQDEF command were not installed 08 Syntax error on a TAPEREQ statement 12 The TAPEREQ structure has not been initialized System Action None User Response Correct the errors and re issue the TREQDEF comma
135. ecause each level produces a drive list containing common drives for both DD1 and DD2 Another example DD1 DD UNIT 3498M VOL SER INACSM DSN VIRTUAL DATASET1 DISP 0LD DD2 DD UNIT AFF DD1 VOL SER INACS1 DSN VIRTUAL DATASET2 DISP 0LD DD3 DD UNIT AFF DD1 VOL SER NL8 1 DSN REAL DATASET DISP OLD 46 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Assume the following ALLOCDEF SEPLVL 5 has been specified Volume INACSO is in ACSO and VOLATTR MEDIA ECART RECTECH 36B has been defined Volume INACS1 is in ACS1 and VOLATTR MEDIA ECART RECTECH 36B has been defined Volume NL0001 is a nonlibrary volume and VOLATTR MEDIA DD3A has been defined At drive exclusion level 1 two chains result because of incompatible media ECART and DD3A Statements DD1 and DD2 are still chained together and continue through exclusion levels 2 through 5 because the exclusion criteria do not create disparate sets of eligible drives for the two DD statements No further separation of the DD1 DD2 chain can occur because the SEPLVL parameter has been set to level 5 After the last drive exclusion level is completed for the job the SMC examines the final drive lists If the job cannot be allocated because not enough drives remain eligible drive exclusion regresses to the previous exclusion level of the failing DD statement and a separated chain may be rejoined This process repeats until the job can allocate Note The SE
136. eceived an MSP STOP command System Action None User Response Check the network and server subsystem for problems If the mount was not performed issue a manual mount command to the HSC 182 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0144 SMC0145 SMC0146 SMC0144 SMC0146 Mount of volser VVVVVV on device XXXX drive is in use reply C to cancel mount or R to retry Message Level 0 Explanation SMC has communicated a mount or dismount request to HSC HSC has responded with a message indicating that the drive is in use System Action If the mount is still outstanding the SMC automatically redrives the mount every 30 seconds The message is DOMed if the mount is no longer pending or the drive becomes available User Response Wait for the drive to become available or reply C to cancel the request or R to retry immediately Mount of volser VVVVVV on device XXXX volume is in use reply C to cancel mount or R to retry Message Level 0 Explanation SMC has communicated a mount or dismount request to HSC HSC has responded with a message indicating that the drive is in use System Action The SMC verifies that the mount is still outstanding If the mount is still outstanding the SMC automatically redrives the mount every 30 seconds The message is DOMed if the mount is no longer pending or the volume becomes available User Response Wait for th
137. ed as a unit 224 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B data sharing The ability of concurrent subsystems or application programs to directly access and change the same data while maintaining data integrity I device number A four digit hexadecimal number that uniquely identifies a device attached to a processor device preferencing The process of preferring one 36 track transport type over another 36 track transport type device separation See drive exclusion direct access storage device DASD IBM s term for a disk drive storage device directed allocation See drive prioritization disconnected mode A relationship between a host and an ACS In this mode the host and the ACS are not capable of communicating there are no online stations to this ACS DMS OS DASD Management System Operating System dotted decimal notation The syntactic representation of a 32 bit integer that consists of four 8 bit numbers written in base ten with periods dots separating them In TCP IP descriptions dotted decimal notation is used for Internet addresses drive exclusion previously referred to as device separation refers to the Storage Management Component SMC function of excluding drives for an allocation request based on SMC exclusion criteria See the SMC Configuration and Administration Guide for more information drive panel An LSM wall containing tape t
138. edrives the mount or dismount to the server transmitting the specified message response User Response See the HSC Messages and Codes Guide for the corresponding HSC message and respond as directed Note The MSGDef command SMCWtorpfx parameter can be used to suppress the SMC0137 portion of the message 180 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0138 SMC0139 nmnnannannan SMC0138 nnnnnnnn XML input output parse error RC nnn transaction TTTTTTTT LIBRARY LLLLLLLL Message Level 0 Explanation The SMC encountered an XML parse error Input XML errors are produced when the input XML transaction cannot be parsed Output XML errors occur when transaction response data cannot be converted to XML The transaction type and library name are also displayed System Action Depending upon the type of error and server characteristics the allocation or mount event may not be processed by the SMC User Response Contact Sun Microsystems support UNITATTR for device DDDD is model MMMMMMMM Message Level 0 Explanation A UNITATTR command was issued specifying device DDDD and the LIST parameter The model associated with device DDDD is model MMMMMMMM System Action None User Response None SMC 14 DFSMS message Message Level 0 Explanation The DFSMS ACS routine has issued the DFSMS message nnnnnnnn will be the JCL statement number or the DDNAME if it is a dynamic allocation Sy
139. een the following e User Exit 10 return code separation decision ALLOCDef or ALLOCJob command SEPLvl parameter value User Exit 10 User Exit 10 sends an entire affinity chain to the user for examination The user can decide whether the affinity chain remains together or separates during exclusion processing after the minimum level If User Exit 10 returns UX10SEP indicating the chain members can be separated the SMC proceeds as if ALLOCDEF SEPLVL MAX were specified 44 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B If User Exit 10 returns UX10LDRV UX1ONDRV UXI0ESUB or UX10ASUB the affinity chain remains together for the remainder of drive exclusion processing The location requested e g library drives if UX10LDRV is returned replaces any location value provided by User Exits 02 or 08 This location information is used by drive exclusion level 4 Refer to Table 2 on page 32 and Table 3 on page 37 for drive exclusion level information For example DD1 DD UNIT CART DSN SYS4 DATASET1 VOL SER NOL1B1 DISP 0LD DD2 DD UNIT AFF DD1 DSN SYS4 DATASET2 VOL SER INLIB2 DISP 0LD Assume the following DDI requests a nonlibrary volume and DD2 requests a library volume e User Exit 08 returns a nonlibrary esoteric for DD1 UXO8ESUB User Exit 10 returns a no separate decision and a library location UXIOLDRV The affinity chain stays together Drive exclusion ignores the esoteric returned by User Exi
140. em or the HSC subsystem and re ENABLE the SERVer or LOCSUBsys NAME must be specified to add or modify a SERVER at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The user entered a SERVER command to add a new SERVER or modify an existing SERVER path but the SERVER path NAME was not specified System Action None User Response Enter the SERVER command specifying the SERVER path NAME UEXIT nn is now ENABLED DISABLED Message Level 0 Explanation The user entered a UEXIT nn ENABLE or DISABLE command or the SMC detected an abend in the specified user exit The specified user exit is now ENABLED or DISABLED System Action None User Response If the SMC automatically disabled the user exit due to an abend the exit cannot be re enabled unless it is also reloaded Chapter 9 SMC Messages 173 312614001 Rev B SMC0122 SMC0123 SMC0122 SMC0123 UEXIT nn STATUS YACTIVE DISABLED ABENDED CCCC CCCC SEQUENCE nn LOADED YYYY MM DD HH MM SS CHANGED YYYY MM DD HH MM SS Message Level 0 Explanation A UEXIT command was issued with the LIST keyword The SMC0122 multiline message lists the user exit status for each user exit defined to the SMC subsystem REfer to the UEXIT command for parameter descriptions e nn indicates the SMC user exit number type STATUS indicates the user exit status ACTIVE indicates that the exit is loaded and active DISABLED indicates that the exit is loaded
141. enabled 3490E or 3590 image T10000B transport T1B34 Indicates a non encryption enabled 3490E image T10000B transport T1B35 Indicates a non encryption enabled 3590 image T10000B transport TIBE Indicates an encryption enabled 3490E or 3590 image T10000B transport TIBE34 Indicates an encryption enabled 3490E image T10000B transport TIBE35 Indicates an encryption enabled 3590 image T10000B transport Virtual o a VTV Virtual Tape Volume mounted on a VTD Virtual Tape rive When this parameter is not specified a default is chosen based on the value of the MEDia parameter The following table shows default values used if RECtech is omitted Table 11 Recording Technique Defaults MEDia Entered pa LONGItud LONGItud Standard LONGItud ECART 36track ZCART 36Ctrack DD3A DD3B DD3C DD3D DD3 STKIR STK1U STK1Y STKIR STK2P STK2W STK2P T10000T1 T10000TS T10000CT T10K Virtual Virtual 214 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B MODel Type MODel The model type is used to specify the model number of a transport drive or drive MODel provides the same type of information as RECtech but a user may find it more convenient to specify a transport model rather than a recording technique MODel and RECtech are mutually exclusive MODel is used in the following NCS commands and control statements e SMC TAPEREQ control statement e SMC UNITAttr opera
142. ent 45 312614001 Rev B During specific volume exclusion level 7 the list of eligible drives in DD are all located in ACSO and the list of eligible drives in DD2 are all located in ACS1 No drives are common to both lists This affinity chain separates Note MAX is the default value for SEPLvl The SEPLvl parameter can be specified as MIN The value MIN requests that any affinity chains that remain together after the minimum level of drive exclusion should not be separated during the remaining levels of drive exclusion processing Using the same example DD1 DD UNIT 349 VOL SER INACS DSN MY DSN1 DISP OLD DD2 DD UNIT AFF DD1 VOL SER INACS1 DSN MY DSN2 DISP 0LD Once again assume e Both volume INACSO and INACS1 share common media characteristics e Volume INACSO resides in ACSO and volume INACS1 resides in ACS1 ALLOCDEF SEPLVL MIN has been specified During specific volume exclusion level 7 the list of eligible drives for DD1 is all located in ACSO DD1 is considered the head of the chain and exclusion is performed to ACSO Only drives in ACSO remain eligible for the allocation and the affinity chain remains together The SEPLvl parameter can also be set to a specific drive exclusion level The level number indicates the highest drive exclusion level at which separation can occur Using the previous example if the user specifies ALLOCDEF SEPLVL 6 The chain remains together through drive exclusion level 6 b
143. ents if different drive addresses are defined between client and server hosts 12 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scenario 4 SMC and a Single HSC Library Configuration with Multiple Remote Server Paths In this scenario the SMC runs on a host with no local HSC but with multiple paths to a remote HSC as illustrated in the following figure Client Servers MSPA MSPB TCP IP stack HSC B Address space SMC Address space Initiator Address space CGI Routines SMC Address space StorageTek HTTP SERVER TCP IP stack Remote Library HSC C Address space CGI Routines SMC Address space TCP IP stack StorageTek HTTP SERVER Figure 4 NCS Remote Library Configuration with Two Server Instances Chapter 2 SMC and Sun StorageTek Library Management 13 312614001 Rev B The following example illustrates the LIBrary and SERVer commands for the SMC on MSPA LIBRARY NAME SHRLIB SERVER NAME REMPATH1 LIBRARY SHRLIB HOST MSPB SERVER NAME REMPATH2 LIBRARY SHRLIB HOST MSPC Requests originating in an Initiator Address Space on MSPA are intercepted by the SMC Address Space on MSPA The SMC on MSPA sends requests for volume and drive data and mount requests to the SERVER on MSPB or MSPC The SMC attempts to communicate with the first defined server MSPB If this attempt fails the SM
144. eparated by one or more blanks or a comma A value is associated with a parameter by an equal sign or by enclosing the value in parentheses and concatenating it immediately after the parameter Case upper or lower is ignored in actual control statements Continuations are supported by including a plus sign at the end of the line to be continued and can be used to enclose comments in the job stream Comments can be continued over multiple lines but cannot be nested The maximum length for a control statement is 1024 characters xxiv SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Related Publications The following publications contain information about specific topics relating to the use of the Storage Management Component SMC Sun StorageTek Nearline Control Solution NCS MSP Implementation NCS Installation Guide e NCS User Exit Guide Sun StorageTek Host Software Component HSC MSP Implementation HSC Configuration Guide HSC Operator s Guide HSC System Programmer s Guide e HSC Messages and Codes Guide Sun StorageTek Virtual Storage Manager VSM MSP Implementation e VTCS Installation and Configuration Guide e VTCS Administration Guide e VTCS Messages and Codes Guide e VTCS Command and Utility Reference About this Guide xxv 312614001 Rev B Additional Information Sun Microsystems Inc Sun offers several methods for you to obtain addit
145. essages 0 ooooooococororr rr 221 Changed Messages divas A A AS Sle eases Rd ah al ied Signe Dates Reapers 221 Deleted Messages secon cdi Sache ae cise ac bead Heed A AES Sas ees en ee 4 222 GIGSS AY A Bee eral A eS eh hoe A aatre 223 o ik ceases O NN atiaee 233 viii SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Figures Figure 1 NCS Local Library Configuration 0 0 0 0 ccc cect cette 7 Figure 2 NCS Remote Library Configuration 0 0 ttt teens 9 Figure 3 NCS Local Library with Alternate Path Configuration 2 0 00 0 e eee eee 11 Figure 4 NCS Remote Library Configuration with Two Server Instances oooooocoocoooo 13 Figure 5 NCS with Two Libraries One Local and One Remote with Multiple Paths 15 Figure 6 NCS with a Local Library and a Remote Library with Two Server Instances 17 Figure 7 Sample SMC START Procedure 1 2 00 0 c ccc eee teen ne eee 22 Figure 8 TAPEREQ Control Statement 0 0 cee teen eae 102 Figure 9 Scratch Synchronization Between SMC Client host and HSC CDS 130 Figure 10 Sample JCL for Scratch Extraction Utility 20 0 eee eee 136 Figure 11 Scratch Extraction Utility Sample Output Messages 00 0 cece eee een eens 137 Figures ix 312614001 Rev B Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Tabl
146. execution parameter but it was specified as a keyword value pair where no value is allowed System Action The SMC subsystem terminates User Response Correct the subsystem initialization startup procedure to specify the correct execution parameter string SMC startup parameter PPPPPPPP must have a value Message Level 0 Explanation During initialization the SMC subsystem initialization program encountered a valid execution parameter but it was not specified as a keyword value pair and a value is required System Action The SMC subsystem terminates User Response Correct the subsystem initialization startup procedure to specify the correct execution parameter string Chapter 9 SMC Messages 149 312614001 Rev B SMC0035 SMC0037 SMC0035 Error processing SMC startup parameter PPPPPPPP CCCCCCCCCCCC Message Level 0 Explanation During initialization the SMC subsystem initialization program encountered an error in the execution parameter string The string CCCCCCCCCCCC indicates the type of error encountered System Action The SMC subsystem terminates User Response Correct the subsystem initialization startup procedure to specify the correct execution parameter string SMC0036 SMC startup parameter PPPPPPPP successfully processed Message Level 4 Explanation During SMC initialization the execution parameter PPPPPPPP was successfully verified and processed System Action None User Response None SM
147. eyword However no entries were found in the SMC queue for the specified command A LIST command was specified with a control block keyword However no control blocks of the specified type were found System Action None User Response None Chapter 9 SMC Messages 147 312614001 Rev B SMC0027 SMC0030 SMC0027 SMC0028 SMC0029 SMC0030 Keyword KKKKKKK1 of the CCCCCCCC command requires keyword KKKKKKK2 at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified keyword KKKKKKK1 but not the required co requisite keyword KKKKKKK2 System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command STOP command received Message Level 0 Explanation The MSP stop P command was received by the SMC and the SMC subsystem termination process is set to begin System Action The SMC subsystem begins termination processing User Response None CCCCCCCC command processing error matching entry not found command line truncated will be ignored parameter truncated command ignored at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation An error was found processing the CCCCCCCC command System Action Processing continues The command is ignored User Response Use the LIST keyword to list the current SMC queue of entries then ensure that the
148. f duplex channel requires that one port receives while the other transmits channel to channel CTC Refers to the communication transfer of data between programs on opposite sides of a channel to channel adapter I client The ultimate user of the ACS services as provided by the Library Control System client computing system CCS A computer and an operating system client link The communications link between the LCS and a client client server A model of interaction in a distributed system in which a program at one site serves a request to a program at another site and awalts a response The requesting program is called a client the program satisfying the request is called a server client system The system to which the LCS provides an interface to a Sun StorageTek Automated Cartridge System coaxial cable A transmission medium used in data transmissions for networks using synchronous communications as opposed to twisted pair the primary medium for asynchronous RS 232 communications complex A system composed of other systems specifically the ACS server system and the client system connected mode A relationship between a host and an ACS In this mode the host and an ACS are capable of communicating in the sense that at least one station to this ACS is online connection number The unique identifier on the server for a communications path The number is assigned by TCP IP to identi
149. f recording techniques but they must be separated by commas IS Note A list specifies a generic pool from which a selection is made There is no implied priority recording technique indicates the recording technique See Table 10 on page 212 for a list of valid recording technique values IS Notes e RECtech and MODel are mutually exclusive e If this parameter is not specified on any matching TAPEREQ a default is chosen based on the value of the MEDia parameter See Table 11 on page 214 for default values used if the MEDia parameter is omitted To avoid problems it is recommended that all TAPEREQ statements specify MEDia and RECtech consistently Be sure to include one or both parameters on each statement If both media type and recording technique are omitted all available devices are eligible for allocation MODel Optionally specifies the model number of a transport You can enter a list of models but they must be separated by commas MODel provides the same type of information as RECtech but a user may find it more convenient to specify a transport model rather than a recording technique IS Note A list specifies a generic pool from which a selection is made There is no implied priority model type indicates the model type See Table 12 on page 215 for a list of valid model type values IS Note MODel and RECtech are mutually exclusive 108 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B
150. f the volume resides in a library all drives outside the library are excluded and if the volume resides outside the library all library drives are excluded For example DD1 DD UNIT CART VOL SER L1B001 DISP 0LD Assume volume LIB001 resides in a library All drives outside the library are excluded from consideration for this allocation Exclusion Level 7 For volumes residing in the library the ACS location of the volume reduces the remaining list of eligible drives Any drives that remain that do not reside in the same ACS as the volume are excluded For example DD1 DD UNIT CART VOL SER ABBVL1 DISP 0LD Assume volume AOOVLI resides in ACSOO and the drives reside in ACSOO and ACSO1 The drives residing in ACSO1 are excluded from consideration for this allocation Additionally for resident VTVs drives that do not reside in the resident VTSS are excluded This allows you to set your default minimum level to 3 if you use mixed density drives Chapter 4 SMC Allocation in a JES Environment 35 312614001 Rev B Exclusion Level 8 Exclusion levels and 3 restrict the list of eligible drives to those compatible with the volume s actual media and its recording technique if specified on the HSC server VOLATTR statement Exclusion level 8 may further restrict the drives for the request based on the TAPEREQ recording technique The SMC TAPEREQ definitions can explicitly denote a recording technique for the allocation request For exa
151. fatal error in its main task and is attempting to perform an orderly shutdown Forcibly terminating task t Explanation The task is forcibly terminated Disable abend handling option specified handling disabled Explanation The HTTP server abend handlers will not be enabled so any abends can cause dumps and may also shut down the server Error initializing translation tables Explanation An error occurred while initializing the server file name translation table SERVERBASE not set shutting down Explanation The required parameter SERVERBASE was not set in the parameter file The server shuts down because it cannot locate its data files Authentication request received from client at XXX XXX XXX XXX PPPP Explanation A request to authenticate was received from the client at network address XXX XXX XXX XXx and port pppp Chapter 10 Sun StorageTek HTTP Server Messages 199 312614001 Rev B SKY100W SKY1091 SKY100W SKY101W SKY102E SKY103E SKY104E SKY105E SKY106E SKY1071 SKY108E SKY1091 Unable to set socket option to value Explanation The named socket option could not be set Processing continues Unable to set socket option Explanation A socket option could not be set Socket option error explanation Explanation Indicates why a socket option could not be set Cannot open parameter file dsname terminating Explanation The HTTP server was unable to open the parameter file d
152. fies the subpool name ESOTeric optionally specifies the esoteric defining the list of eligible transports to be used to satisfy a tape request esoteric group name Specifies the esoteric group name The name specified can consist of one to eight alphanumeric or national characters A slash or hyphen is also valid MGM Telas optionally specifies a Management Class you defined on the VTCS MGMT clas control statement Refer to the VTCS Command and Utility Reference for more information mgmt class name the Management Class name Caution If you specify a Management Class on the MGMTclas parameter you must specify both Media V and RECtech V Chapter 6 Commands and Control Statements 111 312614001 Rev B TRace TCPip Command The SMC TCPip command alters or lists the current TCPNAME and ADSNAME defaults for your TCP IP communications environment It allows you to direct TCP IP requests to a specific TCP IP stack on an MSP host The TCPip command can be issued at any time tcpip parms none none Rey A O le tor Command Name TCPip initiates the TCPip command Parameter Descriptions List optionally lists current TCPNAME and ADSNAME TCP IP defaults OFF optionally specifies that system defaults are used for TCP IP communications TCPname optionally specifies the TCPNAME value for a specific TCP IP stack on an MSP host name indicates the TCPNAME value ADSname optionally specifies
153. follows CMDDEF PREFIX B F As a result SMC operator commands can be entered as follows BOF MSGDEF CASE MIXED 72 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B DRIVemap DRIVemap Command The SMC DRIVemap command is used to map client drive addresses to server drive addresses This command allows users to specify different MSP device addresses on different hosts for the same library or virtual drives in client server mode See Chapter 2 SMC and Sun StorageTek Library Management for more information about drive mapping IS Note See Client Server Drive Address Mapping on page 18 for information about using DRIVemap commands and the HSC DRVHOST parameter when client and server addresses differ Syntax LIst gt oavenap lt OFF ecient devnum q devnum range SErver devnum devnum range devnum 1ist Command Name DRIVemap initiates the DRIVemap command Parameter Descriptions List optionally lists all current DRIVemap mappings This is the default if no parameters are specified OFF optionally removes all current DRIVemap mappings If specified with CLient this parameter removes DRIVemap ranges specified in the CLient parameter CLient specifies the device numbers mapped by the DRIVemap command SErver specifies the device numbers that are defined on the HSC server The ranges and lists must match those in the CLient
154. from the client at IP address xxx xxx xxx xxx port pppp No active client connections Explanation This message is issued in response to a display client console command when there are no clients currently connected to the server Missing to from translation string Explanation The data set file name translation is incorrect Connections total nn max mm min Explanation This message is issued in response to a display client console command There have been a total of nn connections at a maximum rate of mm per minute Not APF authorized some facilities not available Explanation The HTTP server is not APF authorized Chapter 10 Sun StorageTek HTTP Server Messages 197 312614001 Rev B SKY032I SKY051E SKY032I SKY040I SKY043E SKY045E SKY046E SKY047E SKY048E SKY049E SKY050E SKY051E Connection rates nn min mm hour Explanation This message is issued in response to a display client console command The connection rates are nn per minute and mm per hour Option nnnn ssss Explanation The parameter option nnnn is set to ssss Terminating execution due to parameter error s Explanation There was an error in one or more parameters The server shuts down SAF authentication requested but not APF authorized Explanation SAF authentication requires caller to be APF authorized but server is not APF authorized The server shuts down Supplied parm is too long Explanation The length of th
155. fy the unique connection between the server node and a specific port on the server and the client node and a specific port on the client The connection number exists only as long as the connection exists console The primary I O device to control a session on a system control data set CDS The data set used by the host software to control the functions of the automated library Also called a library database Control Path Adaptor CPA A Bus Tech Inc hardware device that allows communications between a host processor s block multiplexer channel and a local area network Control Unit CU A microprocessor based unit situated locally between a channel and an I O device It translates channel commands into device commands and sends device status to the channel coupling facility A special logical partition that provides high speed caching list processing and locking functions in a SCMP D coupling facility channel A high bandwidth fiber optic channel that provides the high speed connectivity required for data sharing between a coupling facility and the central processor complexes directly attached to it 1 CTC Channel to channel D Data Path Adapter A hardware device which translates from a client computing system s data protocol to the data protocol of the Sun StorageTek Control Unit or IMU An example is DEC s TC44 AA BA STI to 4400 ACS Interconnect data set A set of records treat
156. g criteria are evaluated by the SMC in the order shown to determine which library subsystem controls the allocation request 1 Libraries are interrogated in the order they are defined If LIBrary commands are defined to the SMC the order of the LIBrary commands is used If LIBrary commands are not defined to the SMC the subsystem order in the MSP SSCVT subsystem table is used 2 If the Eligible Device List EDL for the request does not contain drives owned by a specific library that library cannot own the request unless overridden by explicit subsystem or library selection 3 If the TAPEREQ esoteric contains only drives in a single library it is selected as the request owner 4 Ifa user exit explicitly selects a subsystem name or library name that is active that library is the owner even if it does not contain any drives in the EDL 5 Ifa specific requested volume is found in a library that library is considered the owner unless overridden by explicit subsystem or library selection Ifthe volume is not found in a library but that library contains a VOLATTR for that volume then the library is considered the owner if the specific volume is not found in any other library 6 Ifa library indicates that it has scratch volumes for the request it is considered the owner unless overridden by explicit subsystem or library selection If the library does not have scratch volumes for the request but the specified subpool name is known to
157. gram to produce an extract file in the following format Position Field Format 1 Scratch volume CL6 7 GMT of run XL8 15 Unused CL2 The time filed in the SMC scratch extract file is a character representation of the first four bytes of the output of the MSP STCK macro For example if the STCK macro produces a result of X B0912345 6789ABCD the GMT field of the SMC extract contains the character value C B0912345 SMCUDBX SLUDRCA 1 SLUDRTLM and SLUDRZAR are provided as load modules You can use the current versions of these load modules with CA DYNAM TLMS Release 5 4 and above CA 1 Release 5 0 and above and Zara 1 2 The HSC SAMPLIB file on the base installation tape contains the sample source code IS Notes If there are local modifications to your tape management system you must reassemble the associated READ routine If your tape management system is CA 1 Release 4 9 or below you must modify and reassemble the SLUDRCAI routine See Using SMCUDBX with CA 1 Release 4 9 or Below for information about modifying and reassembling this routine If your tape management system is CA DYNAM TLMS Release 5 3 or below you must reassemble the SLUDRTLM routine See Using SMCUDBX with CA DYNAM TLMS Release 5 3 or Below for information about reassembling this routine If your tape management system is Zara the SMCUDBX utility must be able to access the data set that contains the Zara API module ZARAAPI1 You can e
158. hardware or communication errors with either a local or remote HSC e Use of the RESYNChronize command to automate pending mounts for newly active HSC systems requires that the SMC MOUNTDef AUTOPendmount ON option is specified Use of the RESYNChronize command to automate pending mounts for newly active HSC systems should be issued after the HSC system has reached FULL service level Chapter 6 Commands and Control Statements 95 312614001 Rev B SERVer SERVer Command The SMC SERVer command defines a named path to a remote library server an HSC subsystem executing on another host The SERVer command describes the communication path to the Sun StorageTek HTTP server IEY Notes Before a SERVer is defined the LIBrary that it references must be defined using a LIBrary command The library name associated with a SERVer cannot be changed See LIBrary Command on page 76 for more information Syntax LIst gt SE RV e r A gt NAme name ENable HNAme name LIBrary name Server path parameters NAme name LIBrary name Server path parameters Note A LIBrary name must be specified when the SERVer NAME is first defined Server path parameters POrt 80 WA1t 68 REtry 3 FAi1 Host hastnane ___ _ L IPaddress ipaddress POrt nnnn WAit nnnn REtry nnnn FAil nnnn INITFail 8 aa 96 SMC 6 1 MSP Configuration and Administration Guide 312
159. he SMC encountered a READ command but the specified DDNAME or DSNAME could not be opened System Action The READ command is ignored User Response Look for Fujitsu related messages in the SYSLOG or job log and refer to Fujitsu documentation for more information Identically named subsystem SSSS is initializing Message Level 0 Explanation During initialization the SMC subsystem initialization program detected an identically named SMC subsystem SSSS already being initialized but not yet fully active System Action The currently initializing SMC subsystem terminates User Response Only one SMC can be active on a system at a time If the prior SMC subsystem SSSS was terminated abnormally and is not truly active then restart SMC SSSS with the RESET execution parameter 1 0 error reading DDNAME SMCPARMS SMCCMDS DSNAME DDDDDDDD Message Level 0 Explanation The SMC received an I O error attempting to read the SMCPARMS or SMCCMDS data set specified in the SMC started procedure or a data set specified on a READ command System Action The indicated data set is not processed User Response Determine the cause of the error If the input data set is a PDS ensure that a member name was specified Command beginning at line nnnn of SMCCMDS SMCPARMS is too long input ignored Message Level 4 Explanation The SMC encountered a multi line command beginning at line nnnn of the specified file This command exceeds 1024
160. in the command data set is correct or enter the corrected command Keyword KKKKKKKK of the CCCCCCCC command is not allowed for EEEEEEEE at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified keyword KKKKKKKK which is not valid in the current operating environment EEEEEEEE System Action Processing continues The command is ignored User Response Ensure that the specified keyword is valid in your environment Chapter 9 SMC Messages 145 312614001 Rev B SMC0019 SMC0022 SMC0019 SMC0020 SMC0021 SMC0022 Duplicate keyword KKKKKKKK specified for the CCCCCCCC command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified the same keyword KKKKKKKK more than once System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command Keyword KKKKKKK1 of the CCCCCCCC command is mutually exclusive with keyword KKKKKKK2 at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified multiple keywords two of which KKKKKKKT1 and KKKKKKK2 are mutually exclusive System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command COLD WARM start failure
161. ing feature of its CA 1 tape management system OFF do not update DEFER status at SSI24 time This is the default value ON update DEFER status at SSI24 time Specify this value if you use the Real Time Stacking feature of CA 1 DEFer enables or disables deferred mount processing for library mounts With deferred mounting enabled a library resident volume is mounted when the data set is opened If the data set is not opened the cartridge is not mounted freeing the robot to perform other work Ifthe data set is opened however the job waits until the cartridge is mounted ON enables deferred mount processing This overrides the user s JCL and defers all ACS mounts until the data set is opened This is the default setting for JES environments OFF disables deferred mount processing and honors user JCL specifications Chapter 6 Commands and Control Statements 63 312614001 Rev B ALLOCDef EXTVOLesot optionally instructs the SMC to use the specified esoteric to allocate a specific external volume i e a volume that is not in the library When this esoteric is used depends upon the setting of the modifier value specified after the esoteric as well as whether the specified esoteric is valid intersects with the original esoteric specification OFF indicates that EXTVOLesot processing is disabled If OFF then nonlibrary drives will be selected if possible when a specific external volume is allocated This is the default
162. ing on the Library Control System processor that controls the functions of the ACS HSC See Host Software Component HTTP Hypertext Transfer Protocol IEEE 802 3 A standard produced by the IEEE and accepted worldwide for local area networks using CSMA CD Carrier Sense Multiple Access with Collision Detection ICRC Improved Cartridge Recording Capacity A compression and compaction feature that increases the amount of data that can be stored on a 1 2 inch cartridge initial program load IPL A process that activates a machine reset Intelligent Management Unit IMU Hardware similar to a Control Unit This term is reserved for future products Internet A collection of networks using TCP IP that functions as a virtual network Internet address The numbering system used to specify a network or host on that network for TCP IP communications Standard Internet address notation is dotted decimal format Internet Protocol IP Formal description of messages and rules two networks use to exchange messages J job control language JCL A problem oriented language designed to describe a job s processing requirements to an operating system JES Job entry subsystem I JES An MSP subsystem that receives jobs into the system converts them to internal format selects them for execution processes their output and purges them from the system In an installation with more than one processor
163. ings and override settings in the order they are processed by job name step name and PROC step This is the default if no parameters are specified It cannot be specified with any other parameter Chapter 6 Commands and Control Statements 67 312614001 Rev B ALLOCJob OFF optionally removes all job name step name and PROC step overrides for allocation Ifno other parameters are specified allocation overrides are removed for all jobs Ifonly JOBname is specified allocation overrides are removed for ALL ALLOCJob entries for that job name If JOBname STEPname and PROCstep are specified allocation overrides are removed only for the specified entry Global allocation settings are not affected by this parameter JOBname optionally specifies a job name This parameter is required unless LIst or OFF is specified jobname indicates the job name The value entered must be one to eight characters in length An asterisk can be used as a wildcard when included as the last character ALLOCJob is set for all jobs whose job names match the characters preceding the asterisk STEPname optionally specifies a step name This parameter is only valid when JOBname is also specified stepname indicates the step name The value entered must be one to eight characters in length An asterisk can be used as a wildcard when included as the last character PROCstep optionally specifies a PROC step This parameter
164. ining multiple TAPEREQ control statement members hostid the name of one or more hosts from which to execute this control statement Multiple host names must be separated by commas RELOAD reloads the currently loaded TAPEREQ control statements from the same data set This parameter can be used after a TREQDEF DSN dsn command is issued and changes may then be made to the contents of that data set Example The following example illustrates the use of the TREQDEF command Load the TAPEREQ Parameters from YOUR DSN MEMBER TREQDEF DSN YOUR DSN MEMBER 120 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B UNITAttr UEXit Command User exits 1 2 8 9 and 10 are invoked and managed by the SMC The UEXit command defines which load module is invoked for a specific user exit and whether the user exit is enabled or disabled HSC user exit formats are supported The UEXit command specifies the desired format rs Notes Use this command to load each user exit you wish to use Ifa user exit is not loaded it will not be called e All user exits are executed on the host where the SMC resides regardless of where the library server resides e HSC User exit 7 SLSUX07 is no longer supported e These user exits must reside in a library accessible to the subsystem SMC STEPLIB JOBLIB or you system s LINKLIB concatenation e Refer to the NCS User Exit Guide for information about each u
165. ion Control Protocol Internet Protocol trace event type Types of event traced through the system when tracing is enabled trace file A file that contains information useful for debugging the system transaction A specific set of input that triggers the execution of a specific process Transmission Control Protocol TCP An inter network standard protocol that provides a full duplex stream service transport An electro mechanical device used to thread position and read or write from a tape Glossary 229 312614001 Rev B U UCB Unit Control Block userid The userid is the name that identifies a specific virtual machine user or client utility Program that performs a function ancillary to the chief function s of a computer system V virtual storage A feature of the OS where main storage requirements are allocated by segments or pages as needed by programs thus creating the apparent existence of unlimited or virtual storage Virtual Storage Manager VSM A storage solution that virtualizes volumes and transports in a VTSS buffer in order to improve media and transport use Virtual Tape Control System VTCS The primary host code for the Virtual Storage Manager VSM solution This code operates in a separate address space but communicates closely with HSC Virtual Tape Storage Subsystem VTSS The DASD buffer containing virtual volumes VTVs and virtual drives VTDs
166. ional information Sun s External Web Site Sun s external Web site provides marketing product event corporate and service information The external Web site is accessible to anyone with a Web browser and an Internet connection The URL for the Sun external Web site is http www sun com The URL for Sun StorageTek brand specific information is http www sun com storagetek Product Publications The Sun Documentation Web site provides online access to Sun product publications http docs sun com To order hardcopy versions of Sun publications contact a Sun sales or marketing representative Partners Site The Sun Partners site is a web site for partners with a Sun Partner Agreement This site provides information about products services customer support upcoming events training programs and sales tools to support partners Access to this site beyond the Partners Login page is restricted On the Partners Login page Sun employees and current partners who do not have access can request a login ID and password and prospective partners can apply to become Sun StorageTek resellers The URL for partners with a Sun Partner Agreement is http www sun com partners Customer Support Customer support is available 24 hours a day seven days a week to customers with Sun or StorageTek maintenance contracts and to Sun employees The URL for Sun Storage TekTM support is http www sun com storagetek support xxvi S
167. iption and patented allocatability testing algorithms In all cases the SMC attempts to ensure that the most important policies and criteria are applied first For example the SMC ensures that a specific volume is never allocated to an incompatible drive type Other policies those above minimum level are considered optional The SMC will ignore optional policies in order to be able to allocate the job 2 In JES SMC allocation uses documented operating system interfaces IEFSSI IEFSSTA IEFJFRQ to perform allocation influencing For the most part if no parameter overrides such as MIACOMPAT or CAIRTS are specified the SMC performs its modifications at SSI 78 MSP tape allocation rather than updating the Eligible Device List EDL at SSI 24 In some cases other vendors products rely on the Sun StorageTek EDL modifications at SSI 24 to work correctly You can specify MIACOMPAT ON to force the SMC to update the EDL as earlier NCS releases did 3 SMC policies use logical defaults including e Always separate affinity chains e Always honor user exit and TAPEREQ policies for head of chain when an affinity chain is not separated e Allow allocation to fail when a volume can not be mounted Do not attempt to influence allocation if the original list of eligible drives does not contain any drive known by Sun StorageTek For most customers these changes eliminate the need to specify previously required policies such as UNITAFF SEP and
168. is only valid when JOBname and STEPname are also specified procstep indicates the PROC step The value entered must be one to eight characters in length An asterisk can be used as a wildcard when included as the last character 68 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCJob BYPass optionally specifies that SMC allocation influencing is not performed for the indicated job job step step name PROC step This parameter cannot be specified with the MINLvl or SEPLvl parameter It is only valid when JOBname is also specified IEY Note It is recommended that you use MINLV 0 instead of BYPASS except when no mounts will be performed i e IEFBR14 jobs MINLvl optionally specifies the desired minimum level of drive exclusion Ifa job is not allocatable at the minimum exclusion level the SMC still excludes drives to the minimum level and allows the job to fail This parameter cannot be specified with the BYPass parameter It is only valid when JOBname is also specified minlevel indicates the desired minimum allocation exclusion level Valid values are 0 8 0 indicates that the SMC will not exclude any drives even if all drives would be excluded during level 1 exclusion processing The default is the current value of the ALLOCDEF MINLVL setting See Chapter 4 SMC Allocation in a JES Environment for more information regarding SMC exclusion levels IS Notes e Setting MINLVL 0 i
169. ither store this module in the LINKLIST or include a JOBLIB or STEPLIB DD statement in the SMCUDBX JCL that points to the library containing the module Any routine that you modify and reassemble must be re linked as non reentrant NORENT parameter with AMODE 24 and RMODE 24 132 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Using SMCUDBX with CA 1 Release 4 9 or Below To use SMCUDBX with CA 1 Release 4 9 or below you must modify and reassemble the SLUDRCAL1 routine The CA 1 MACLIB containing the TMRECORD MACRO must be accessible during the assembly Perform the following steps for CA 1 Release 4 9 1 Delete the asterisk in column 1 of the following line TMRECORD 2 Add an asterisk in column 1 of the following line TMMTMREC 3 Reassemble the SLUDRCA 1 routine Using SMCUDBX with CA DYNAM TLMS Release 5 3 or Below Perform the following steps to use SMCUDBX with CA DYNAM TLMS Release 5 3 or below 1 Verify that the CA DYNAM TLMS Release 5 3 MACLIB containing the VMFBASE MACRO is accessible for the re assembly of the SLUDRTLM routine 2 Reassemble the SLUDRTLM routine no modifications to the source code are required Chapter 8 SMC Tape Management Extract Utility 133 312614001 Rev B Specifying Values for the PARM Parameter You can specify the following values for the PARM parameter on the JCL EXEC statement when running the Scratch Extraction utility gt gt PARM _ Ly Optional
170. itialization memory could not be allocated for mmm memory The server shuts down Unable to open log reason rrr Explanation The log handler task was unable to open the log file for reason rrr Out of memory for stack space requested nnnn bytes Explanation An HTTP server task was unable to allocate stack memory No free worker tasks at maximum limit Explanation A request has been received but there are no idle worker tasks and the number of tasks is at the maximum limit A server busy request is returned to the client If this condition occurs frequently consider increasing the maximum limit of worker tasks to a value where this is a rare occurrence Chapter 10 Sun StorageTek HTTP Server Messages 203 312614001 Rev B Appendix A Intercepted Messages Fujitsu Operating System Messages The messages listed in Table 6 are received by the SMC Fujitsu message manuals describe the exact format spacing etc and definition for each message Ellipses are used to indicate that the message contains more text than is shown Correct operation of the SMC depends on these messages Do not suppress or alter them using products designed to handle messages through the subsystem interface SSI Many automated operations systems make use of the subsystem interface to intercept and alter or suppress messages IS Note If the suppressed by subsystem and hardcopy only bits are turned on in the WQE the MSP write queue element
171. itions Variable Data Definition AA ACSid n decimal value X hexadecimal value various letters C N K etc variable information character data numbers 1 2 etc related variable information combined with letters i e commands CCCCCCCCI and CCCCCCCC2 multiple choices optional field may not appear in message 140 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0001 SMC0004 SMC System Message Listing SMC0001 SMC0002 SMC0003 SMC0004 The following SMC messages are listed numerically SMC subsystem initializing Message Level 0 Explanation The MSP start command was entered for the SMC and the SMC subsystem initialization process has begun System Action None User Response None CCCCCCCCCCCCCCCC failed return code XXXX1 reason code XXXX2 Message Level 0 Explanation MSP facility or macro CCCCCCCCCCCCCCCC completed with the specified nonzero return code XXXX and reason code XXXX2 System Action Depending upon the type of error initiation termination may try to continue If the MSP facility is listed as Requested SDUMP the error occurred during the TRACE SNAP process and processing will continue without producing the requested SDUMP User Response Look for Fujitsu related messages in the SYSLOG or job log and refer to Fujitsu documentation for the explanation SMC subsystem SSSS terminating Message Level 0 Exp
172. itsu documentation for the explanation of return code XXXX Load failed for module MMMMMMMM Message Level 0 Explanation The SMC subsystem could not load the required module MMMMMMMM System Action The SMC subsystem terminates User Response Ensure that the SMC startup procedure has access to all SMC distributed load libraries in its steplib concatenation Termination waiting for job JJJJJJJJ JOBnnnnn in allocationlin message handling Message Level 0 Explanation The SMC subsystem received the MSP stop command but there is an active job JJJJJJJJ in tape allocation or message handling System Action The SMC waits for 30 seconds or until all active processes are complete User Response Ensure that there are no jobs performing tape allocation or message handling when the SMC is terminated Respond to any MSP allocation recovery messages Chapter 9 SMC Messages 143 312614001 Rev B SMC0013 SMC0015 SMC0013 TRACE settings CCCC CCCC Message Level 0 Explanation The TRACE command was specified with the LIST keyword The SMC0013 multiline message lists the current settings for the SMC subsystem Refer to the TRACE command for parameter descriptions System Action None User Response None SMC0014 Unmatched quotelor invalid parenthesis detected command ignored at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command containing an unterminated quoted string o
173. l drives for non labeled NL specific volume requests Chapter 4 SMC exclusion level 2 is updated for resident VTVs excluding virtual drives only if they are in a VTSS to which the VTV cannot be migrated and recalled Chapter 4 SMC exclusion level 5 is updated to exclude drives based on the SMC ALLOCDEF EXTVOLESOT esoteric Chapter 4 SMC exclusion level 7 is updated to exclude drives based on the resident VTSS This change allows customers with mixed density drives to set the minimum exclusion level to 3 Chapter 4 SMC exclusion MINLVL 0 is now valid for both ALLOCJOB and ALLOCDEF commands MINLVL 0 is used to force SMC to proceed with allocation even if none of the allocation level criteria are satisfied Chapter 4 Message changes additions and deletions Chapters 9 10 Appendix E xiv SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Use the following table to identify the SMC 6 1 replacement for a command control statement macro or specific parameter that was previously provided by the HSC HSC 6 0 Component Parameter SMC 6 1 Replacement Page TAPEREQ control statement TAPEREQ control statement 101 TREQDEF command and control TREQDEF command 119 statement UNITATTR control statement UNITATTR command 124 nonlibrary and IGNORE only UNITDEF command UNITATTR command 124 ALLOC command ALLOCDEF command DEFER DEFER Note Default ON
174. lanation The MSP stop command was entered for the SMC and the SMC subsystem termination process has begun System Action None User Response None MSP release is down level Message Level 0 Explanation An attempt was made to initialize the SMC on an MSP system that does not support the necessary services required by this version of SMC System Action The SMC subsystem terminates User Response Upgrade MSP to the required release level Chapter 9 SMC Messages 141 312614001 Rev B SMC0005 SMC0008 SMC0005 Invalid command CCCCCCCC at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation An undefined command CCCCCCCC was encountered by the SMC System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command SMC0006 SMC subsystem not dynamic Message Level 0 Explanation The SMC was defined as a nondynamic subsystem using the positional form of the SUBSYSxx parmlib member The SMC must run as a dynamic subsystem System Action The SMC subsystem terminates User Response Use the keyword format of the subsystem definition in the SUBSYSxx parmlib member to define the SMC subsystem or remove the SMC subsystem from the SUBSYSxx parmlib member SMC0007 SMCCVT incompatible with previous version defaulting to COLD start Message Level 4 Explanation During initialization the SMC subsystem detected that
175. llowing example two libraries DENVER and OMAHA are defined The first library DENVER has both a local HSC HSCO on the SMC host and a backup remote path on MSP system DEN1 SMC uses the local path unless the local subsystem is inactive or is disabled using the command LIB NAME DENVER LOCDIS If the backup remote path is used selected HSC messages are displayed on the client host LIBRARY NAME DENVER LOCSUBSYS HSCB WTORDEST CLIENT SERVER NAME DENBKUP LIBRARY DENVER HOST DEN1 PORT 8888 The second library OMAHA is always accessed using a remote server The SMC attempts to use the first defined server OMAHA1 If this server becomes inactive inaccessible or is disabled the SMC uses the next defined server OMAHA2 If the SMC is unable to communicate with either server no library requests are directed to the OMAHA library LIBRARY NAMECOMAHA WTORDEST CLIENT SERVER NAMECOMAHA1 LIBRARY OMAHA HOST OMA1 PORT 8888 SERVER NAMECOMAHA2 LIBRARY OMAHA 1P 11 22 33 44 PORT 7777 MSP hosts DEN1 OMA and the host represented by the IP address 11 22 33 44 must each have an instance of the Sun StorageTek HTTP server executing on them in order for SMC to communicate with the HSC on these hosts The Sun StorageTek HTTP server port must be defined as 8888 for the first two hosts and 7777 for the third host 100 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TAPEREQ TAPEREQ Tap
176. lso Initialization error messages will not be generated for every request but will only be generated at 5 minute intervals until the path is successfully activated System Action The allocation or mount event may not be processed by the SMC User Response Use the specified error reason to determine the cause of the problem If the error was produced for a remote server verify that the HTTP server is active ERROR WARNING No cartridge transport s for XXXX1 XXXX2 for UNITATTRIDRIVEMAP ADDRESS CLIENT Message Level 0 Explanation A UNITATTR or DRIVEMAP command was issued specifying a device XXXX1 or range XXXX1 XXXX2 None of the specified devices is a cartridge transport device System Action e Ifthe message indicates an ERROR the command is not processed Ifthe message indicates a WARNING the SMC stores the value and may use it to translate addresses for non MSP defined RTD devices User Response Review the devices specified in the command and re issue the command if they are incorrect LIBRARY LLLLLLLL1 has same LOCSUBSYS SSSS as LIBRARY LLLLLLLL2 at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A LIBRARY command was issued with a different library name LLLLLLLL1 but the same LOCSUBSYS name as an existing library LLLLLLLEL2 System Action The LIBRARY command is not executed User Response Correct the error and resubmit the command Chapter 9 SMC Messages 177 312614001 Rev
177. lumes 8 Exclude drives based on the requested recording technique Primary source TAPEREQ RECTECH parameter LOCTYPE ACSORVTSS POLRECTECH Keywords associated with each exclusion level are specified in the exclusion criteria displayed in message SMC0046 Level 2 is the default minimum level 32 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Exclusion Level 1 The SMC excludes drives that are not compatible with the volume media The volume media can be obtained from the volume label or from an HSC VOLATTR statement MEDIA parameter The SMC excludes all virtual drives for non labeled NL specific volume requests Note Specifying MINLVL 0 allows the allocation to succeed even if the volume s media conflicts with the EDL See ALLOCJob Command on page 67 for more information Exclusion Level 2 If the specific volume requested is a resident virtual volume the SMC excludes virtual drives that reside in a VTSS to which the VTV cannot be migrated and recalled Refer to the VTCS documentation for more information about virtual volumes Exclusion Level 3 Ifan HSC VOLATTR statement specified the recording technique RECTECH parameter for this specific volume the SMC excludes drives that do not provide that recording technique For example DD1 DD UNIT TLACS VOL SER VOL DISP OLD A VOLATTR statement has been defined to the HSC VOLATTR SERIAL VOL RECT
178. mands included in the MYCMDS member of the MY COMMAND PDS data set READ DSN MY COMMAND PDS MYCMDS 94 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SERVer RESYNChronize Command The SMC RESYNChronize command is used to re establish connections to all defined libraries for the purpose of acquiring drive configuration information from all libraries This action is automatically performed when the SMC first activates a new path to a library when an HSC subsystem local or remote reports a configuration change or when an active local path to a library is accessed during an MSP allocation or mount event However the operator must issue the RESYNChronize command in the following instances When the user wants to automate pending mounts for a newly activated HSC library and does not want to wait for an MSP allocation or mount event to trigger the reconnection To attempt to redrive outstanding mounts that may have been lost due to hardware or communication errors Syntax REStart Command Name RESYNChronize initiates the RESYNChronize command Parameter Descriptions REStart starts the RESYNChronize attempt at the first SERVER regardless of the last active path REStart also attempts to redrive any outstanding mounts IS Notes e The SMC RESYNChronize command is not required when communicating with HSC but may be used to redrive outstanding mounts that may have failed due to
179. me SMC subsystem SSSS is already active RESET specified startup continuing Message Level 4 Explanation During initialization of SMC subsystem SSSS the initialization program detected that the prior SMC subsystem terminated abnormally but the user specified the RESET execution parameter to ignore this condition System Action None User Response None Chapter 9 SMC Messages 151 312614001 Rev B SMC0041 SMC0044 SMC0041 SMC0042 SMC0043 SMC0044 Command Comment beginning at line nnnn of SMCCMDS SMCPARMS is unterminated Message Level 4 Explanation A command or comment beginning at line nnnn of an input command file ended with a continuation character but no continuation was found System Action Processing continues The command containing the unterminated string is ignored User Response Ensure that the syntax in the command data set is correct Job JJJJJJJJ step SSSSSSSS not allocatable before SMC modification Message Level 4 Explanation During execution of job JJJJJJJJ step SSSSSSSS the SMC allocation component detected that the job step was not allocatable before any allocation influencing was performed System Action None The job is failed by MSP or express canceled by JES User Response Correct the JCL Job JJJJJJJJ step SSSSSSSS not allocatable at MINLVL nn failing DD DDDDDDDD Message Level 4 Explanation During execution of a job with tape allocation the SMC allo
180. ments on page 57 for information about SMC commands that may be specified in either of these data sets The TISPAPPL DD statement identifies the data set used to obtain the VTAM G TISP server application names for TCP communication with the HTTP Server TIME 1440 must be coded to ensure that the SMC does not time out and terminate 22 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC EXEC Statement The EXEC statement is used to define SMC startup parameter settings EXEC Statement Syntax SSYS subsystem MSTR EXEC Statement Parameters PARM defines the list of parameters passed to the SMC initialization routine IEY Note Execution parameters must be separated with commas Separating parameters with blanks results in a syntax error WARM specifies that the SMC main control block is not rebuilt This is the default setting for normal operation COLD specifies that all SMC control blocks are rebuilt This parameter is mutually exclusive with WARM Warning Do not use this parameter unless the SMC has terminated abnormally and cannot be restarted SSYS specifies a subsystem ID that is different from the first four characters of the SMC START procedure The SMC searches for this subsystem ID during initialization subsystem must be one to four characters in length Chapter 3 Starting the SMC 23 312614001 Rev B RESET specifies that the active subsystem status flag in the MSP
181. mple DD1 DD UNIT CART VOL SER TV984 DISP NEW DSN SYS4 TR4 DATA Assume the requested volume is a 9840 volume in the library with no recording technique specified on a VOLATTR Assume an SMC TAPEREQ has been defined TAPEREQ DSN SYS4 TR4 RECT STKIRB Previous exclusion levels restricted the list of devices to all T9840 models In this example the TAPEREQ recording technique of STKIRB leaves only T9840B devices in consideration for this allocation 36 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scratch Volume Request Drive Exclusion Criteria For a scratch volume allocation the SMC excludes drives in order from lowest exclusion level to highest based on the criteria in Table 3 The lower the level number the more important the exclusion criteria Table 3 JES Drive Exclusion Levels Scratch Request Scratch Volume Criteria For nonlabeled NL scratch volume requests exclude all virtual drives Exclude all MODEL IGNORE drives Keyword VIRTUALLABEL For virtual volumes only exclude virtual drives that reside in a VTSS to which the VTV cannot be migrated and recalled AVAILVTSS Exclude drives based on the requested media Primary source TAPEREQ MEDIA parameter Secondary source User Exit 02 request for virtual media Exclude drives based on user location policies Primary source TAPEREQ ESOTERIC parameter Secondary source User Exit 02 and 10 return codes POLM
182. n cannot take place and the job is allowed to fail The SMC drive priority is assigned based on the following criteria For specific volumes drives in LSMs closest to the volume are preferred The SMC sets equal priority value for drives that are located the same number of passthrus from the volume For scratch volumes drives in LSMs with the largest number of scratch volumes are preferred The TAPEREQ DEVTPREF parameter causes drives with specific recording techniques to be preferred The TAPEREQ SCOPE parameter determines the relative priority of LSM location and drive type preferencing The following parameters control statements and user exits also influence the drive priority HSC ALLOC command parameters LOWSCR LSMPREF and SCRTECH e SLSUX02 HSC format user exit 02 After a final list of drives has been selected for allocation the preference order of the eligible drives after considering LSM and drive type preferencing is selected based on a last use algorithm To reduce excessive wear on allocated drives the SMC allocates drives by rotation based on the last mount time for each drive This value is examined for every drive in the final drive list The drive that had the most recent mount is located and the drive immediately following it in the list is selected as the most preferred for the current allocation IS Note This algorithm does not apply to virtual drives 48 SMC 6 1 MSP Config
183. n in a JES Environment 39 312614001 Rev B Exclusion Level 5 The combined media and specified recording technique of the volumes in a scratch subpool define this criterion for drive exclusion An SMC TAPEREQ SUBPOOL parameter can specify a scratch subpool name for the request If no TAPEREQ SUBPOOL parameter is specified for this allocation User Exit 02 can return a scratch subpool number or subpool name when it also sets the return code to use default processing or library drives User Exit 10 can also apply to affinity chains here Refer to Affinity Separation on page 44 for a discussion about the interaction between User Exit 02 and User Exit 10 IS Note When no specific subpool applies to the allocation the default subpool subpool 0 is used Drives that do not provide a recording technique compatible with a volume s in the subpool are excluded from consideration for this allocation For example DD1 DD UNIT CART DSN NEW TRK36 DATA DISP NEW KEEP Assume HSC has scratches of media types 36TRACK and DD3 in a subpool named SUBPOOL3 and an SMC TAPEREQ entry exists TAPEREQ DSN NEW SUBPOOL SUBPOOL3 Drives providing 36 track recording and helical recording remain in consideration for this allocation A User Exit 02 example for this criteria DD1 DD UNIT CART DSN SYS4 MYGROUP DATA DISP NEW KEEP Assume the following User Exit 02 returns UX02LIB e User Exit 02 returns MYSUBPL in UX02SNAM MYSUBPL h
184. n issues the WTOR to the operator of the system that the SMC executes on The SMC redrives the mount or dismount request to the server supplying the WTOR response Server WTOR messages are issued on the HSC server console This is the default SERVerlist lists defined libraries their attributes and associated servers The SERVerlist parameter may also be specified with the NAME parameter to limit the display to a single library NAME specifies the library name for which servers are to be listed name indicates the library name Example In the following example the LIBrary command defines a local HSC subsystem executing on the same host as the SMC LIBRARY NAME DENVER LOCSUB HSC In the following example the LIBrary command specifies that the remote subsystem OMAHA return selected WTORs to the SMC client without the remote HSC issuing the WTOR message LIBRARY NAMECOMAHA WTORDEST CLIENT SERVER NAMECOMAHA1 LIBRARY OMAHA HOST OMA1 PORT 8888 SERVER NAMECOMAHA2 LIBRARY OMAHA 1P 11 22 33 44 PORT 7777 IS Note The SERVer command must be specified to define the path to the remote library 78 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B LOG List Command The SMC LIst command is used to display storage accessible from the SMC started task address space Syntax I LIst Address address Length length lt CB control block name TA
185. nation A SERVER command was issued with the NAME of an existing SERVER and a LIBRARY name but the LIBRARY name of the existing server did not match the library name in the new command System Action The command is rejected User Response Omit the library name change the library name to match the existing server or change the SERVER name to add a new server to the specified library No LOCSUBSYS for LOCENABLE LOCDISABLE parameter on LIBRARY command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation A LIBRARY command was issued with a LOCENABLE or LOCDISABLE parameter but the library was not defined with a LOCSUBSYS subsystem name System Action This message is a warning The LIBRARY will be added or modified but the LOCENABLE or LOCDISABLE parameter is ignored User Response None 172 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0119 SMC0120 SMC0121 SMC0119 SMC0121 SERVER LOCSUBSYS CCCCCCCC now disabled Message Level 0 Explanation The SMC detected TCP IP errors in excess of the FAIL count or detected a fatal error for a local subsystem See the preceding SMC0128 SMC0129 messages for the reason for the disable System Action None If there are no additional server paths defined for the associated library the library hardware is no longer accessible from this host User Response Correct the problem with the TCP IP network SMC server host operating syst
186. nctions are not performed e volume lookup for allocation influencing automated mount processing When this occurs re start the library subsystem and issue the SMC RESYNC command The SMC automatically re establishes communication with the library and automates any outstanding mounts regardless of the SMC MOUNTDef AUTOPendmount setting See Automating Mount Requests for Inactive Libraries below for more information Certain software products allow you to suspend processing that may require dynamic allocation Common allocations can be postponed by holding the job queue or purging all initiators Refer to the appropriate Fujitsu publication for more information about JES operator commands Note You can provide a backup path to a remote library that is automatically activated when the local HSC is discovered to be inactive Automating Mount Requests for Inactive Libraries MSP mount requests for drives owned by inactive library subsystems are automatically redriven when the corresponding HSC library subsystem is activated Lost MSP Mount Requests for Active Libraries An MSP mount request may be lost when an LMU error occurs Use this procedure if you suspect lost mounts 1 Issue the following MSP command on the system requesting the mount to determine if any drives have a mount request pending D R L 2 Issue the following MSP command on the same system to determine which VOLSER to mount D U uuuu 1 3 Ifthe drive i
187. nd SMC0150 TREQDEF specifications installed from DDDDDDDD Message Level 0 Explanation The TAPEREQ statements in the data set specified on the TREQDEF command were successfully installed System Action None User Response None SMC0151 TREQDEF status Loaded from DDDDDDDD Title TTTTTTTT Loaded on YYYY MM DD at HH MM SS Message Level 0 Explanation The TAPEREQ command was issued with the LIST keyword The current TAPEREQ statements were loaded from data set DDDDDDDD The title TTTTTTTT is displayed if one was specified in the OPTION statement System Action None User Response None 184 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0152 SMC0153 SMC0154 SMC0155 SMC0152 SMC0155 TREQDEF DSN command has not been previously issued Message Level 0 Explanation The TAPEREQ LIST or RELOAD commands have been specified without a prior TREQDEF DSN command System Action None User Response Issue a TREQDEF command with the DSN keyword prior to issuing the TREQDEF with the LIST or RELOAD keyword Dynamic allocation failed for DDDDDDDD Message Level 0 Explanation Data set name DDDDDDDD specified in a READ command could not be allocated by the SMC System Action The command is not processed User Response Review the specified data set name to ensure that it is a cataloged MSP data set and re issue the command UNITATTR model MMMMMMMM ignored for library device
188. nd Task is shut down and a replacement task is created Task t cmp illegal instruction abend caught Code aaa Explanation The abend handler for task in component cmp intercepted an illegal instruction abend of type aaa Task t will be shut down and a replacement task created Task t cmp memory access abend caught Code aaa Explanation The abend handler for task tin component cmp intercepted a memory abend of type aaa Task t is shut down and a replacement task is created Task t request error nnn msg description Explanation For worker task t an HTTP protocol error was encountered for a client request ppp out of valid range min max Explanation The numeric parameter ppp is outside the allowed range hhh handler ready Explanation The handler Ahh task has finished initializing and is ready for work 202 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SKY1311 SKY132E SKY133E SKY134E SKY135E SKY136W SKY138W SKY1311 SKY138W hhh handler shutting down Explanation The handler Ahh task has started shutting down hhh handler startup timeout terminating Explanation The startup timeout for the handler task hh has been exceeded The handler will be terminated Unable to start hhh handler terminating Explanation The HTTP server was unable to start its handler task hhh The server shuts down Unable to allocate mmm memory terminating Explanation During in
189. nd was issued with the LIST keyword Each unique job job step and PROC step entry found in the ALLOCJOB queue is displayed in a separate SMC0055 message The BYPASSED message indicates that the specified job job step or PROC step will not have any of its tape allocations influenced by the SMC MINLVL nzn indicates the desired minimum exclusion level at which affinity and GDG chains are separated System Action None User Response None SMC0056 nn Bytes AAAAAAAA 8800 XX XX XX XX XX XX XX XX CC CC AAAAAAAA 001 XX XX XX XX XX XX XX XX CC CC AAAAAAAA 8800 XX XX XX XX XX XX XX XX CC CC Message Level 0 Explanation An SMC LIst command was issued The SMC0056 multiline message lists the nn bytes of storage in translated hexadecimal xx xx and character cc cc format each line listing the next 16 bytes X 10 bytes of storage beginning at hexadecimal address aaaaaaaa System Action None User Response None SMC0057 No SMCPARMS SMCCMDS DDNAME statement found Message Level 8 Explanation During SMC initialization the specified SMCPARMS DD or SMCCMDS DD was not present in the SMC startup procedure System Action Initialization continues User Response None 156 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0058 SMC0059 SMC0060 SMC0061 SMC0058 SMC0061 Error opening DDNAME SMCPARMS SMCCMDS DSNAME DDDDDDDD Message Level 0 Explanation T
190. ndicates that the job will not be failed by the SMC even if the device and specific volume are incompatible MINLVL 0 may be used to force SMC to allow allocation to succeed when a foreign tape cartridge has the same volume serial number as an existing library or virtual volume e Increasing minlevel has no effect unless message SMC0045 or SMC0091 has been issued for a specific job step Chapter 6 Commands and Control Statements 69 312614001 Rev B CMDDef SEPL vl optionally specifies the exclusion level at which affinity and GDG chains are separated This parameter cannot be specified with the BYPass parameter Itis only valid when JOBname is also specified MIN do not separate chains beyond the minimum level MAX separate chains for conflicting exclusion criteria whenever sufficient drives are available This is the default value seplevel indicates a level between the minimum and maximum levels When sufficient drives exist the SMC attempts to separate chains at this level See Chapter 4 SMC Allocation in a JES Environment for more information regarding SMC exclusion levels IEY Note The seplevel value cannot be less than the minlevel value Example In the following example the ALLOCJob command specifies that job PRODJOB1 with stepnames beginning with STEP1 be allowed to allocate even though SMC determines that volumes are not compatible with any drives in the EDL or esoteric ALLOCJOB JOB PRODJOB1 S
191. nection esoteric name The name assigned to transports that have the same device type Ethernet One LAN architecture using a bus topology that allows a variety of computers to be connected to a common shielded coaxial spine The Ethernet architecture is similar to the IEEE 802 3 standard event control block ECB Provides an area for a completion code to be stored when an operation has completed Glossary 225 312614001 Rev B F file A set of related records treated as a unit File Transfer Protocol FTP A TCP IP command that provides a way to transfer files between machines connected through TCP IP foreign socket One of two end points in a TCP IP connection oriented protocol Specifies the address of a foreign host that can connect to the server G GB 1 073 741 834 bytes of storage H handshake A flow of control signal sent by one process to another heartbeat interval Specifies how often CLS checks the communications link to a client to make sure it is still up helical cartridge A high capacity helical scan cartridge that can hold up to 50GB of uncompressed data This cartridge can be used only on RedWood SD 3 transports heterogeneous systems Systems of dissimilar processor or system type homogeneous Of the same or a similar kind or nature host computer A computer that controls a network of computers Host Software Component HSC Software runn
192. ng allocation when a communication failure prevents the retrieval of volume information from a library subsystem or library server or if no libraries are available OFF do not fail a job step when a communication failure occurs during the volume lookup process or if no libraries are available This is the default setting ALL or ON if a communication failure occurs during the volume lookup process or if no libraries are available then mark all devices ineligible and fail the job step SPECIFIC if a communication failure occurs during the volume lookup process for a specific volume or if no libraries are available and the step contains allocations for specific volumes then mark all devices ineligible and fail the job step If the job step contains only scratch allocations then the job step is allowed to proceed and allocation is based solely on TAPEREQ policy specifications 62 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ALLOCDef MIAcompat optionally specifies whether or not the EDL is to be modified at SSI24 time for compatibility with Computer Associates Unicenter CA MIA Tape Sharing for z OS and OS 390 product OFF do not update the EDL at SSI24 time This is the default value ON update the EDL at SSI24 time Specify this value if you use Unicenter CA MIA CAIrts optionally specifies whether DEFER processing is performed at SSI24 time for compatibility with Computer Associates Real Time Stack
193. ocedures to resolve problems in the server system reel id Identifier of a specific tape volume Equivalent to volume serial number VOLSER request Term used to refer to commands issued to the 4400 ACS to perform a tape related function S SCMP A set of MSP systems communicating and cooperating with each other through certain multisystem hardware components and software services to process customer workloads 1 seratch tape A tape that is available to any user because it is not owned 228 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B scratch tape subpool A defined subset of all scratch tapes Subpools are composed of one or more ranges of volsers with similar physical characteristics type of volume teel or cartridge reel size length physical location and so on Some installations may also subdivide their scratch pools by other characteristics such as label type SD 3 The Sun StorageTek helical cartridge transport Also known as RedWood server The communications component of the NCS solution also known as the Sun StorageTek HTTP server socket A unique address on a network plus a node address plus the id of one specific application on a specific network An abstraction used by TCP IP standard capacity cartridge A cartridge that can be used on any longitudinal transport i e 4480 4490 9490 or 9490EE standby The status of a station that has been
194. ocessing continues User Response If no compatible device is available reply NO to message KHE201D or KHE206D to stop the swap process If a compatible device is offline vary it online and reply with its device number to message KHE201D or KHE206D 168 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0109 SMC0110 SMCO0111 SMC0109 SMCO0111 The SMC subsystem is running in key n results are unpredictable reply Y to continue or N to terminate Message Level 0 Explanation During initialization SMC detected that it is running in key n not 1 through 7 System Action The SMC waits until a reply is received User Response A reply of N stops SMC A reply of Y causes SMC to continue initialization though results are unpredictable Possible problems are SOC1 and SOC4 ABENDs To prevent this message update the Program Properties Table PPT with PPT PGMNAME SMCBINT SYST KEY n where n is between 1 and 7 inclusive Allow swap of VVVVVV from XXXX1 to XXXX2 Reply Y N or DEVICE Message Level 0 Explanation The SMC has intercepted DDR swap processing The SMC is awaiting operator approval to allow the swap System Action The SMC continues processing however the swap cannot complete until an operator reply is entered User Response To allow the swap to proceed using the selected device XXXX2 reply Y To select a different swap to device reply with its device a
195. on The SMC then applies SCOPE LIBrary to one ACS giving all of the preferred models in that ACS a higher selection probability A scratch request can be directed to any ACS whether or not it contains scratch volumes In this case the SMC applies SCOPE LIBrary to all ACSs giving all of the preferred models in all ACSs a higher selection probability IS Note To prevent a scratch request from being directed to an ACS with no scratch volumes use ALLOCDef Zeroscr ON See ALLOCDef Command on page 60 LSM Specifies that all of the preferred models within an LSM are to be given a higher selection probability than all of the alternate models within that same LSM while maintaining the ability to automate tape mounts Each LSM is processed individually without regard to the models attached to other LSMs in the ACS This means that if the preferred model is not available in the LSM where the volume resides an alternate transport in the same LSM is allocated preventing a pass thru of the volume to a different LSM SCOPE LSM should be requested if reducing pass thru events is more important than allocating a preferred transport in a different LSM SCOPE applies only when DEVTpref is specified LIBrary is the default value for the SCOPE parameter 110 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B A TRace SUBPool optionally specifies the subpool used to satisfy a scratch request subpool name Speci
196. ontinues User Response If a command prefix is desired add the CMDDEF command to the SMCPARMS data set The command is processed the next time SMC is initialized The command prefix is PPPPPPPP Message Level 0 Explanation The command prefix for the subsystem is set to PPPPPPPP System Action The SMC now accepts commands prefixed with PPPPPPPP User Response None Command prefix value VVVVVVVV contains invalid character C at line nonn of SMCPARMS Message Level 0 Explanation The command prefix value VVVVVVVV of the CMDDEF command contained an invalid character C System Action Processing continues The command is ignored User Response Review the list of valid characters for the command prefix listed with the CMDDEF command description Update the CMDDEF command in the SMCPARMS data set with the new prefix value The command is processed the next time the SMC is initialized Command prefix not added prefix is not unique CPF system error Message Level 0 Explanation The command prefix was disallowed by the CPF facility because the prefix was not unique or a system error occurred System Action Processing continues The command is ignored User Response If the prefix is not unique compare the prefix with those of the other subsystems The command prefix cannot include a command string a command abbreviation or any string that invokes a command The command prefix cannot include a string that is a subset or s
197. over library drives User Response Change the JCL to request a supported label type or change the policy to direct the allocation to a different device type SMC0075 SEPLVL cannot be less than MINLVL on the CCCCCCCC command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified either a SEPLVL that is lower than the applicable MINLVL or a MINLVL higher than the applicable SEPLVL System Action Processing continues The command is ignored User Response Ensure that command MINLVL and SEPLVL values are correct in the command data set or enter the corrected command SMC0077 Subtask CCCCCCCC terminating at retry count n please start and restart SMC subsystem Message Level 0 Explanation The specified SMC subsystem task abnormally terminated N times and could not be restarted The subsystem is now operating without a required service System Action Processing continues However specific allocation or command facilities may be affected User Response Stop and restart the SMC subsystem If the named subtask is SMCOCMD use the MSP CANCEL command to terminate the subsystem 160 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0078 SMC0079 SMC0080 SMC0081 SMC0078 SMC0081 No command prefix defined Message Level 0 Explanation No CMDDEF command specified a command prefix in the SMCPARMS data set System Action Processing c
198. pecified with any other parameter 84 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B ES gt gt MSGDef AUTOPendmount specifies whether the SMC automates pending mounts for library drives found when SMC is first initialized and the owning NCS library subsystem or server is first activated ON automate pending mounts for library drives when the SMC determines that the owning library subsystem or server is first activated This is the default setting OFF do not automate pending mounts Note If AUTOPendmount is OFF you must issue an HSC MOUNT command to complete any pending mounts found when a library is first activated DISMSCRReal specifies how the SMC interprets the delete disposition on a dismount message for real nonvirtual volumes Note The DISMSCRReal and DISMSCRVirt parameters replace the DELDISP parameter of the HSC LIBGEN SLILIBRY macro OFF Retain the real cartridge as nonscratch when MSP indicates delete disposition in the dismount message This is the default setting and is recommended for CA 1 or CA TLMS users to leave volumes in a consistent nonscratch status during the CA 1 and CA TLMS grace period ON Scratch the real cartridge when MSP indicates delete disposition in the dismount message DISMSCRVirt specifies how the SMC interprets the delete disposition on a dismount message for virtual volumes Note The DISMSCRReal and DISMSCRVirt parameters replace the DEL
199. r invalid or unmatched parenthesis System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command SMC0015 Invalid keyword KKKKKKKK for the CCCCCCCC command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified an invalid keyword KKKKKKKK System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command 144 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0016 SMC0017 SMC0018 SMC0016 SMC0018 Invalid value VVVVVVVV for keyword KKKKKKKK of the CCCCCCCC command at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified keyword KKKKKKKK with an invalid value VVVVVVVV System Action Processing continues The command is ignored User Response Ensure that the syntax in the command data set is correct or enter the corrected command Keyword KKKKKKKK of the CCCCCCCC command requires a value at line nnnn of SMCCMDS SMCPARMS Message Level 0 Explanation The SMC encountered a command that specified keyword KKKKKKKK without an accompanying value required by most keywords System Action Processing continues The command is ignored User Response Ensure that the syntax
200. r the job to allocate Without SMC influence MSP allows the job to proceed through allocation However with SMC influence message SMC0043 is issued and the job fails Note No exclusion criteria including minimum level are applied when the user specifies demand allocation 1 e requests a specific drive or drives Subsequent Levels Once the minimum level of exclusion has succeeded the remaining exclusion levels are performed Any level above the minimum level that fails is skipped and exclusion continues to the next level Note A level fails if it results in too few drives for the DD statement to allocate The only required exclusion levels are those at the minimum level or below After the last drive exclusion level is completed the SMC examines the final drive lists If the job step cannot be allocated because not enough drives remain eligible drive exclusion regresses to the previous exclusion level for the failing DD statement This process repeats until the job step can allocate 30 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Intentionally Failing a Job Depending upon the characteristics of your installation you may want specific jobs to fail at allocation time rather than execute them with nonoptimal devices As an example if you have two ACSs one of which is located at a remote site you may prefer to fail the job rather than having to transfer the correct volume from one ACS to another
201. r was produced for a local library subsystem using cross memory services on this same host i e not using a server then the next line will list the interface error Ifthe communication error was produced for aremote HTTP server or its associated remote HSC library subsystem using TCP IP then one of the message reason lines will be displayed Examples of the reason strings include Specific TCP IP function errors connect send recv etc Data error incomplete or invalid data response e Subsystem inactive not found or at an incompatible release level Subsystem function error HTTP server not authorized HSC ASCOMM error Interface or communication timeout IS Note Certain remote errors may result in a display of the entire HTTP server response as follows Response from HTTP server follows HTTP 1 8 4091 Unauthorized If the message indicates Comm error limit nnn exceeded then the SMC0128 message will be followed by an SMCO119 message and the SERVER path will be disabled by the SMC 176 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0129 SMC0130 SMC0129 SMC0130 If the message indicates an Initialization error then the error occurred before any successful communication to the named SERVER path Such errors are not counted against the cumulative error count on the server path and will not result in the named SERVER being automatically disabled by the SMC A
202. raced or listed To trace all jobs specify TRACE JOB STEPname optionally specifies a step name stepname indicates the step name The value entered must be one to eight characters in length This parameter is only valid if JOBname is also specified PROCstep optionally specifies a PROC step procstep indicates the PROC step The value entered must be one to eight characters in length This parameter is only valid if JOBname and STEPname are also specified SNAPdump optionally requests a snap dump IS Note A snap dump may impact system performance and should be used only as directed by Sun Microsystems Software Support BEFORe perform a snap dump before allocation influencing AFTEr perform a snap dump after allocation influencing BOTH perform a snap dump both before and after allocation influencing 116 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TREQDef ALLProc enables tracing for all SMC components This is the default if no parameters are specified ALLOc optionally enables tracing for the SMC allocation component that performs drive exclusion and drive prioritization MSGHndlr optionally enables tracing for the SMC message handler component that processes all MOUNT DISMOUNT and SWAP messages and issues robotic movement commands to the Sun StorageTek tape library Examples In the following example tracing is enabled for any job whose name begins with TEST
203. ransport 36Btrack Indicates a 9490 transport 36Ctrack Indicates a 9490EE transport HELical Indicates a device using helical recording DD3 Indicates a device using helical recording STKIR Indicates any T9840 transport STK1R34 Indicates a 3490E image T9840 transport STK1R35 STKIRA Indicates a 3590 image T9840 transport Indicates a T9840A transport STK1RA34 Indicates a 3490E image T9840A transport STKIRA35 Indicates a 3590 image T9840A transport 212 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Table 10 Recording Techniques Continued Recording Technique Description STKIRB Indicates a T9840B transport STK1RB34 Indicates a 3490E image T9840B transport STK1RB35 Indicates a 3590 image T9840B transport STKIRAB Indicates a T9840A or T9840B transport STK1RAB4 Indicates a 3490E image T9840A or T9840B transport STKIRABS Indicates a 3590 image T9840A or T9840B transport STKIRC Indicates a T9840C transport STK1RC34 Indicates a 3490E image T9840C transport STK1RC35 Indicates a 3590 image T9840C transport STKIRD Indicates a T9840D transport STKIRDN Indicates a non encryption enabled T9840D transport STK1RD34 Indicates a non encryption enabled 3490E image T9840D transport STK1RD35 Indicates a non encryption enabled 3590 image T9840D transport ST
204. ransports The drive panel for a T9840 transport can contain either 10 or 20 transports The drive panel for a non T9840 transport can contain a maximum of 4 transports drive prioritization previously referred to as directed allocation refers to the Storage Management Component SMC function of influencing selection of a particular drive based on allocation criteria including volume location See the SMC Configuration and Administration Guide for more information Dual LMU A hardware microcode feature that provides a redundant LMU capability dump A printed representation of the contents of main storage at time This representation is used for debugging purposes dynamic server switching The capability of switching server processors when a system failure occurs on the active server E ECART Enhanced Capacity Cartridge Enhanced Capacity Cartridge A cartridge that has a length of 1100 feet and can be used only on 36 track transports i e 4490 9490 and 9490EE Enterprise Systems Connection ESCON A set of products and services that provides a dynamically connected environment using optical cables as a transmission medium I error codes EC Numeric codes displayed by messages indicating the type of problem that caused an error error recovery procedures ERP Procedures designed to help isolate and where possible to recover from errors in equipment ESCON Enterprise Systems Con
205. rcepted by the SMC are passed to the user exit The SMC does not support the user exit 01 return code of REPLY Chapter 5 SMC Message Handling 51 312614001 Rev B Message Handling Policies The SMC honors the following MSP and SMC policies related to mount dismount and swap message handling MSP Policies The System Authorization Facility SAF can be used to protect tapes at the volume level CLASS TAPEVOL using your current security software If defined the SMC honors the policies defined through the SAF interface regarding the write protect requirement for a volume mounted on a library transport The SMC invokes the SAF interface by issuing a RACROUTE macro and protects read only volumes through the ACS Virtual Thumbwheel VTW support SMC Policies The SMC MOUNTDef command is used to control message handling 1 e mount dismount options previously controlled by the HSC MNTD command in addition to HSC input parameters and LIBGEN options These options control the automation of pending mounts delete disposition at dismount time whether messages are produced when a library volume is mounted outside the library and when mount messages are rolled off the console IS Note This command is new for SMC release 6 1 See MOUNTDef Command on page 84 for more information 52 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Tape Management System Support The SMC interprets Mount Dismount and
206. rocessing is used Device addresses are identically defined for all hosts in a single client server network but not all devices are defined to all hosts Drive address mapping is not required However you must use the HSC SET SLIDRIVS utility to define all drive addresses on hosts that will be used as servers even if the devices are not defined to the host Refer to the HSC System Programmer s Guide for more information about the SET SLIDRIVS utility Client server processing is used Device addresses are identically defined to all HSC hosts but one or more SMC client only hosts use a different set of addresses for the same device Use the SMC DRIVemap operator command to map the SMC client host addresses to the HSC host addresses SMC performs the necessary address translations in influencing allocations and requesting mounts from the server See page 73 for more information about the SMC DRIVemap command Client server processing is used Two MSP hosts MSP1 and MSP2 both running HSC and SMC One MSP host MSP3 running only SMC but defined as communicating to either of the two hosts as a server Device addresses are defined differently among all three hosts For example MSP1 AA0 AAF MSP2 BAO BAF MSP3 CA0 CAF 1 Since the SMC on MSP3 can communicate with either the MSP1 or MSP2 host for a particular mount event you must use the HSC SET utility SET DRVHOST to designate one of these hos
207. ronment describes the SMC allocation function for a JES environment Chapter 5 SMC Message Handling describes the SMC message intercept function Chapter 6 Commands and Control Statements describes the SMC operator commands Chapter 7 Recovery Procedures describes procedures used when SMC or an HSC library subsystem becomes inactive Chapter 8 SMC Tape Management Extract Utility describes SMC system utilities Chapter 9 SMC Messages describes the SMC system messages Chapter 10 Sun StorageTek HTTP Server Messages describes Sun StorageTek HTTP Server messages Appendix A Intercepted Messages lists MSP and TMS messages that are intercepted by the SMC About this Guide xvii 312614001 Rev B e Appendix B MEDia RECtech and MODel Values describes valid values for parameters used to specify media types recording techniques and model types e Appendix C Differences Between SMC and HSC 6 0 and Below describes various differences between SMC and NCS 4 1 including those related to allocation and message handling Appendix D SMC Interaction with Other Software describes interaction with various third party software packages An index and glossary are also included Contact Us Sun welcomes your feedback Visit the Sun Documentation site at http docs sun com and click on the FEEDBACK link at the bottom right of the screen to access the Opinion Lab feedback s
208. s 128 track recording technique 4400 Automated Cartridge System ACS A fully automated cartridge based 18 track storage and retrieval library A 4400 ACS consists of 1 to 256 LMUs with each LMU connected to from 1 to 24 LSMs 4410 The standard Library Storage Module LSM 4411 Library Control Unit LCU 4480 The Sun StorageTek 18 track 1 2 inch cartridge transport 4480 Cartridge Subsystem The Sun StorageTek 4480 Cartridge Subsystem consists of a control unit CU plus cartridge drives CDs 4490 The Sun StorageTek 36 track long tape cartridge transport with ESCON support Also known as Silverton 230 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B 4780 Same as a 4480 but is used for attachment to certain non IBM computers 8380 Sun StorageTek DASD system 9310 The PowderHorn a high performance version of the standard LSM 4410 9360 The WolfCreek a high performance LSM with a smaller capacity than the standard LSM 4410 9490 The Sun StorageTek 36 track cartridge transport Also known as TimberLine 9490EE The Sun StorageTek 36 track cartridge transport Also known as TimberLine EE 9740 A small four sided Sun StorageTek library that supports large style cartridge transports This library can be configured to contain either 326 cartridges or 494 cartridges SL3000 The Sun StorageTek high performance library scalable from 200 to 3 000
209. s de maniere non exclusive la liste de personnes qui font objet d un ordre de ne pas participer d une facon directe ou indirecte aux exportations des produits ou des services qui sont regi par la legislation americaine en matiere de controle des exportations et la liste de ressortissants specifiquement designes sont rigoureusement interdites LA DOCUMENTATION EST FOURNIE EN L ETAT ET TOUTES AUTRES CONDITIONS DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFACON eo is Y Y Adobe PostScript Document Effectivity EC Number Date Doc Kit Number Type Effectivity 132246 May 2006 Revision A This document applies to SMC MSP Release 6 1 February 2009 Revision B Document Effectivity iii 312614001 Rev B Contents What S NOW coi A hoa cata 9 be bed laa seat gn aa Taaa eae ede betes xiii ADOQUETRIS QUIE ereere A wen cates A A ee a AA A oar xvii AUUGIONCE oa xvil Organization of This Guide o o ooooooooorrr eee nent nent teen nee xvil Contact US edea a o a o Rie ee othe ted xviii Conventions Used in this Guide nnna naana anana xviii Product Names id bebe Bi a aa ek Ged is Oa A a ae xviii Typographic ia tt a cing Beall dls m aaia aa Gil Gale lech Gari al xviii ll A a a a haa wes
210. s defined to an HSC library issue the HSC Mount command for the volume on the MSP system on which the HSC is active 128 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Chapter 8 SMC Tape Management Extract Utility Overview This chapter provides information for the Tape Management Extract utility used to support scratch synchronization between the SMC client host and the HSC CDS SMC Utility Return Codes and Messages SMC utilities may return the following return codes e A return code of 0 is returned when the utility program completes successfully with no errors or warnings e A return code of 4 is returned when a warning message is detected A return code of 8 is returned when an error that prevents the utility from completing is detected For a listing of SMC messages that may be returned by SMC utilities see page 193 These messages are identified by the SMCU prefix Chapter 8 SMC Tape Management Extract Utility 129 312614001 Rev B Tape Management Extract Utility The SMC utility SMCUDBX supports scratch synchronization between the SMC client host and the HSC CDS Using common tape extract modules SEUDRCA1 SLUDRTLM SLUDRRMM and SLUDRZAR with HSC the SMC accesses the client tape management system to produce an extract file that can be read as input by the HSC scratch tape conversion module SLUCONDB This process is illustrated in the following figure Client Server MSPA S
211. s not sufficient to allocate the scratch volume correctly investigate whether FAILNOINFO ALL ON should be specified Chapter 9 SMC Messages 191 312614001 Rev B SMC0226 SMC9999 Path switch from SERVER SSSSSSSS to SSSSSSSS for LIBRARY LLLLLLLL Message Level 4 Explanation The SMC automatically switched the communication path from the secondary server SSSSSSSS to primary server SSSSSSSS for library LLLLLLLL System Action Processing continues User Response None MMMMMMMM Variable text Message Level 12 16 20 24 28 Explanation SMC9999 messages are intended for Sun Microsystems Support problem determination and resolution MMMMMMMM is the name of the issuing module System Action None User Response None A message level LVL of 12 or higher should generally be specified only when directed by Sun Microsystems Support SMC Utility Message Listing SMCU0008 SMCU0009 SMCU0010 SMCU0011 SMCU0012 SMCUDBX input parameter error Explanation An error was detected in the input PARM for the SMCUDBX utility A detailed description of the error follows System Action The utility processing terminates with a return code of 8 User Response Correct the indicated error and resubmit the job Unable to load TMS interface routine SLUDRCA1 SLUDRTLM SLUDRRMM SLUDRZAR Explanation Explanation Based on the input TMS parameter the SMCUDBX utility attempted to load the corresponding tape management access
212. s or data set names at open time information available at Job Step Allocation time may be incorrect as interpreted by the SMC IS Note Some vendor software products use MSP Open Type J If you are experiencing unexpected allocation results using a vendor software product check with the vendor to determine if Open Type J is used and follow the recommendations below SMC allocation may be influencing MSP allocation erroneously based on information that may have changed at open time To prevent this problem when using the Open Type J macro specify the appropriate esoteric in the JCL or specify an appropriate esoteric in an applicable TAPEREQ control statement SAMS DISK DMS Sterling Software s SAMS DISK DMS has two methods of allocating transports e allocates transports at session startup holds onto the transports throughout the session and uses Open Type J refer to the section about Open Type J e uses dynamic allocation DYNALLOC to allocate transports when required The SMC allocates correctly when dynamic allocation is used Therefore the latter method of allocating transports is recommended MSP Security Packages Ensure that your MSP security package e g RACF TopSecret is configured to grant SMC the necessary authority to respond to MSP swap messages Appendix D SMC Interaction with Other Software 219 312614001 Rev B Appendix E Message Change Summary The following messages have been added changed
213. s terminated SKY007E Accept error shutting down Explanation There was an error in network connection accept processing The server shuts down SKY008E Error reading request Explanation A network error occurred while reading a client request SKY0131 Shutdown command from operator acknowledged Explanation The server has received a console command to shut down 196 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SKY016l SKY018l SKY023E SKY025E SKY026l SKY0271 SKY030E SKY0311 SKY031W SKY016I SKY031W name Server ver started at tttt requests received nnn tasks default dd active aa limit 1 Explanation Response to an operator display status command and indicates the server name version start date and the total number of requests received It also details the worker task settings the default number of idle tasks the maximum limit of dynamically started tasks and the current number of active tasks Request n task completed rc ret Explanation The worker task t has completed with return code ret Unknown server command cmd Explanation The command cmd is not a valid console command Invalid command option oooo Explanation The option 0000 is not a valid option for the operator command Task t Requests n Client xxx xxx xxx xxx pppp Explanation This message is issued in response to a display client console command Task has serviced n requests
214. s the default if no parameters are specified OFF optionally disables SMC tracing Ifno other parameters are specified tracing is disabled for all jobs e If only JOBname is specified tracing is disabled for all entries for that job name e If JOBname STEPname and PROCstep are specified tracing is disabled only for the specified entry SUbsys optionally enables or disables SMC tracing for one or more SMC subsystem components or subtasks OFf disables tracing for all SMC subtasks CMd enables tracing for the SMC subtask that processes all SMC operator commands INitterm enables tracing for the SMC subtask that performs SMC initialization and termination AScomm optionally enables tracing for the SMC address space component Tracing of library and configuration requests is performed only if tracing is also enabled for the jobname making the request Chapter 6 Commands and Control Statements 115 312614001 Rev B TREQDef CGi optionally enables tracing to the log of the Sun StorageTek HTTP server Tracing of HTTP server requests is performed only if tracing is also enabled for the jobname making the request JOBname optionally specifies a job name jobname indicates the job name The value entered must be one to eight characters in length An asterisk can be used as a wildcard when included as the last character In this case all jobs whose job names match the characters preceding the asterisk are t
215. se the following procedure to disable a TAPEREQ definition 1 Edit the definition data set containing the current TAPEREQ control statements 2 Delete the parameters of the TAPEREQ control statement you want to disable or delete the TAPEREQ control statement 3 Issue the TREQDEF operator command to reload the definition data set To disable all TAPEREQ definitions load a definition data set that contains only one TAPEREQ control statement with no parameters Chapter 6 Commands and Control Statements 101 312614001 Rev B TAPEREQ Syntax oa A A kk PROGram a rere ae DATASET E taset ge a _PGMname program name DSN dataset name RETPD GE retention period T EQ VoLTypec specific NE Nonspec EXPDT expiration date MEDi TEE A A E TETTE MODe1 eee DEVTpref model 1 C noder LIBrary model3 apet E gy O gt ae subpool name ei Pee eee a Wiimote e MGMTclas mgmt class name Figure 8 TAPEREQ Control Statement IS Note See Appendix B for valid media types recording techniques and model types 102 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TAPEREQ Control Statement Name TAPEREQ initiates the TAPEREQ control statement If any of the following conditions exist e there is no TAPEREQ control statement specified in the definition data set to match a request no matching TAPEREQ statement specifies th
216. ser exit Syntax Chapter 6 Commands and Control Statements 121 312614001 Rev B UNITAttr Command Name UEXit Initiates the UEXit command Parameter Descriptions LIst optionally displays status information for all user exits This is the default if no parameters are specified number optionally specifies the user exit number Valid values are 1 2 4 8 9 10 11 12 and 13 NAME optionally specifies the user exit s load module name name indicates the load module name e g SLSUX01 FORMat optionally specifies the format of user exit to be enabled or disabled HSC indicates the HSC user exit format LOAD optionally loads the specified user exit making it available for use IS Notes e Ifa user exit is not loaded it will not be called A subsequent load of a module for the same user exit causes the currently active copy of the load module to be deleted when its use count reaches zero ENable optionally enables a user exit that was previously disabled due to a problem DISable optionally disables a user exit to allow for problem resolution 122 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Example USERMsg In the following example the UEXit command is used to load the HSC format SLSUXO01 of user exit 01 UEXIT 1 NAME SLSUX 1 FORMAT HSC LOAD SLSUX01 is loaded from the SMC STEPLIB JOBLIB or your system s linklib concatenation
217. sname The server shuts down Parameter ppp invalid Explanation The parameter ppp is not known Unexpected character c encountered skipping line Explanation When parsing the parameter file an unexpected character was encountered The parameter is skipped by moving to the next line Expected number but non numeric ssss Explanation When parsing the parameter file a non numeric item was found when a number was expected parm set to vvv Explanation The parameter parm is set to value vvv Expected string ssss skipping Explanation When parsing the parameter file the string ssss was expected but not found Parsing skips to the next parameter pppp set to vvv Explanation When reading the parameter file the parameter pppp was set to value vvv 200 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SKY110E SKY112E SKY113E SKY1141 SKY1151 SKY116E SKY1181 SKY1191 SKY120E SKY121E SKY110E SKY121E Unknown token type tttt Explanation The parameter token is unknown Cannot create tbl terminating Explanation During initialization the memory table tbl could not be allocated The server shuts down Cannot start task tttt terminating Explanation During initialization the task tttt could not be started The server shuts down Task tttt completed rc nn Explanation Task ttt completed with return code nn Commencing server shutdown Explanation
218. soteric name that contains customer selected drives Any drives in the current list of eligible devices that did not match the user exit return values are excluded here For example DD1 DD UNIT CART VOL SER VOL 1 DISP O0LD User Exit 08 returns UXO8ASUB and ACSO which requests library drives and ACSO The drives that are not in ACSO are excluded from consideration for this allocation Exclusion Level 5 The ALLOCDEF EXTVOLESOT parameter is used to specify an esoteric to allocate specific external nonlibrary volumes Additionally the ALL modifier allows you to use this esoteric for all specific external volumes regardless of the value of the specific user exit return code Note The EXTVOLESOT esoteric replaces the HSC ALLOC SPECVOL ACS list The following describes how to use the SMC EXTVOLESOT to achieve the same functionality Ifyou used the UX08 SPECVOL return code specify EXTVOLESOT name USEREXIT Ifyou used the SPECVOL list to force all nonlibrary volumes to be allocated inside the library no defined NONLIB esoteric use EXTVOLESOT name ALL 34 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Exclusion Level 6 The generic location of the volume library or nonlibrary reduces the remaining list of eligible drives IS Note For exclusion level 6 nonlibrary drives are outside the library and contain either known from the SMC UNITATTR command or unknown device characteristics I
219. st s network address and a specific port for an application process LP See logical port LSM See Library Storage Module LSM id An LSM id is composed of the ACS id joined to concatenated with the LSM number LSM number A method used to identify an LSM An LSM number is the result of defining the SLIACS macro LSM parameter during a LIBGEN The first LSM listed in this parameter acquires the LSM number of 00 hexadecimal the second LSM listed acquires a number of 01 and so forth until all LSMs are identified up to a maximum of 24 or hexadecimal 17 Glossary 227 312614001 Rev B M manual mode Operation of a cartridge drive apart from an ACS See library mode master LMU The LMU currently controlling the functional work of the ACS in a dual LMU configuration mixed configuration A configuration that contains different types of cartridge drives in both manual and library modes modem A device that enables digital data to be transmitted over an analog transmission facility multi client The environment where more than one homogenous or heterogeneous client system is connected to one LCS N NCS Nearline Control Solution consisting of SMC HSC Sun StorageTek HTTP server and LibraryStation O OCR label Optical character recognition label An external label attached to the spine of a cartridge that is both human and machine readable operator console In this document
220. stem Action None User Response None Chapter 9 SMC Messages 181 312614001 Rev B nnnnnnnn SMC0143 Aannannannn SMC 141 UNIT value VVVVVVVV1 replaced by VVVVVVVV2 Message Level 0 Explanation The DFSMS ACS routines has changed the esoteric mnnnnnnn is the JCL statement number or the DDNAME if it is a dynamic allocation e VVVVVVVV1 is the esoteric that was in the JCL If a UNIT parameter was not used in the JCL this will be NULL UNIT e VVVVVVVV2 is the esoteric that was supplied by the DFSMS ACS routines System Action Use the new esoteric supplied by the DFSMS ACS routines for the allocation User Response None SMC0142 Invalid reply to prior message from LIBRARY LLLLLLLL SERVER SSSSSSSS Message Level 0 Explanation The WITORDEST CLIENT option was specified for LIBRARY LLLLLLLL and SMC has communicated a mount or dismount request to HSC via server SSSSSSSS When SMC attempted to redrive the request HSC returned an indication that the response was invalid System Action SMC redisplays the HSC message User Response Refer to the HSC Messages and Codes Guide for the valid responses for the indicated message SMC0143 Response timeout wait cancelled by SMC STOP for job JJJJJJJJ volser VVVVVVVV device XXXX from LIBRARY LLLLLLLL SERVER SSSSSSSS Message Level 0 Explanation SMC has communicated a request to LIBRARY LLLLLLLL via SERVER SSSSSSSS Either the response timed out or the SMC subsystem r
221. syntax in the command data set is correct or enter the corrected command TRACE JOBNAME JJJJJJJJ STEPNAME SSSSSSSS PROCSTEP PPPPPPPP SNAPDUMP DDDDDDDD CCCCCCCC Message Level 0 Explanation The TRACE command was specified with the LIST keyword The SMC0030 message lists the jobs step and PROC steps and the associated processes which have been specified for tracing System Action None User Response None 148 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0031 SMC0032 SMC0033 SMC0034 SMC0031 SMC0034 No SMC start mode specified defaulting to WARM start Message Level 4 Explanation During SMC initialization the subsystem detected that neither a WARM or COLD start was specified in the initialization program s execution parameters System Action Initialization continues in WARM start mode User Response None Number of SMC startup parameters specified exceeds maximum of n Message Level 0 Explanation During initialization the SMC subsystem initialization program encountered an execution parameter string containing too many parameters System Action The SMC subsystem terminates User Response Correct the subsystem initialization startup procedure to specify the correct execution parameter string SMC startup parameter PPPPPPPP may not have a value Message Level 0 Explanation During initialization the SMC subsystem initialization program encountered a valid
222. t 08 for DD1 and excludes all but library drives as requested by User Exit 10 Any one of the four return values UX10LDRV UX1ONDRV UX10ESUB and UXI0ASUB from User Exit 10 causes the SMC to operate as if ALLOCDEF SEPLvI MIN were specified IS Note Any User Exit 10 separation decision overrides the SEPLvl parameter of the ALLOCDef or ALLOCJob commands SEPLvI Parameter Value If the decision to separate or keep the affinity chain together still has not been made further affinity chain processing depends on the SEPLvl parameter value of the ALLOCDef and ALLOCJob commands refer to Chapter 6 Commands and Control Statements for descriptions of these commands and setting an affinity separation level The SEPLvl parameter operates in three distinct ways depending on the value specified The SEPLvl MAX parameter allows drive exclusion to be performed to the maximum level for each allocation element in the affinity chain At the end of the drive exclusion process if two or more elements of the chain no longer have common drives the affinity chain is separated For example DD1 DD UNIT 349 VOL SER INACS DSN MY DSN1 DISP 0LD DD2 DD UNIT AFF DD1 VOL SER INACS1 DSN MY DSN2 DISP 0LD Assume the following Both volume INACSO and INACS1 share common media characteristics e Volume INACSO resides in ACSO and volume INACS1 resides in ACS1 ALLOCDEF SEPLVL MAX has been specified Chapter 4 SMC Allocation in a JES Environm
223. ted to the denied persons and specially designated nationals lists is strictly prohibited DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID Copyright 2009 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 Etats Unis Tous droits r serv s Sun Sun Microsystems le logo Sun et Sun StorageTek sont des marques de fabrique ou des marques d pos es de Sun Microsystems Inc aux Etats Unis et dans d autres pays UNIX est une marque d pos e aux Etats Unis et dans d autres pays et licenci e exlusivement par X Open Company Ltd see above Les produits qui font l objet de ce manuel d entretien et les informations qu il contient sont regis par la legislation americaine en matiere de controle des exportations et peuvent etre soumis au droit d autres pays dans le domaine des exportations et importations Les utilisations finales ou utilisateurs finaux pour des armes nucleaires des missiles des armes biologiques et chimiques ou du nucleaire maritime directement ou indirectement sont strictement interdites Les exportations ou reexportations vers des pays sous embargo des Etats Unis ou vers des entites figurant sur les listes d exclusion d exportation americaines y compris mai
224. ternal Web site at http www sun com worldwide xxviii SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Chapter 1 Introduction What is SMC SMC the Storage Management Component is the interface between Fujitsu s MSP EX operating system and Sun StorageTek HSC automated library control systems SMC operates on JES systems and is a required NCS component Its primary functions are e Influencing tape allocation according to hardware requirements and customer policies to ensure that appropriate tape drives are selected e Intercepting tape management and operating system mount dismount and swap messages and translating them in order to request the required tape hardware functions from the appropriate NCS automated library control system e Coordinating requests among multiple Sun StorageTek automated libraries SMC resides on every MSP host that accesses Sun StorageTek real and virtual tape hardware SMC may communicate with any number of Sun StorageTek automated libraries using cross address space facilities to communicate with HSC running on the same host and TCP IP to communicate with HSC systems executing on other hosts Note For the purposes of this publication HSC refers to the MSP implementation of the Sun StorageTek Host Software Component The VM implementation of HSC is not supported by SMC Chapter 1 Introduction 1 312614001 Rev B Terminology SMC introduces three important terms
225. tes the model type See Table 12 on page 215 for a list of valid model type values OFF specifies that the model type for the device numbers specified by the ADDRess parameter should be determined from the device UCB or for a device which was previously set to MODEL IGNORE that the MODEL information from the library server should be restored Example In the following example model 9840C devices outside of an NCS library are defined UNITATTR ADDR 2918 2911 MODEL T9848C Chapter 6 Commands and Control Statements 125 312614001 Rev B USERMsg Command The USERMsg command allows you to specify additional message identifiers for messages to be intercepted and passed to the library subsystem s user exit 01 This command can also be used to list the message identifiers of those messages that have been defined using the USERMsg command Syntax LIst swot S ID msgid Command Name USERMsg initiates the USERMsg command Parameter Descriptions List optionally lists the message identifiers in the customer defined message table This is the default if no parameters are specified ID optionally specifies a message to be added to the customer defined message table This message is passed to any active library subsystem user exit 01 SLSUX01 SCSUX01 IS Note This parameter may only be specified in the SMCPARMS data set msgid indicates the message identifier for the message to be added Example In
226. the LIBrary command Parameter Descriptions List optionally lists the specified library If no library name is specified all libraries are listed NAME specifies the library name to be listed name indicates the library name NAME specifies the library name to be defined or modified name indicates the library name The following rules apply The first character must be an alpha character The last character must be either an alpha character or digit e Any character between the first and last must be either an alpha character digit or hyphen ENAble enables the specified library to be selected for allocation or mount requests DISable disables the specified library The library is not used for any allocation or mount requests LOCSUBsys specifies a local HSC subsystem subsysname indicates the subsystem LOCENAble enables the specified HSC subsystem to be used as a local path to the library LOCDISable disables the specified HSC subsystem LOCDISable can be used to force the SMC to ignore the local subsystem and access the library via a remote server Chapter 6 Commands and Control Statemenis 77 312614001 Rev B List WTORdest optionally specifies the console to which HSC WTOR messages are directed See Managing HSC Mounts from the SMC Client on page 55 for messages that apply Client the remote HSC returns selected WTORs to the SMC client without issuing the WTOR message The SMC client the
227. the current system date and the first date cannot be greater than the second date IS Note A comma or no keyword blank results in the system default date of January 1 1900 1900001 MIXED Specifies to print all report headings and messages in mixed case characters uppercase and lowercase Note A comma or no keyword blank results in headings and messages being printed in uppercase characters zara subsys name Specifies the subsystem name for the Zara tape management system where zara subsys name is the four character name The default subsystem name is ZARA Chapter 8 SMC Tape Management Extract Utility 135 312614001 Rev B Sample JCL The following definitions apply to the JCL used for the SMC Scratch Extract utility DBTMS Input to the Scratch Extract utility in the form of the CA 1 TMS or the CA DYNAM TLMS VMS This DD statement is not required for Zara STDOUT Output messages from the Scratch Extraction utility This DD statement is required DBEXTFIL Output file from the Scratch Extract Utility Ifa DCB LRECL is specified it must specify a 16 byte value If Zara is the tape management system the Zara API module must either reside in the MSP LINKLIST or you must include one of the following JCL statements to access the module STEPLIB DD DISP SHR DSN your zaraapil library DISP SHR DSN your tmsextract library or JOBLIB DD DISP SHR DSN your zaraapil library Figure 10 shows sample JCL used
228. the job User Response If libraries are implied using the MSP SSCVT chain or via the LIBrary command LOCSUBsys parameter ensure that the HSC on the host are active and at the correct level If libraries on another host are defined using the LIBrary command ensure that the HSC on the remote host defined by the SERVer command is active and at the correct level Also ensure that the HTTP server is active on the remote host SMC subsystem interface error for job JJJJJJJJ reason SSSSSSSS function CCCCCCCC Message Level 4 Explanation SMC processing in an MSP initiator address space attempted to communicate with the SMC subsystem in order to process an allocation or mount request but encountered an error The reason for the failure is SSSSSSSS while the function attempted was CCCCCCCC System Action The SMC will not be able to continue processing the allocation or mount request User Response Investigate the cause of the error by looking for related SMC subsystem or MSP error messages 154 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0052 SMC0053 SMC0054 SMC0052 SMC0054 User exit nn inactivelabended and disabled Message Level 8 Explanation During execution of a job with tape allocation the SMC allocation component invoked the user exit nn from an HSC subsystem However the user exit is currently inactive or has abended and is now disabled for both the SMC and the owning HS
229. the job name in the request STEPname Optionally specifies the step name If the STEPname parameter is not specified the default value is stepname Specifies the name of the step for which the TAPEREQ control statement is processed The TAPEREQ control statement is used only when the specified stepname matches the step name in the request 104 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TAPEREQ PROGram or PGMname Specifies the program name The program name used is the job step program name The default value is program name Specifies the program name for which the TAPEREQ control statement is processed The TAPEREQ control statement is used only when the specified program name matches the program name in the request DATASET or DSN Specifies the data set name The default value is dataset name Specifies the data set name for which the TAPEREQ control statement is processed The TAPEREQ control statement is used only when the specified dataset name matches the data set name in the request IEY Note The name you specify on this parameter might be different from the value coded in the DSN parameter on a DD statement For example The name you specify on this parameter might be different from the value coded in the DSN parameter on a DD statement For example DSN amp amp ABC may be coded on a DD statement if a data set is temporary However the actual data set name is not
230. the library then the library will be considered the owner if scratch volumes are not found in any other library IS Note Only a single version of an allocation user exit is executed regardless of the number of libraries defined Therefore user exit return codes such as USE LIBRARY DRIVES USE VIRTUAL DRIVES etc are not used to determine a request owner nor does the user exit return code of USE NONLIBRARY DRIVES result in the selection of a different library The preferred way to select a library owner from among multiple libraries is through esoteric substitution on TAPEREQ Alternatively user exits can be used to specify a library name or esoteric Chapter 2 SMC and Sun StorageTek Library Management 19 312614001 Rev B Chapter 3 Starting the SMC Overview The SMC manages all interfaces with MSP for allocation and message handling and therefore must be started as a task on every MSP host where tape processing occurs The SMC calls on HSC for volume and drive information Therefore HSC can be active on the same host or HSC can be active on another host with the Sun StorageTek HTTP server Unlike previous releases HSC 6 1 can be initialized before the SMC without producing error messages However an SMC subsystem must be active to influence tape allocations and intercept MSP messages SMC startup requires the following tasks e creating the SMC START procedure e executing the SMC START procedur
231. the operator console refers to the MSP client system console operating system OS Software that controls the execution of programs that facilitate overall system operation P Pass thru Port PTP A mechanism that allows a cartridge to be passed from one LSM to another in a multiple LSM ACS physical port The communications hardware required to support a server client link physical volume A physically bound unit of data file media See cartridge pipe VM Inter User Communications Vehicle UCV path PowderHorn 9310 The high performance version of the standard LSM pre configured package A storage server package including all hardware software and configuration parameter settings delivered by the vendor privilege class Applicable to both the VM and CLS environments userids are granted access to either system based on assigned rights to execute various commands product change request PCR A request for enhancement to a product Normally this request comes from a client but may come from Sun StorageTek program temporary fix PTF A software release designed to remedy one or a series of defects program update tape PUT One or more tapes containing updates to or new versions of the SMC system software protocol A formal description of message formats and the rules two or more machines must follow to exchange these messages R recovery Automatic or manual pr
232. tination or origination of data allocation The assignment of resources to a specific task asynchronous transmission Character oriented data transmission as distinct from IBM s block mode transmission Automated Cartridge System ACS A fully automated cartridge storage and retrieval library subsystem consisting of one or more Library Storage Modules LSMs connected by pass thru ports Automated Cartridge System Library Software ACSLS The library control software which runs in the UNIX based Library Control System automatic mode A relationship between an LSM and all attached hosts LSMs operating in automatic mode handle cartridges without operator intervention This is the normal operating mode of an LSM that has been modified online The opposite situation is manual mode See manual mode bar code A code consisting of a series of bars of varying widths This code appears on the external label attached to the spine of a cartridge and is equivalent to the volume serial number volser This code is read by the robot s machine vision system BISYNC Binary Synchronous Communications An early low level protocol developed by IBM and used to transmit data on a synchronous communications link It is a form of data transmission in which synchronization of characters is controlled by timing signals generated at the sending and receiving stations C CAPid A CAPid uniquely defines the loc
233. tine which routes the request to the HSC executing on MSPB using MSP EX facilities for cross address space communication Any configuration that includes a remote library requires the Sun StorageTek HTTP server and LIBrary and SERVer commands The following example illustrates the LIBrary and SERVer commands for the SMC on MSPA LIBRARY NAME REMLIB SERVER NAME REMPATH LIBRARY REMLIB HOST MSPB Note See Client Server Drive Address Mapping on page 18 for additional requirements if different drive addresses are defined between client and server hosts 10 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Scenario 3 SMC and a Single HSC Library Configuration with One Local and One Remote alternate Path When a single library hardware configuration is shared between multiple MSP hosts you can define multiple paths to the library as shown in the following figure TCP IP stack SMC Address space C l ient Initiator Address space HSC Address space L Local Library HSC Address space CGI Routines Server SMC Address space TCP IP stack StorageTek HTTP SERVER Figure 3 NCS Local Library with Alternate Path Configuration Chapter 2 SMC and Sun StorageTek Library Management 11 312614001 Rev B The following example illustrates the LIBrary and SERVer commands for the SMC on MSPA LIBRARY NAME SHRLIB LOCSUBSYS HSC
234. tive Library Subsystem 0 0 ccc cece een nen 128 Automating Mount Requests for Inactive Libraries 0 0 0 c eee eee eee 128 Lost MSP Mount Requests for Active Libraries 2 0 0 cece eee eee 128 Chapter 8 SMC Tape Management Extract Utility ooo oooooommo 129 OV EIVICW se cece asain Yet ie thie Sele eee inte ahaa oles eee iat ne Ata nite Gia ne ai gatas 129 SMC Utility Return Codes and Messages 00 ccc cette nents 129 Tape Management Extract Utility 0 ect eetnee enn ees 130 Running the SMC Scratch Extract Utility 0 2 0 0k en eee 131 Using SMCUDBX with CA 1 Release 4 9 or Below 2 0 0 cece 133 Using SMCUDBX with CA DYNAM TLMS Release 5 3 or Below 133 Specifying Values for the PARM Parameter 0 0 0 cece cece een eens 134 Parameter Descriptions mes jews SR baw eee he hw Dns Cn wa 134 sample ICE eki a aioe day otha Mth A a ld 136 CA E E O 137 Chapter 9 SMC Messages seis rra ARA 139 OVA A iba 139 Message Format unen ra A A ti eae 139 Contents vii 312614001 Rev B Message Descriptions sastran Si WS aa RS a WR dE Se eh SR Sa RH See ad ns 140 Variable Definitions c bese ang hese bd tee A A ee we Re tee 140 SMC System Message Listing 0 ccc ee een e nent nen n ees 141 SMC Utility Message Listing tan li db dt 193 Chapter 10 Sun StorageTek HTTP Server Messages 00 cece ence eee eeeee 195 Overview A A a eG
235. tor command HSC VOLATTR control statement The following table describes valid MODel types IEY Notes The SL8500 library supports only model types associated with T9840 and T9940 series transports e You can specify multiple values for this parameter separate each value with a comma Table 12 Model Types Model Type Description 4480 Indicates a 4480 18 track transport 4490 Indicates a 4490 36 track Silverton transport 9490 Indicates a 9490 36 track Timberline transport 9490EE Indicates a 9490EE 36 track Timberline EE transport SD3 Indicates an SD 3 RedWood transport 9840 Indicates a 3490E image T9840A transport 984035 Indicates a 3590 image T9840A transport T9840B Indicates a 3490E image T9840B transport T9840B35 Indicates a 3590 image T9840B transport T9840C Indicates a 3490E image T9840C transport T9840C35 Indicates a 3590 image T9840C transport T9840D Indicates a non encryption enabled 3490E image T9840D transport T9840D35 Indicates a non encryption enabled 3590 image T9840D transport T9840DE Indicates an encryption enabled 3490E image T9840D transport T9840DES5 Indicates an encryption enabled 3590 image T9840D transport T9940A Indicates a 3490E image T9940A transport Appendix B MEDia RECtech and MODel Values 215 312614001 Rev B Table 12 Model Types Continued Model Type Description T9940A35 Indi
236. ts as the drive host master For example MSP1 AA0 AAF Once the drive host master is specified in the HSC CDS the addresses associated with that host master AA0 AAF are used by both MSP1 and MSP2 when communicating with the SMC If desired you can add a dummy host ID to be the HSC DRVHOST and use nonexistent drive addresses to map to client addresses For example use the HSC SET NEWHOST utility to define hostname DRVDUMMY and define the device range as 000 00F Refer to the HSC System Programmer 5 Guide for more information about the HSC SET DRVHOST utility and HSC SET NEWHOST utility 2 Use the SMC DRIVemap operator command on clients MSP2 and MSP3 to map drive addresses BAO BAF and CAO CAF to the server addresses AAO AAF See page 73 for more information about the SMC DRIVemap command 18 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC Drive Type Information Synchronization The SMC acquires drive type information from the HSC library control system For HSC subsystems drive configuration changes are automatically recognized by the SMC for both local and remote systems The SMC UNITAttr command can be used to define device types for nonlibrary drives and to set MODEL IGNORE for device addresses not available for the host SMC Library Subsystem Selection When the SMC intercepts a specific or scratch allocation request it selects an owning library to service the request The followin
237. umentation for more information about virtual volumes Exclusion Level 3 The SMC TAPEREQ definitions can explicitly specify the media desired for the allocation request or media can be derived from the TAPEREQ RECTECH Drives that do not provide the requested media support are excluded at this level For example DD1 DD UNIT CART DISP NEW KEEP DSN SYS4 VIRT DATA No SMC TAPEREQ has been defined Assume the User Exit 02 return code requested virtual media UX02VIRT The User Exit 02 media selected for this request is virtual Only virtual drives remain in consideration for this allocation The next example shows how TAPEREQ can override User Exit 02 return codes For example DD1 DD UNIT CART DISP NEW KEEP DSN SYS4 TR4 DATA An SMC TAPEREQ has been defined TAPEREQ DSN SYS4 TR4 MEDIA DD3A RECT DD3 Assume User Exit 02 return code requested virtual media UX02 VIRT If no TAPEREQ definition applies to this allocation request User Exit 02 return code UX02VIRT can explicitly request virtual media Nonvirtual drives are excluded at this level However the TAPEREQ media definition overrides the user exit return code and the media selected for this request is helical Only helical drives remain in consideration for this allocation Messages SMC0045 and SMC0046 are issued indicating that the user exit request for virtual volumes was not honored 38 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B
238. uperset of an existing prefix beginning with the same character Chapter 9 SMC Messages 161 312614001 Rev B SMC0082 SMC0085 SMC0082 Command prefix already set Message Level 0 Explanation The command prefix can be specified only once while the SMC is initializing and cannot be changed during execution System Action Processing continues The command is ignored User Response To change the command prefix update the CMDDEF statement in the SMCPARMS data set and recycle the SMC SMC0084 MMM DD YYYY HH MM SS SSSS active on hostid HHHH Message Level 4 Explanation The date MMM DD YYYY time HH MM SS subsystem name SSSS and MSP hostid HHHH are displayed once a day at midnight and during SMC initialization System Action None User Response None SMC0085 SMCBPREI IEFSSI failed RC XX RS XXXX Message Level 0 Explanation The SMC subsystem pre initialization routine SMCBPREI encountered an error System Action Ifthe Return Code RC is 4 or less the SMC subsystem was defined Ifthe Return Code RC is 8 or higher the SMC subsystem was not defined User Response Investigate the Return Code RC and Reason RS and take the necessary action The return code and reason are documented in the Fujitsu manual Task Management Macro Instructions Reference Manual 162 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B SMC0086 SMC0087 SMC0088 SMC0086 SMC0088 SMC SUBSYS
239. uration and Administration Guide 312614001 Rev B Deferring Mounts The SMC can also set the deferred mount status if the installation chooses to defer the mount of library volumes The SMC ALLOCDef command DEFER parameter can set defaults for an installation Defer ON The volume mount is deferred until the data set is opened This is the default Defer OFF The volume mount is deferred only if the user s JCL requests it For optimal performance it is recommended that you set Defer ON IS Note Virtual mounts are always deferred Library Subsystem Selection In order to support the execution of SMC on a different host from the library subsystem all allocation and message processing user exits are now managed and invoked by the SMC It is recommended that you carefully review the contents of your existing user exits to determine the most effective method to direct allocations to the correct library Specifically the use of the user exit return code use nonlibrary drives to direct allocation to another library subsystem is no longer supported It is recommended that you use TAPEREQ or user exit esoterics to direct allocations to the appropriate library subsystem An alternative method to select a library subsystem is to alter your scratch or specific allocation user exit to use the new HSC format and explicitly select a LIBRARY name to direct a request See SMC Library Subsystem Selection on page 19 for information
240. ust be defined to SMC using the SMC LIBrary command And because a remote library can be shared by multiple instances of HSC ruming on different remote hosts the path to each remote host is defined to SMC using the SMC SERVer command See Chapter 6 Commands and Control Statements for more information about these commands Client Communication Monitor Subtask This feature directs SMC to periodically validate whether an active communication path is available for all non disabled libraries It does not require SMC to process an allocation or mount event Validation automatically occurs at a specified monitor scan interval This interval is specified using the MONItor parameter on the TCPip command By default the communication monitor subtask is automatically enabled at SMC startup To disable this feature issue the following SMC command TCPIP MONITOR OFF Chapter 2 SMC and Sun StorageTek Library Management 5 312614001 Rev B One communication monitor subtask services all libraries defined to SMC and the TCPip MONitor and PREFprimary parameters apply to all non disabled libraries If an active communication path is not available for a library the monitor subtask attempts to communicate with each defined communication path beginning with the local path if available followed by the primary server path and each secondary server path in turn If the monitor subtask re establishes communication with the library all pending mounts are
241. value must be one to eight characters in length The first character must be an alpha character The last character must be either an alpha character or digit Any character between the first and last must be either an alpha character digit or hyphen IS Note If you are using the Sun StorageTek HTTP server there can be multiple NAMEd paths to a single LIBRary configuration See Chapter 2 SMC and Sun StorageTek Library Management for more information HOst optionally specifies the host on which the subsystem resides hostname indicates the host name The following arpanet rules apply The first character must be an alpha character The last character must be either an alpha character or digit Any character between the first and last must be either an alpha character digit hyphen or period e The host name can be a maximum of 128 characters IPaddress optionally specifies the subsystem IP address ipaddress indicates the IP address IS Note IPaddress and HOst are mutually exclusive POrt optionally specifies the server port nann indicates the server port The default is 80 98 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B TAPEREQ WAit specifies the maximum wait time for any single request made over the network nnnn indicates the wait time in seconds The default is 60 Note The default for a mount or dismount request is 10 minutes 600 seconds or more if
242. varied online but is connected to the standby LMU of a dual LMU ACS standby LMU The redundant LMU in a dual LMU configuration that is ready to take over in case of a Master LMU failure or when the operator issues a SWITCH command station A hardware path between the host computer and an LMU over which the HSC and LMU send control information Storage Management Component SMC Software interface between IBM s OS 390 and z OS operating systems and Sun StorageTek real and virtual tape hardware SMC performs the allocation processing and message handling for the NCS solution storage server A set of hardware and software products designed to enable heterogeneous computer systems to use automated tape cartridge library services switchover The assumption of master LMU function by the standby LMU synchronous See BISYNC synchronous LAN Local area network built on synchronous communications Systems Network Architecture SNA A description of the logical structure formats protocols and operational sequences for transmitting information units through and controlling the configuration and operation of networks T tape drive A tape processing device consisting of up to four transports in a cabinet A drive can refer to an individual transport tape library management system TLMS TLMS as used in this document refers to any tape library management system not to CA 1 TCP IP Transmiss
243. vel 8 Exclusion level 3 restricts the list of eligible drives to those compatible with the TAPEREQ requested media Exclusion level 5 restricts the list of eligible drives to those compatible with the scratch media in the requested subpool Exclusion level 8 may further restrict the devices for the request based on the TAPEREQ data class recording technique The SMC TAPEREQ definitions can explicitly specify a recording technique for the allocation request This criterion is the last to be applied to the drives that are eligible for the allocation Any drive that does not provide the requested recording technique is excluded from consideration for the allocation For example DD1 DD UNIT CART DISP NEW KEEP DSN SYS4 TR4 DATA Assume an SMC TAPEREQ has been defined TAPEREQ DSN SYS4 TR4 RECT STKIRB Previous exclusion levels restricted the list of devices to all T9840 models In this example the TAPEREQ recording technique of STK1RB leaves only T9840B devices in consideration for this allocation Chapter 4 SMC Allocation in a JES Environment 43 312614001 Rev B Affinity Separation Explicit unit affinity is an MSP facility that allows volumes associated with two separate JCL DD statements or allocation requests to be mounted serially on the same drive A request for all generations of a GDG group GDG ALL chain can be considered as a GDGALL affinity The SMC makes no distinction between these two types of affinity When
244. vice types has been applied to all NCS products including SMC KEYWORD KKKKKKKK of the CCCCCCCC command is required Message Level 0 Explanation The command CCCCCCCC was issued without the required keyword KKKKKKKK System Action The command is not processed User Response Re issue the command with the required keyword Chapter 9 SMC Messages 167 312614001 Rev B SMC0106 SMC0108 SMC0106 SMC0107 SMC0108 Mount of HSC volser VVVVVV in LIBRARY LLLLLLLL on device XXXX not in library Message Level 0 Explanation An SMC MOUNTDEF VOLWATCH option is ON The SMC has detected that a volume resident in library LLLLLLLL is being requested to be mounted on a drive outside all libraries System Action None User Response Cancel the job requesting the mount or eject the volume to satisfy the mount request Swap VVVVVV from XXXX1 to XXXX2 Message Level 4 Explanation The SMC has intercepted DDR swap processing XXXX2 is either the original device selected to swap to or a device selected by SMC that more closely matches the device characteristics of XXXX7 System Action DDR swap processing continues User Response None No compatible drive found for SWAP processing Message Level 0 Explanation The SMC has intercepted DDR swap processing The original device chosen to swap to is not compatible with the swap from device and the SMC could not locate a compatible alternate device System Action DDR swap pr
245. y specifies whether mount errors generated by the HSC are echoed directly to the console for the SMC client ON mount errors generated by the HSC are echoed directly to the console for the SMC client IS Note This parameter is valid for both local and remote servers OFF mount errors generated by the HSC are not echoed to the console for the SMC client This is the default SMCWtorpfx optionally specifies whether the SMC0137 prefix is displayed for HSC WTOR messages generated by WTORDEST CLIENT on the LIBRARY command ON The SMC0137 prefix is displayed for HSC WTOR messages This is the default OFF The SMC0137 prefix is not displayed for HSC WTOR messages 88 SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B MSGJob Example In the following example the MSGDef command specifies that SMC messages are displayed in mixed case The command also specifies that only error and warning messages from the SMC subsystem are displayed MSGD CASE MIXED LVL 4 Chapter 6 Commands and Control Statemenis 89 312614001 Rev B MSGJob MSGJob Command The SMC MSGJob command allows an override of the default message level by job name step name and PROC step Syntax List soo pfs OFF a gt lt JOBname jobname wut PROCstep procstep Command Name MSGJob initiates the MSGJob command Parameter Descriptions LIst optionally lists current default SMC message
246. ystem Conventions Used in this Guide Product Names HSC refers to the MSP implementation of the Sun StorageTek Host Software Component Typographic In the JCL examples in this guide some fields appear in lower case You must update these fields to match your installation requirements Symbols The following symbols are used to highlight text in this guide Note Information that may be of special interest to you Notes are also used to point out exceptions to rules or procedures Warning Information necessary to keep you from damaging your hardware or software f Caution Information necessary to keep you from corrupting your data xviii SMC 6 1 MSP Configuration and Administration Guide 312614001 Rev B Syntax Flow Diagrams Syntax flow diagramming conventions include the following Flow Lines Syntax diagrams consist of a horizontal base line horizontal and vertical branch lines and the text for a command control statement macro or utility Diagrams are read left to right and top to bottom Arrows indicate flow and direction e astatement begins with gt gt e astatement ends with e diagrams continuing to the next line begin with e fragments begin and end with Single Required Choice Branch lines without repeat arrows indicate that a single choice must be made If one of the items from which a choice is being made is positioned on the base line of the diagram a single choice is required

(MSP) Configuration and Administration Guide

Contents

Download Pdf Manuals

Related Search

Related Contents