System Messages — VMS 5.5-2H4
Additional information available:
Errors
Additional information available:
AAAABENDABENDDABENDTABFNAMABKEYWABKW
ABNORMAL_EXITABORTABORTABORTABORTABORT
ABORTCABORTEDABPRIKWABSENTABSTIMREQABSYMD
ABVERBACCACCCIRACCDISERRACCERRACCESSFAIL
ACCLINACCONFLICTACCONFLICTACCOUNTACCQUOTA
ACCVIOACCVIOACCWAITACCWAITDONEAC_LSS_MP
ACPINITACPMBFAILACPNAMEACPNOCTLACPNOKSTK
ACPNOVIRTACPRECURSACPSHOACPTIMEACPUNSTAK
ACPVAFAILACPVAFULACSACSIGNACTACTIVEACTIVEBCB
ACVINORCVADDERRADDFILADDFILEADDMSGADDQUOTA
ADJSCROLLREGADRLSTSYNXADRWRTDATADVADVCOMP
ADVADVERSENDADVALLOCADVBADFORMATADVBTIMADVCACHEINIT
ADVCANTIMADVCHUIDADVCLILOADFAILADVDEASGN
ADVDEFCONNADVDEFLOADADVDEFOPENADVDEFPARSE
ADVDEVCHECKADVDUMPFAILADVETHERMEMADVMBX
ADVNICKUIDADVPRIVADVRANDOMADVRECBUF
ADVRECREATEADVREREADADVSETIMRADVSOLCOMP
ADVTIMERRADVUIDNICKADVWRITETHERAGAIN
AIDALCPHDALCSMBCLRALERTEDALERT_NESTING
ALIALIGNDISKALIGNXCEEDALLOCALLOCCLRALLOCEXT
ALLOCFAILALLOCFAILALLOCMEMALLOCMEMALLOCSET
ALNALPBFOVFALQALRCURTIDALREDEFALTIHDBAD
AMBCMDAMBDATTIMAMBIGAMBIGNAMEAMBIGSYMUSED
AMBKEYAMBSYMDEFANIAOPAPPENDEDB
APTREFHIGHAPTWRTERRAQBTIMEARBTOOBIG
ARCHIVEDSBARCHIVEMOVEARCHIVENEWARCNOTDISK
ARCOPENFAILARGMISMATCHARGREQARGTOOLONG
ARTRESASCEFCFERASCTOOLONGASGNMNTSYN
ASGNQUEASSIGNASSIGNASSIGNFAILASTFLTASTRPDFER
ASUSPECTASYNCACTIVEASYNCWRTERATLINEATPC
ATPROCLINEATRATTACHEDATTCONSTOATTREQREF
ATWAUTOMEMCOPYAUTOMEMERGEAUTOMEMSUCC
AUTONOTSTARTAUTOSYNCBACKLINKBACKUPERRBADACC
BADACPBADACTRLBADALORQSZBADARGSBADASSIGNBADATTRIB
BADBITMAPBADBLKBADBLKSIZEBADBLOADR
BADBLOCKBADBLOCKSBADBLOSIZBADBOOTCBBADBUFADR
BADBUFTYPBADBUFWRITEBADBUGBADBYTEBADCACHE
BADCASEBADCASELIMITBADCASERANGEBADCCCBADCCC
BADCHARBADCHECKSUMBADCHKSUMBADCHKSUM
BADCONDEVBADCOPIESBADCSPBADCTLMSK
BADDALRQSZBADDATABADDATCHKBADDATDAT
BADDATLENBADDELETEBADDELIMBADDENSBADDEV
BADDIRBADDIRBADDIRENTBADDISDEVBADDISDIR
BADDSTBADDSTMAPBADDSTVBNBADECOBADEFBLK
BADENTRYBADESCAPEBADEVTYPBADEVVALBADEXCLBADEXCLNAM
BADEXEBADEXECLOBADEXERABBADEXITIFBADFID
BADFIELDBADFILEBADFILEHDRBADFILENAMEBADFILENAME
BADFILEVERBADFIRSTLINEBAD_FIXUPVECBADFLAG
BADFORKIPLBADFORMBADFORMBADFORMATBADFRMT
BADFUNCBADGETDIRBADGETJPIBADGSDBADHDRBADHDR
BADHEADERBADHIBLKBADHOMBLKBADIDENTBADIF
BADIMGHDRBADIMGHDRBADINDEXBADINITSZBADIONAME
BADIRECTORYBADISDBADITMPROCBADJOBIDBADJOBNAME
BADJOUCHARBADJOUCOMBADJOUCPOSBADJOUEDIT
BADJOUEIGHTBADJOUFILEBADJOUINITBADJOUINPUT
BADJOUKEYBADJOULINEBADJOULPOSBADJOUPAGE
BADJOUSECBADJOUSTRBADJOUTERMBADJOUWIDTH
BADJRNLBAD_KEYBADKEYBADKEYBADKEYBADLABELQ
BADLCKWSLEBADLEXARGBADLEXFORMBADLOGIC
BADLOGICBADLOGICPCBADLOGVERBADLONGBAD_LRL
BADMARGINSBADMATCHBADMCKCODBADMODE
BADMODNAMBADMOPFCTBADMOPPGMBADMOPPROC
BADMOPSIDBADMOPVERBADMSGBADMSGBAD_NAME
BADNODFORMBADOFFSETBADOPCODEBADOPEN
BAD_ORDERBADOUTBANDBADOVRBADPADBADPAGFILA
BADPAGFILDBADPAGTYPEBADPARAMBADPARAM
BADPARAMBADPARAMBADPARAMBADPARAM
BADPARSETBLBADPATBADPKTBADPNAMEBADPRO
BADPROCBADPROCNAMEBADPROGBADPROGDELETEBADPROMPTLEN
BADPRTYBADPSCBADQFILEBADQHDRBADQNAMEBADQUAL
BADQUEUEHDRBADRANGEBADRANGEBADRCTBADREADBADREFCNT
BADREPLYBADREPLYBADREQUESTBADRETURNBADRSEIPL
BADRVNWCBBADSBMBLKBADSECTIONBADSEQNUM
BADSETAFFBADSETCNTBAD_SIZEBADSORTBADSPC
BADSPECBADSPLINDEXBADSPLNAMEBAD_SRLBADSTA
BADSTACKBADSTACKBADSTARTBADSTATUSBADSTRCNT
BADSTRLVLBADSTRLVLBADSTRUCTBADSUBFCN
BADSWPVBNBADSYMBADSYMTABBADTAGVAL
BADTIMEBADTYPEBADTYPEBAD_TYPEBADUICBADUSERDESC
BADUSRBADUSRDATBADUSRLENBADVALUEBADVALUE
BADVALUEBADVALUEBADVALUEBADVALUEBADVECBADVOL1BADVOLACC
BADVOLLBLBADWCBPTBADWIDTHCHANGEBADWINDADJUST
BADWINDLENBADWORDBADZONEBASDUERRSBASESYM
BASSHRBELBATCHNOOPRBATIS_OFFBATIS_ONBATSTIPRO
BBFOVFBBFWRTBBLHEADERBDPPURGERRBEGIN
BEGINDBEGINTBEGNLENDBEGOFBUFBEGOFFILEBEGRANBES
BINARYOPERBINCHKSUMBINRECFMTBITMAPERR
BITMAPINVBKSBKZBLK0BADBLKDIRSYNX
BLKEXPNABSBLKZEROBLKZEROBLNBLOCKCHECK
BLOCKCHECK0BLOCKCNTERRBLOCKCRCBLOCKLOST
BLPRSPBMSBOFBOTLINETRUNCBRDCSTBRDESTRANG
BRDMSGLOSTBREAKBRKNLIBBRTOOFARBUFBLKREQ
BUFBYTALIBUFFEROVFBUFFEROVFBUFFERSLOST
BUFNOTALIGNBUFOVFBUFOVFLBUFOVRBUFTOOSMALL
BUGBUGCHECKBUGCHECKBUG_DAPBUG_DDIBUSYBUSY
BVNCACLSCAFINVGROUPCAFNEITHERCAFNOTCLU
CAFOLDGROUPCAFOLDPASSCAFPASSLENCAFREBOOT
CALLOVERCALLUSERFAILCANCELCANCELEDCANCELQUIT
CANNOTUNSELCANTATTACHCANTBALCANTCOPYSTR
CANTEXPREGCANTLOCKCANTLOCMACCANTSPAWN
CAPTINQCAPTINTCAPTIVECAPTIVECARDSCASETOOLARGE
CBTCCFCCRCDACEBREFNEGCEM
CENTRLCHAINWCHANCHANGE_INVCHANINTLK
CHGCHKCHKALTHOMECHKPRIHOMECHKSCB
CHMONISCHMVECCHNCINBADCINREJCIPORTCJFERR
CJLCLASDISABCLASMISSCLASNPCLASUNKCLIERRCLIFAIL
CLIFRCEXTCLIMISMATCHCLIPBOARDFAILCLIPBOARDLOCKED
CLIPBOARDNODATACLIPBOARDZEROCLIPROTCLIQUALCLISYMTBL
CLIWARNMSGCLOSEDELCLOSEERRCLOSEERRCLOSEERRCLOSEFILE
CLOSEFOREIGNCLOSEINCLOSEINCLOSEINCLOSEJOBCLOSEMON
CLOSEOUTCLOSEOUTCLOSEOUTCLREFCFERCLSERRCLSTBLERR
CLUBELBASCLUEXITCLUGDIFFCLULISTCLUPDIFFCLUSTER
CLUSTERCMDCANCMDERRCMDERRORCMDINPUTCMDLIN
CMDNOTFNDCMDNOTVLDCMDOBSCMDOBSCMDSYNTAX
CMDSYNTAXCMDTOOLONGCMDTOOLONGCMODSUPR
CMODUSERCMPOUTF11CNFCNFOVRCNFQUAVAL
CNSCNTERRCNTRLYCNTRSOBSCNVRTINGCNXMGRERR
COBCODCOFCOICOLLERRCOMBCLUCOMCOD
COMFAIL_COMFILCOMFILEMTYCOMMACOMMERROR
COMM_FAILCOMMHARDCOMOREXECOMPARED
COMPATCOMPBEGINCOMPENDCOMPFAILCOMPILEDCOMPILEFAIL
COMPLETECOMPLXCOMPSYNCCOMREMJBCCOMSTACONABORT
CONATMPTCONCATCONCEALEDCONERRCONFAILCONFATTR
CONFBASADRCONFCONCONFDEFREQCONFDELCONFDIS
CONFFACCONFIXMEMCONFLICTCONFLICTCONFMEMCONFNEG
CONFNOCONCONFNODISCONFNONNEGCONFNOPARM
CONFNOQUALCONFOUTPUTSCONFPARMCONFQUALCONFQUAL
CONFQUALCONFQUALCONFQUAVALCONFROUTIMGCONLOST
CONNECCONNECFAILCONNECTEDCONSEQERR
CONSTRTOOLARGECONTIMEOUTCONTINUECONTINUED
CONTRACTCONTRADEFCONTROLCCONTROLCCONTROLCCONTROLC
CONTROLOCONTROLOCONTROLYCONVERT_STALLCOOCOPIED
COPIEDBCOPIEDCCOPIEDRCOPMSGCOPY_LOGCOPY_LOG_ENDED
COPY_LOG_LINECORCORRUPTEMBCPUCEASED
CPUEXITCPUNOTACTCPUNOTVLDCPUSANITY
CPUSPINWAITCPUSTARTDCPUSTARTIPCPUSTOPPING
CRCCRCLSCRECREA_ERRCREATDIRCREATECREATED
CREATEDCREATEDCREATEDCREATED_SOMECREATEDSTM
CREATEFAILCREATELOSTCREATEVIRTCREDIR
CREDIRERRCREERRCREJOBCREJOBCRENEWFOLD
CREPARFILCREPRCCREPRCFALCREPRCSTOPCREPRIJOB
CREQUECRE_STMCRFCRFERRCRMPCRMPSCCRP
CTRLCEXITCTRLCHARCTRLCJOUCTRLERRCTRLERRCTRLY
CTXSTSERRCURCUREXECCVTERRCVTERRCVTUNGRANT
CWFDACDANDATACHECKDATADEVERR
DATAERDATALOSTDATALSTSYNDATAOVERUNDATAOVFL
DATATRUNCDATFILCREDATMISMCHDATTOOLNG
DBCORRUPTDBGTFRDBLERRDCVNOTFNDDDIFIN
DDIFOUTDEADLOCKDEBUGDEBUGDECNETDECOVFDECOVF
DECPTREFDECTSTFAIDEFAULTEDDEFAULTLENDEFCHARSTIC
DEFER_Q_FULLDEFERRDEFFORMDEFFORUSEDEFINEKEY
DEFKEYDEFOVFDEFPWDDELDELACCESSDELCONPFN
DELDATERRDELETEDELETEDELETEDDELETEDDELETED
DELETEFAILDELETESWLDELEXIGBLDELGBLSEC
DELGBLWCBDELHEADERDELHEADER_BUSYDELKEY
DELKEYERRDELLINKDELPORTDELSERVICEDELSYM
DELTIMREQDELTVADELVERDELWSLEXDENOSUDENSITY
DEQSUBLCKSDESSTROVFDESTPDEUNUSDEV
DEVACTIVEDEVALLOCDEVALLOCDEVALRALLOCDEVALSPL
DEVASSIGNDEVCLASSDEVCMDERRDEVCOUNTDEVFOREIGN
DEVICEDEVICEFULLDEVICESDEVINACTDEVMNTDEVMOUNT
DEVNOTALLOCDEVNOTBLKDEVNOTERMDEVNOTEXIST
DEVNOTFORDEVNOTFORDEVNOTKNWNDEVNOTKNWN
DEVNOTKNWNDEVNOTMBXDEVNOTMOUNTDEVNOTSPL
DEVNOTSUITDEVOFFLINEDEVOFFLINEDEVOFFLINX
DEVONLINEDEVONLYDEVQUALSDEVRCTDEVREQERR
DEVSELREQDEVSPECDEVWRTLCKDFLDGQINCOMP
DIAGNOSTICDIAGPACKDIALFAIDIALINNOTDIFACCTSDIFCHARS
DIFLWDSDIFSTRINGSDIFTIMESDIFTYPDIFVALDIR
DIRALLOCDIRECTDIRE_ERRORDIRENTRYDIRFULLDIRNAME
DIRNOTCREDIRNOTEMPTYDIRSYNXDISCONDISCONNECT
DISCONNECTEDDISKCLASSDISKFRAGDISKSDISMALDISMOUNTD
DISMPARTDISPCHARSTICDISPERRDISPFILEDISPFORMDISPJOB
DISPLAY_SHORTDISPQUEDISREQDIVBY_ZERDIVBYZERO
DIVBYZERODIVZERODNADNFDNRDNS
DOESNTFITDONEMSGDOS11_BADLABELDOS11_BLOCKSIZE
DOS11_IOERRORDOS11_POSITIONDOUBLDALOCDOUBLDEALO
DPEDQCLUSDRIVENAMDRIVERNOTSHUTDRVERRDRVRSTRT
DSAQUOTADTPDTRBADMAILDTSBADMAILDUALLOC
DUMPEMPTYDUMPERRORSDUMPINCOMPLDUP
DUPDUPBLKNUMDUPBUFNAMEDUPCHARNAME
DUPCHARNUMDUPCOMFILDUPDEFDUPDEVSPC
DUPDSKQUOTADUPFILENAMEDUPFORMDUPFORMNAME
DUPGLOBALDUPIDENTDUPINVALIDDUPKEYDUPKEY
DUPKEYMAPDUPKEYMAPLISTDUPLABELDUPLNAMDUPMOD
DUPMODULEDUPMODULEDUPMSGDUP_OUTPUT
DUPPLACEDUPPREFIXDUPPROMPTDUPQUALDUPRVN
DUPSYMDUPSYMDUPSYNTAXDUPTYPEDUPUNITDUPVALUE
DUPVOLNAMDVIDVNDX1DX2ECONOTSET
ECOSETEDITPROCEDITSCLSHEDOUTSEQEF_ALRFREEF_ALRRES
EFDEF_RESSYSELDELEALREXIELETOOLONEMPTY_CHECK
EMPTYDEFEMPTYFILEEMPTYFILEEMPTYHIST
EMPTYINEMPTYJOBEMPTYKMLISTEMPTYLIBRARYEMPTYLST
EMSKNOTABSENAQUOTAENDENDENDABORTENDDIAGS
ENDEDENDEDDENDEDTENDNOOBJENDOFBUFENDOFFILEENDOFFILE
ENDOFTAPEENDOFVOLUMEENDPRSENDTOPICENDWRNGMAC
ENDWRNGMACENGLUSEDENQENTENTEREDENTERLOST
ENTERRENTFILENTIDMTCHENTIDMTCHBENTIDMTCHO
ENTIDMTCHTENTNFENTNOTFOUENVENV
ENVNOTSETEOFEOFEOFEOFMISMATCH
EOMERROREOMFATALEOMFTLEOMSTKEOMWARNEOTIN
EQV_NOTICEERACTEDERASEBLKSERASEFAILERBOXPROC
ERRAT_LINERRCACHFULERRCREKBDERRCVTFIL
ERRCVTOPNERREXECOMERREXEFILERREXEOPN
ERREXEREAERREXEREPERRFREDYNERRHALT
ERRINPFILERRLINERRORERRORERROR_HALTERRORISUE
ERRORSERROUTOPNERRPARSEERRPHOTRAERRPROMPT
ERRRECFILERRROUCALERRSYMACTIVEERRSYSINFO
ERRTSTMODERRVIRDPYESAESCAPEESL
ESSESTABCONEVENT_OCCURREDEVLEVTSIZEXARANGE
EXASTLMEXBIOLMEXBYTLMEXCCOPEXCEPTIONEXCPSC
EXCPTSTEREXCPUTIMEXDEPTHEXDIOLMEXDISKQUOTA
EXEABOEXECUTEFAILEXECUTINGEXENQLMEXFILLM
EXGBLPAGFILEXHFULEXHNEVCALEXISTENCEEXISTS
EXISTSEXITFAILEXITINGEXITSTATUSEXIT_THREAD
EXLNMQUOTAEXPEXPAGQUOEXPANDPHDEXPCOMPLEX
EXPECTEDEXPGFLQUOTAEXPIREDEXPORTQUOTAEXPOVR32
EXPRCLMEXPREGEXPSHRPATEXPSTKOVREXPSYN
EXPTOOCOMEXPVIREXQUOTAEXTEXTBITEXTCACHIV
EXTENDEXTENDEDEXT_ERREXTN_ERREXTNOTFOUEXTNOTFOUND
EXTQELMEXTRACTEDEXTRAENDMEXTRANEOUSARGS
EXTRAPARMFABFABFACFACOVFLFACTBAD
FACTOOLONGFAILFAILEDFAILFREVMFAILGETVM
FAILGETVMFAILOVERFAILUREFAILURE_STATUSFAIOPEFIL
FAOFAOBUGFAOFAILFAOFAILFATALERRFATALERRFATALERROR
FATALEXCFATALEXCPTFATERRLIBFATERRLIBFATERRLIBFATINTERR
FAUFCPREADERRFCPREPSTNFCPREWNDERR
FCPSPACERRFCPWRITERRFDEXNORCVFDLERROR
FDLPARFDLPARSEFELFEXFFVSDIVERFFVSMLTER
FFVSSBTERFFVVADDERFFVVDIVERFFVVMLTER
FFVVSBTERFIDERRORFIDNOTFNDFIDNUM_ZERO
FIELDLIMFIL11_NORECFILACCERRFILADDEDFILALRACCFILAREDIF
FILCNTNONZFILDISABLFILE_ABSENTFILE_EMPTY
FILE_EXISTSFILEACCFILECONVERTEDFILEGONEFILEIN
FILEIOFILELOCKEDFILEMPTYFILENABLFILENOTFOUND
FILENUMCHKFILEOUTFILEPURGEDFILESEQCHK
FILESTRUCTFILETOOLONGFILLIMFILMODIFDFILNOPOST
FILNOTACCFILNOTCNTGFILNOTDELFILNOTEXP
FILNOTFNDFILNOTPURFILOPEFILPURGED
FILREMOVEDFILREQDFILTOOLONFILTRNERRFINDHOME
FINDIHDFINISHEDFIRSTMODFLAGTRUNCFLGFLK
FLOOVEMATFLOUNDMATFLOVNORCVFLTDIV
FLTDIV_FFLTOVFFLTOVF_FFLTPNTSYNXFLTUNDFLTUND_F
FLUNNORCVFLUSHFNAFNAFNDFNF
FNFFNFFNMFOPFORCEDERRORFORCEDEXIT
FORGETFORM_ABORTFORMATFORMATFORWLOOPFPART_SECTN
FREEBADBUFFREEDISKFREEMEMFREEMEMFREEPAGREF
FREEVMFRERANGEFRESIZEFREWSLXFROMBUILTINFROMLINE
FROMPROCLINEFRZNCTXFSZFTMFULFUNNOTSUP
FUTBAKDATFUTCREDATFUTREVDATFWF
GBCGBLNDFGBLNOTCREGBLONLYGBLPAGSZRO
GBLSECMAPGBLSELOWNERGBLWARNGBLWSLXERR
GENERRGEN_MAXGENMINUS1GENWRNGETCHNGETCHN
GETDVIGETDVIGETERRGETERRGETJPIGETJPIERRGETMEM
GETMSGGETPTIERRGETTIMGETVMGFCGFVSADDER
GFVSDIVERGFVSMLTERGFVSSBTERGFVVADDER
GFVVDIVERGFVVMLTERGFVVSBTERGOSUBMAX
GPGNULPGFLGPTFULLGRANTERRGRANTMSGGSDFULL
GSDTYPGSDTYPGSDTYPHALTHALTEDHANGUPHBREAD
HBWRITEHDRBLKHDRCRCHDRERRSHDRNOTMAPHDRNOTRES
HDRTRUNCHEADCOPIEDHEADER_DELHEADERFULL
HELPHELPERRHELPERRHIBHIBERHIDDENHIGHVER
HISTERRHOMBLKBADHOMBLKCHKHRDFAIIAL
IANIBFIBKIBOICONCLUDATICONPFNDAT
ICPAGELOCICVNOTFNDIDDIDENTIDENT
IDMISMATCHIDMISMATCHIDMISMCHIDOUTRNGIDR
IDXIDXCONCATIDXFILEFULLIDXHDRBAD
IDX_LIMIDXMAPERRIFAIFDIRSYNXIFEXPRNABS
IFFIFIIFLIFLEVLXCEDIFREPAGCNT
IFTIGNCLIFLAGIGNFILIGNOREDIGNORE_DIRE
IGNORE_VERSIGNQUALIIFILCILEILLANSIBS
ILL_ARGILLARGDESCILLASCARGILLBATFNCILLBLKNUM
ILLBRDESTILLCDTSTILLCHRILLCNTRFUNCILLCOMPONENT
ILLCREOPTILLCTLILLDESQUEILLDFLTARGILLEFCILLEGALTYPE
ILLEVTNUMILLEXPRILLFMLCNILLFMLCNTILLFMT
ILLFORMATILLFUNCILLIDXNUMILLIFCONDILLINDXREG
ILLINISTRILLINROUILLIOFUNCILL_KEYILLKEYLVLILLMACARGN
ILLMACNAMILLMASKBITILLMODEILLMODNAM
ILLMTCOPYILLNAMELENILLOPILLOPDEFILLOPDEFVL
ILLOPTILLOUTROUILLPAGCNTILLPATASILLPERNAM
ILLPSCLENILLQUALILLQUALVALILLRECLENILLRECLENILLRECLN2
ILLRECTY2ILLRECTYPILLRECTYPILLREGHEREILLREGNUM
ILLREQUESTILLRQSTILLSAVESETILLSELFILLSEQOP
ILLSERILLSEVERITYILLSHROPRILLSHRXPRILLSTRCLAILLSTROPS
ILLSTRSPEILLSYMLENILLSYMLENILLTIRILLTYPILLVALILLVAL
ILLVALILL_VALUEILLVECILLVECOPILLVPSIMAGEFMTIMAGEFNF
IMAGELENIMAGE_NOT_FOUNDIMGADDEDIMGBASEDIMGDUPINV
IMGFILGONIMGFILSPEIMGHDRIMGINVIMGNAMEIMGNOTFND
IMGRECSIZIMGREMOVEDIMG_SIZIMGTRACEDIMGVEXC
IMXIN_BARRIER_WAITINBUILTININCBADDIRINCCTXTINCDATTIM
INCDELERRINCDELETEINCDEVLISINCDISABLED
INCDSTQUEINCDUMPFORMINCENTERRINCFILATR
INCFILSPEINCFORMPARINCHMKINCKWDCOMINCMEMNAM
INCMVEINCOMPACPINCOMPATINCOMPATINCOMPATINCOMPEXI
INCOMPLINCOMPLETEINCOMPSHRINCONISDINCONQUALS
INCONSDEVINCONSTATEINCONSTATEINCPTREF
INCQUETYPINCQUOTAINCRVNINCSEGTRAINCSETCNT
INCSHAMEMINCVOLLABELINDEXINDEXERRINDEXOVFL
INDEXTYPEIND_OVRINHCHMEINIINIACCINIALRPRO
INIERRINITERRINITERRINITFAILINITPRSINMINOVNORCV
INPBUFOVRINPCONERRINP_FILESINP_FILESINPSTRTRU
INPTOOLONINPUTINPUTINPUT_CANCELEDINPUTERR
INSCLIMEMINSCOLLINSDFAILINSEFINSERTEDINSERTERRINSFAIL
INSFANLINSFARGINSFBUFDPINSFCDTINSFMAPREGINSFMEM
INSFMEMINSFMEMINSFPRMINSFRAMEINSFSPTSINSFVMINSFWSL
INSKIPPEDINSLUNINSNFREPAGINSOPRNDINSQUOCRE
INSRESINSSWPFILINSUFFMEMINSUFPATINSVIRMEM
INSVIRMEMINSVIRMEMINSVIRMEMINSVIRMEM
INSVIRMEMINSVIRMEMINSWAPERRINTDATCOR
INTDELPRCINTDIVINTEGERINTERLOCKINTERNALERROR
INTERRINTHCHARINTINVNODEINTLOGERRINTNODESPACE
INTOVFINTOVFINTPATHSTKOVINTRNLERRINTRNLERR
INTSTKOVINTSTKUNINTTERMININ_USEINVACCINVACCESS
INVACCESSINVACCRECINVADAPINVALIGNINVALQUAL
INVARGINVARGINVARGINVARGINVARGINVARGMAT
INVARGORDINVARRDSCINVATTSIZINVATTSTRINVATTVAL
INVBJLEOFINVBJLSIZINVBJLSTRINVBJLTYPINVBKTINVBLKINVBLK
INVBLKHDRINVBLKSIZEINVBLKTYPINVBLOCK
INVBTIMSPINVBUFDELETEINVBUSNAMINVCALLINVCCFIL
INVCHAINVCHANINVCHANAMINVCHANAMINVCHANUM
INVCHARINVCHARINVCHDABSINVCJFIODINVCLADSC
INVCLADTYINVCLIFLAGINVCLSNMINVCMDINVCMD
INVCMDINVCOLINVCOLARGINVCOMPIDINVCOMPLIST
INVCOMPTYPEINVCONTINVCPUIDINVCTXINVCTXTYP
INVCVTINVDATAINVDATIMINVDATIMINVDEFINVDEFATTINVDEFINE
INVDELIMINVDESCINVDEVINVDEVINVDEVICEINVDEVICEINVDEVTYP
INVDIRINVDIS_IDINVDPTINVDPTINIINVDSTQUEINVDSTREC
INVDSTRECINVDTYDSCINVELEIDINVELENAM
INVELETYPINVETIMSPINVEVEINVEXCEPTNINVEXHLIST
INVEXPINVEXTBACKINVEXTFIDINVEXTHDRINVFAOPARAM
INVFCBDESCINVFCOINVFIDINVFILEXTINVFILSPEINVFILSPE
INVFILSPEINVFILSPEINVFLUSHSPINVFORNAMINVFORNAM
INVFORNUMINVFUNCINVFUNCODINVGBLSELDATA
INVGOSUBINVHEADER_BUSYINVHOMBLKINVIDEINVIFNEST
INVIMGHDRINVINPDMNINVINPFILINVINPUTINVINTSP
INVIOCODEINVITEMINVITEMINVITEMCODEINVITEMNM
INVITMCODINVITMCODINVJOUDATAINVKBD_ID
INVKEYINVKEYINVKEYCHARINVKEYNAMINVKTB_ID
INVLDADRINVLDRESPINVLOCKIDINVLOGINVLOGFILINVLOGFILINVLOGFIL
INVLOGININVMAPINVMAXLENINVMODEINVMSGINVMSGBUF
INVNAMINVNBDSINVNUMBERINVNUMCHIINVNUMSTR
INVOOBINVOPCODEINVOPERINVOPEZONINVOPR
INVOPRNDINVOPTIONINVOPTIONSINVOUTDMNINVOUTSPE
INVOVERQUOTAINVPAGARGINVPARAMINVPARAMINVPARFIL
INVPARLENINVPARMINVPARVALINVPAS_IDINVPASSINVPATH
INVPERMQUOTAINVPGPINVPLACEINVPREFIXINVPRVNAM
INVPTEFMTINVPVAINVPWDINVPWDLENINVPWDLEN
INVQMANMSGINVQUALINVQUAVALINVQUAVAL
INVQUENAMINVQUOINVRANGEINVRANGEINVRECFMT
INVRECORDINVRECSIZINVRECTYPINVREFINVREPTYP
INVREQINVREQCODINVREQPARMINVREQTYP
INVRFAINVRFMINVRFMINVROUTINVROUTINVROWINVRSP
INVRSPINVRSPIDINVSCRPOSINVSECDOMAININVSEMINIINVSEMMAX
INVSHDWMEMINVSMGINVSPEEDINVSTANAMINVSTLEVEL
INVSTMNBRINVSTRINVSTRDESINVSTRLEVINVSTRUCT
INVSYMNAMINVTABINVTABSPECINVTERTAB
INVTIMEINVTOKENINVTQEFMTINVTYPEINVTYPEINVUIC
INVUICINVUICINVUICINVUSERINVUSERNAMEINVUSERSPEC
INVVALINVVALCLAUSEINVVECINVVIEWSPINVVMSOSC
INVVOI_IDINVVOLFMTINVWIDARGIO_CONCLO
IOERRORIOPIRCISD_OFFISD_SIZISD_VBNISI
ISQUALITCITDITEMNOTFOUNDITERATIONITMNOTDEF
ITMREMOVEDIVADDIDIVADDNODEIVADDRIVATIME
IVBAKADIOIVBLKENTIVBLKNUMIVBUFLENIVBUFLENIVCHAN
IVCHARIVCHNLSECIVDEVNAMIVDTIMEIVFNAMIVGBLTYPIVGSDNAM
IVKEYNAMIVKEYWIVLISTKIVLOCKIDIVLOGNAMIVLOGTABIVLVEC
IVMODEIVOPERIVORDERIVPFAILIVPROTIVPROTECT
IVQLOCIVQUALIVQUALIVQUOTALIVREMIDIVREMNODE
IVSIVSECFLGIVSECIDCTLIVSSRQIVSSRVRQST
IVSTSFLGIVSYMBIVTIMEIVTIMEIVTYPEIVVALUIVVERB
IVWSETLISTJBCERRORJBRTAINHLDJECJNLACP
JNLACTIVEJNLDRVJNLNOTAUTHJNLNOTOPENJNLOPEN
JNLPUTJOBABORTJOBCARDJOBCTLABORTJOBDELETE
JOBDELFOJOBNOTEXECJOBQUEDISJOBQUEENAJOBREQUEUE
JOURNALJOURNALBEGJOURNALCLOSEJOURNALEOF
JPITSTERRKBFKEYKEYKEYALRINSKEYAMBINC
KEYCNVKEYDEFPROKEYEDKEY_LENKEYMAPNOTFND
KEYNAMLNGKEYNOTDEFKEYNOTFNDKEYNOTFOU
KEYSUPERSEDEDKEYWORDPARAMKFFKNMKRF
KRNLSTAKNVKSIKSZLABELERRLANLARGECNT
LARGECNTLATSTOPPINGLCKPAGFULLDELENMUSONE
LENNOTEQLLENVIOLEXLIBFINDLIBNAMLNG
LIBNOTOPNLIBOPNLINCOMLINEABRTLINERRLINETOOLONG
LINKLINKABORTLINKDISCONLINKEXITLINNOTFND
LINPROLINTOOLONGLISINPSAVLISTENDSBLISTENENAB
LISTENFAILLISTENNOTMBXLISTNOTFNDLISTTOOSHORT
LKBGRANTEDLKBREFNEGLKPNOTDONLKWSETFUL
LNELNKLOADERRLOADIDXLOCKHEADERLOCKMGRERR
LOCKVOLLOCNEGLOCNOTESTLOCPRESLOGCLOSLOGDBUR
LOGDBUTLOGFAILOGFAILLOGICLOGICLOGINITLOG_IN_USE
LOGIOLOGLINKLOGNAMELOGNAMELOGOPNMLOGOPNRLOGOPNT
LOGTIMELOGZERNEGLONGDSTLOOKUPERRLOSTEXTHDR
LOSTHEADERLOSTINFOLOSTMSGLOSTSCANLOWDISKSPACE
LOWMEMORYLOWQUOTALRJACCESSDENIEDLRJACCESSREJECT
LRJCORRUPTLRJDELETEDLRJDISABLELRJILLEGAL
LRJINUSELRJIVPASSWORDLRJNAMEUNKNOWNLRJNOSERVICE
LRJNOSTARTLRJNOTOFFEREDLRJNOTSUPPORTLRJRESOURCE
LRJSHUTDOWNLRJUNKNOWNLRJUSERDISLRL_MISS
LSTERRLSTMSG1LSTMSG2LSTTOTBKLTCLUNALRFRE
LUNRESSYSLVSADDERLVSMLTERLVSSBTERLVSSHLERLVSSHRERLVVMLTER
LVVSBTERLVVSHLERLVVSHRERMACHINECHKMACLBFMTER
MACNAMLNGMAILBOXMAKEWSLEMANY_TO_ONE
MAPAREAMAPCNTZERMAPHDRBADMATCHMATCHED
MAXBADMAXDEVMAXDIFMAXLABMAXLINKSMAXMAPPEDBUF
MAXPARMMAXSERVMAXTOOBIGMAXUNITSMAXVALUEMAXVOLS
MAYNOTINDXMBACBHUNGMBCMBFULLMBTOOSML
MBXASGERRMBXCRERRMBXCRTERRMBXRDERR
MBXREDERRMBXWRTERRMCHECKMCHECKMCHINSTSYN
MCNOTVALIDMDBSFCRUPTMDBSFRFAIMDFYERR
MDFYMSGMEDOFLMEDOFLMEIMEMBUGMEMBUGMEMERRS
MEMFULMEMNOTSVDMERGEMFNMFSMFYNULPGFL
MGTPRMMHDERRMINVALUEMIRBFOVFMIRCTFMIRDISMISCONFUNI
MISENDSTAMISFILSPEMISNAMREQMISREQPAR
MISSINGENDMISSINGQUOTEMISSNGPARMMISSNGSYM
MISS_PARAMMISSPASSMISSQUOMISSQUOTEMISSYMTAB
MISTERNAMMIXEDTYPESMKDMLBOPNERR
MNLMODIFIEDMODIFYERRMODLINKMODNAMMODNAMLNG
MODNODEMODNOTADDMODNOTFNDMODOUTAIMODOUTAIS
MODOUTBIMODOUTBISMODPORTMODQUOTAMODRANGEMARKS
MODRELNBAKMODSERVICEMOUNEWVOLMOUNTDEV
MOUNTEDMOUNTERRMOUNTERRORMOUNTF11MOUNTFOR
MOUSEINVMOUVOLMOVEFILESMOVETOCOPYMQS
MRCMRGMRGGTMTCHMRNMRSMRS
MSCPNOTLDMSCPSERVMSGBUFSETMSGCMAIIF
MSGNOTFNDMSGNOTFNDMSGQUEEMPTYMSNGENDS
MSTINTERRMTLBLLONGMTLBLLONGMTLBLNONA
MTXCNTNONZMULCLUOPTMULDEFMULDEFLBL
MULDEFPSCMULPRIMULPSCMULSECMULSHRPCS
MULTALLOCMULTCHNGMULTECOMULTEXTHDRMULTFR
MULTIDEFMULTIPLENAMESMULTISELECTMULTOPRMULTRMS
MUSTBECONSTMUSTBEONEMUSTCLOSEFLMVABORTED
MVCOMPLETENAFADDERRNAFAEXNAFCONERR
NAFCREERRNAFDNENAFDONEMSGNAFNOMODS
NAFUAEERRNAMNAMETOOBIGNAMETOOLONG
NAOFILNAONAFNARGNCBFAILNCSNEEDBOTHNEEDFILENAME
NEEDTERMSNEEDTOASSIGNNEFNEGATEDNEGSHBREF
NEGSTRLENNEGTIMNESTERRORNESTLEVEL
NETNETASNNETASNNETDASNETDISNETERRNETFAIL
NETIONETIOERRNETLSTMSGNETMBXNETMBXNETNOBUF
NETNOSTATENETRCVPKTNETSYSSRVNETTRANCNT
NETWORKNEWCOMPFILNEW_FILENEWFILESNEWIGNORE
NEWLINKNEWLOGNAMENEWPAGENEWPORTNEWQUEUE
NEWSAVSETNEWSERVERDBNEWSERVICENEWTAPE
NEXNOTUBANEXTVOLNIANICNMFNMLRSP
NONOACCMANNOACCPTMSGNOACESSNOACNT
NOACPNOACPCHANNOACPDEVNOACPMAILNOADAPTER
NOALLOCNOALLSPOOLNOALOCLASSNOALTPRINOANGLE
NOANSWERNOAQBNOAQBACPNOARGNO_ARGSNOASSIGNMENT
NOAUTOCNFNOAUTOSTARTNOAVAILNOBACKUPNOBADDATA
NOBADDATANOBADINFONOBITMAPNOBRANCHNOBREAKPOINT
NOBUFPCKTNOBUGCHKNOBUGCHKNOBVPVCB
NOBYPASSNOCACHENOCALLSNOCALLUSERNOCARRIAGE
NOCCATNO_CHADISNOCHARREADNOCLASSNOCLASSES
NOCLINOCLITABLENOCLUDEVNOCLUSTERNOCMDMEM
NOCMDPROCNOCMEXECNOCMKNOCMKRNL
NOCOMDNOCOMMSTLEVNOCOMMUNICATIONNOCOMPLSTS
NOCONNECTNOCONSOLENOCONTIGNOCONTIGNOCONVBOOT
NOCOPBADNOCOPBADDELNOCOPDUPNOCOPLOCKNOCOPNODEL
NOCOPPROTNOCOPSAMDEVNOCOPSYSDELNOCOPYBOOT
NOCOPYBUFNOCPUSNOCSPNOCURRENTBUFNOCURTID
NODNODECNTRSONLYNODECODENODEDISABLEDNODEENABLED
NODEFINITIONNODEFPWDNODEINIERRNODELLOCK
NODENOTAVAILNODENOTCLUNODENOTMEMNODENOTPRES
NODERRNODESHUTNODESTQUENODETACHNODEVADAP
NODEVAVLNODEVAVLNODEVICENODEVINFONODEXITNODIAGNOSE
NODIATONENODISKQUOTANODISKSPACENODSTQUE
NODTOOBIGNODUNAVNODUPEXCNOELEMNOENCODENOENCODE
NOENDOFLINENOENTRYSYMNOEOBSTRNOEOMNOEOM
NOEOMNOEPMNOEXQUOTANOFILENOFILENOFILEACCESS
NOFILEIDNOFILEROUTINENOFILESNOFILNAMNOFILPURG
NOFORCMDNOFORMLARGNOFREENOGBLNOGBLSEC
NOGBLSELDATANOGBLSELOWNERNOGROUPNOGRPNAM
NOGRPWILDNOGSDREFNOHANDLERNOHDJMTNOHDRRES
NOHIDDENNOHISTORYNOHLPLIBSNOHLPTXTNOHLPTXTNOHOME
NOHOMEBLKNOHOMEBLKNOIDBAVAILNOIDNAM
NOIMGFILNOINDEXNOINDEXFNOINFONOINITNOINPFILES
NOINPTABNOINSTRANNOINTABLENOIOCHANNOIOCHAN
NOITMLSTNOJOBCTXNOJOBIDNOJOBNAMENOJOURNAL
NOKEYNOKEYMAPNOKEYMAPLISTNOKEYWNOKFEFND
NOLBLSNOLCLNOLICENSENOLINKSNOLISTNOLISTNOLIST
NOLISTENERNOLITERALNOLOADNOLOCKIDNOLOGNAM
NOLOGTABNOLOWVERNOMACFOUNDNOMALFUN1
NOMALFUN2NOMATCHNOMATCHNOMATCHESNOMATCHFOU
NOMBXNOMCHKFRAMENOMEANINGNOMEMBER
NOMODNAMNOMODSNOMODSNOMODSNOMORECHAR
NOMOREENTNOMOREFILENOMOREFILESNOMOREFORM
NOMOREITEMSNOMOREITEMSNOMOREJOBNOMOREKEYS
NOMOREMSGNOMORENODSNOMOREPROCNOMOREQUE
NOMORESVCSNO_MORMSGNOMPNOMSGSNOMSGS
NOMTCHENDMNOMTCHENDRNOMTCHFOUNOMTCHFOU
NOMULTBKNONAMESNONANSICRTNONBRDMSGNONCONTIG
NONCONTIGNONEDELNONEFOUNDNONERECNONET
NONETMBXNONEWMAILNONEXDRVNONEXISTNONEXISTBUF
NONEXPRNONEXSTACPNONLOCALNONODENONPHYSET
NONPICNONPICDATNONPICIMGNONPICREF
NONSMPDRVNONSTDUNINOONE_ENABLEDNOOPCOM
NOOPENJOBNOOPERNOOPERNOOPERNOOPERNOOPR
NOOPRNDNOOUTPUTNOOUTQUALNOP1VANOPAGEDYN
NOPARAMNOPARENNOPARENTNOPARENTNOPARMNOPARMNOPASS
NOPASSWORDNOPATAREANOPENOPERATOR
NOPFNMAPNOPREVNOPRINTNOPRIVNOPRIVNOPRIVNOPRIV
NOPRIVDIRSUMNOPRMCEBNOPRMGBLNOPRMMBX
NOPROCNOPROCESSNOPROCTPSNOPRODSNOPROT
NOPSCTSNOPSWAPMNOQFILENOQUALNOQUALNOQUAL
NOQUECTXNOQUESPACENOQUEUENOQUOTENORCPNORCVBUF
NOREADNOREADCPNOREADERNO_RECORDNOREDEFINE
NOREFNORELNOTENORELOCNOREMBROADNOREMOTE
NOREMWAITNORENDEVNORENEXISTSNORENLOCK
NOREPAIRNOREQNOREQSYMNORESTARTNORESTART
NORETURNVALUENORIGHTSDBNORMALNORMALNORMAL_EXIT
NOROOMNOROOMNORSTBLDNORTTBNORUNMCRNOSAVESET
NOSAVPEXCNOSCSNOSECEXNOSELECTNOSELFNOSENDBUF
NOSERVERNOSETPRVNOSETPRVNOSEVERNOSHDWMEMNOSHMBLOCK
NOSHMEMNOSHMGSDNOSHOWBUFNOSHRDNOSHRIMGNOSIGNAL
NOSLOTNOSOLICITNOSPACENOSPACENOSRVCNOSTACKMEM
NOSTATSNOSTRINGNOSTRMEMNOSUBEXINOSUCHACE
NOSUCHCHARNOSUCHCPUNOSUCHCTXNOSUCHDEV
NOSUCHDEVNOSUCHELENOSUCHENTNOSUCHFILE
NOSUCHFILENOSUCHFILENOSUCHFORMNOSUCHID
NOSUCHJOBNOSUCHLOCNOSUCHMEMNOSUCHMOD
NOSUCHMODUNOSUCHNAMNOSUCHNODENOSUCHNODE
NOSUCHNODENOSUCHNODENOSUCHNODENOSUCHOBJ
NO_SUCH_PARTYNOSUCHQUENOSUCHRQSTNOSUCHRTN
NOSUCHRVNNOSUCHSECNOSUCHSYMNOSUCHSYM
NOSUCHTIDNOSUCHUSERNOSUCHUSERNOSUCHUSR
NOSUCHVERBNOSUMMNOSYMBOLNOSYMBOLSNOSYMBOLS
NOSYSACTNOSYSCLFNOSYSDISKNOSYSGBLNOSYSIPCNOSYSLCKNOSYSNAM
NOSYSPRVNOSYSTPSNOT1STVOLNOT1STVOLNOTACLU
NOTALLPRIVNOTALLREQUENOTALLSYMNOTANSI
NOTANSINOTAPEOPNOTARRAYNOTASCIINOTASSIGNNOTATERMNOT_A_TERM
NOT_A_TRMNOT_AVAILABLENOTBKBLOCKNOTBOOCAP
NOTCLASSNOTCMASTACKNOTCMPLTNOTCOMNOTCOPIED
NOTCOPIEDNOTCOP_RETRYNOTCREATORNOTCTX
NOTDDBDDBNOTDECSTRGNOTDEFINABLENOTDELETED
NOTDELETEDNOTDIRNOTDISCONNOTDISKNOTDISM
NOTDONENOTDONENOTENABOPTNOTENUFOPRNOTERM
NOTERRORKEYWORDNOTEXISTNOTFCBFCBNOTFCBWCB
NOTFCPWCBNOTFILEDEVNOTFOUNOTFOUNDNOTFOUND
NOTFRNOTGENDEVNOTHENNOTHLPLIBNOTIDFMT
NOTIDXNOTIFYNOTIMGLIBNOTIMPNOT_IMPLNOTIMPLEMENTED
NOTIMPOPCODENOTINANIFNOTINMACRONOTINPHYS
NOTINSTALLNOTINTBLSZNOTIRPAQBNOTJOURNAL
NOTLABELNOTLABELMTNOTLEARNINGNOTLGLISOP
NOTLKBNOTLOADEDNOTLOCKEDNOTLOCKED
NOTMEANINGFULNOTMODNOTMODEMNOTMODIFIABLE
NOTMODIFIEDNOTMOUNTEDNOTMPMBXNOTMTLMTL
NOTNEGNOTNETDEVNOTNUMBERNOTNUMCAP
NOTOBJLIBNOTOBJLIBNOTODS2NOTOFFEREDNOTONSCREEN
NOTPARAMNOTPASTEDNOTPATADRNOTPCB
NOTPRINTEDNOTPSECOPTNOTPSECTNOTPSHARE
NOTQUEUEDNOTQUONOTRANNOTRANNOTRANNOTREADIN
NOTRELVOLNOTRENAMEDNOTRESNOTRMSOUT
NOTRULUCBNOTRVTVCBNOTSAMEBUFNOTSAMEDEV
NOTSAMEDEVNOTSAVEDNOTSAVESETNOTSEQNOTSET
NOTSHDWDEVNOTSHRIMGNOTSPLADDRNOTSQDEV
NOTSTRCAPNOTSTRUCT1NOTSUPPORTEDNOTSYSTEM
NOTUCBIRPNOTUCBRVTNOTUCBUCBNOTUCBWCB
NOTUICFMTNOTUQPORTNOT_USABLENOTVALID
NOTVALLENNOTVCBUCBNOTVOLSETNOTVOLSET
NOTVVPVCBNOTWCBIRPNOTWCBWCBNOTWITHCONN
NOTYETNOUNLOADNOUPDATENOUSERNAMENOUSERNAME
NOUSERPASSNOUSERSPECNOUSRWCSNOVALPRSNOVALU
NOVALUENOVALUENOVECTORNOVERNOVIRMEMNOVOLDATA
NOVOLPRONOVOLUMESNOWILDNO_WINASSOCNOWINDOW
NOWORLDNOWRITERNO_WRKNOWRTNPKNSADDRNSF
NTDNUDFENVSNUDFLSYMSNUDFSYMSNULFILNULIDX
NULLFILENULLPRINULLPRIVNULLSTRINGNULSAVESET
NUMBERNUMELEMENTSNUM_KEYNUMOPRNDSNUMTRUNC
NUMVALNVROPRFAIOBJOBJLOCKEDOBSSERVERDB
OBTEVTOCCLUDEDOCVNOTFNDODS2SAVEOFFHOOKOFFLINE
OK_ALKOK_DELOK_DUPOK_IDXOK_LIMOK_NOPOK_RLK
OK_RNFOK_RRLOK_WATOLDINSCHKOLDLIBRARY
OLDMISMCHOLDPURGEOLDTABOLDVALCHKONCOMD
ONDELRECLISTONEDELTIMONEENTQUEONEF11DEV
ONEF11OUTONEIMGDEVONELEARNONEPHYDEV
ONERRONESELECTONEVALONHOOKONLEVLONOVF
OPCCUSOPCDECOPEFAIOPEJBCMBXOPENBITMAP
OPENDIROPENDIROPENERROPENEXCOPENFAILOPENFDLOPENFILE
OPENFILEOPENFOREIGNOPENINOPENINOPENINOPENINDEX
OPENMONOPENOUTOPENOUTOPENOUTOPENOUTOPENQUOTA
OPENUAFOPENVIRTUALOPER1OPER10OPER11OPER12
OPER2OPER3OPER4OPER5OPER6OPER7OPER8
OPER9OPERABORTOPERASSISTOPERFAILOPERREQ
OPERSPECOPERSTSOPINCOMPLOPINPROGOPNERROPNOTPERDOS
OPNOTPERF11OPNOTSUPOPNOTSUPOPNSNKOPRABORTOPREPL
OPREPLYOPREPLYOPRNDLNGOPRNDSYNXOPRNOTIFOPRQST
OPRQSTCANOPRQSTDONOPRSNDERROPSYNTAX
OPTARGMISOPTIGNSHROPTIGNSYSOPTLINOPTSYNERR
OPTVALERRORBTOOBIGORDERORDER_ERROR
ORGOSCTOOLONOUTCMDLNGOUTCONERR
OUTOFRANGEOUTORDEROUTPUTOUT_RANGEOUTSIMG
OUTSIMGPOUTSTRTRUOUTSWPERROVERFLOW
OVERLAPRANGEOVERLAYOVERWRITEOVRALIOVRDSKQUOTA
OVRFLWOVRSIZPACTOOLONGPADPAGECRITPAGEFRAG
PAGEREDERRPAGEWRTERRPAGLIMEXCPAGNTRNVAL
PAGOWNVIOPAGRDERRPARGTMTCHPARITYPARITY
PARMDELPARNOTGRANTPARSEPARSEERRPARSEERRPARSEFAIL
PARSEFAILPARSEOVERPARTCOPIEDPARTESCAPE
PARTMAPPEDPARTOOBIGPART_SECTNPASALREXI
PATERRPATHAMBIGPATHLOSTPATHTLONGPATHUNDEF
PATHUNRESPATOVERPBDIN_USEPBFPC1
PC2PC3PDQUALERRPEAKUTILPENDINGPENDING
PERMSYMPESPEXFULLPFMBSYPFNLISTCNTPFNREFNZRO
PGFGBLBADPGFIPLHIPGFLOCBADPHANOTFND
PHYDEVGEOPHYFILSPEPHYSETPLGPLVPLV
POOLEXPFPORTRXERRPOSPOSERRORPOSITERRPOWERFAIL
PRACCREMPRACRENPRCREATPREDEFREPPREMATUREEOF
PREMEOFPREMEOFPREMMSGPRESENTPREVDUPACEPREVINIT
PRIIHDBADPRIMINPRIMNOSTPPRIMOUTPRINTPRIOSMALL
PRISECMAPPRIVPRIVINSTALLPRMEOFPRMLEN
PRMLONPRMMSPRMNAPRMRNGPROPROCDONEPROCESSEND
PROCFILEPROCGONEPROC_IDPROCINDEXPROCSUPERSEDED
PRODNOTINSPRODSKIPPROERRPROERRPROGLOSTPROL_WRT
PRONOTCHGPROTECTEDPROTECTEDPROTECTED
PROTERRPROTINSTALLPROTMISPROTOCOLPROTOCOLPROTOOLON
PRTEXTPRVPRVNOTFNDPRVNOTUNQPRVNOTUNQ
PRVVIOPSCALIPSCNXRPSECBUFOVFPSECBUFUND
PSECOPCNFLPSTFULLPSUSPECTPTELENVIOLPTRCNT
PURABOPURGEVERPURGWSSCNPUSSTAOVEPUTERR
PUTERRPWDINDICPWDINHISPWDLOCKEDPWDNCHPWDNOL
PWDNOTDIFPWDNOTVALPWDNOTVERPWDSYNTAX
PWDSYNTAXPWDWEAKPWFQEMPTYQFACTIVEQFNOTACT
QIOBFOVFQIOERRQMANCREPRCQMANDELQMANNOTSTARTED
QSTQUALINVQUALOBSQUEAUTOOFFQUE_CLOSED
QUEDISABLEDQUEFORMATQUENOTMODQUENOTSTART
QUENOTSTOPQUERESETQUEUEMPTYQUITTINGQUO
QUOTAFAILQUOTAFILEQUOTAFNFRABRAC
RADRMODRATRAWFMTRBFRCTUNRSZRRDBADDERR
RDBADDERRURDBADDERRVRDBADDMSGRDBADDMSGU
RDBCREERRRDBDONEMSGRDBMDFYERRRDBMDFYERRU
RDBMDFYMSGRDBNOMODSRDBREMERRRDBREMMSG
RDBREMMSGURDDELDATARDSNONRESREADABORTED
READATTRREADBADREADBLOCKREADBMAPREADBOOT
READCHECKREADCHECKRECREADDIRREADERRREADERR
READERRREADERRREADERRREADERRREADERRRECREADERRS
READEVTREADFILEREADHEADERREADHEADERREADHOME
READIBMAPREADIMAPREADJNLACEREADQUEHEADER
READQUOTAREADSBMAPREADSCBREADYREAD
READYWRITEREADZEROREAJBCMBXREALLYQUIT
REALLYRECOVERREBLDREQREBLDWARNREBOOTREBUILD
RECGTRBLRECISDELRECLNGRECLNGRECLNGRECORDANS
RECORDSWLRECOVERRECOVERABORTRECOVEREND
RECOVERFAILRECPRNRECTOBIGRECTOOBIGRECTOOSML
RECTRUNCRECTYPRECTYPRECURLEARNREDCACHEREDEFSYM
REDFLGERRREENTREENTERREENTRANCYREF
REFCNTNEGREFERENCEDREFRESH_NEEDEDREFUSED
REGOPSYNXREGWIDDUPREINITERRREJECTRELCONCAT
RELINKRELMOVEDREMABOREMARCESTREMARCFAIL
REMARCNAVLREMARCSTSREMDEFREMDISABLED
REMENABLEDREMERRREMERRREMMSGREMNOTENAB
REMOINSFREMOTEREMOTEREMOUVOLREMOVEREMOVED
REMOVEDREMOVEDREMRSRCREMSYSRENAMEDRENDEFRENMSG
RENSYSREPEATREPLACEDREPLACEDREPLACEERRREPLACERR
REPLAYFAILREPLAYWARNINGREQARGSMISSINGREQDITEMMISS
REQFILMISREQKEYREQPRMABSREQUESTREQUIRESDECW
REQUIRESTERMRERRESCRASHRESCRITICALRESDISMISS
RESERRRESETRESETQUERESIGNALRESINFORESNOTDISK
RESOKAYRESOPCODERESTARTRESTARTCOMRESTORE
RESTOREFAILRESTRICTRESULTOVFRESUMERESUME
RESUMEDRESUMEFAILRESUMEWARNRESWARNING
RETURNEDREVERSECASEREVOKEERRREVOKEMSG
REWINDREXREXRFARFAERRRFAPASTEOF
RFLOCRFMRHBRLFRLKRLSSRVERR
RLSTMSGRMALRDCLRMSRMSBUGRMSERRORRMSFILINIRMSFILMIS
RMTPATHRMVRNAME_ABSENTRNAME_INVRNAME_LONG
RNAME_ODDRNFRNLROPROPRANDROPRAND
ROUTREQRPLRPTCNTNABSRQSTABORTRQSTCAN
RQSTCMPLTERQSTDONERQSTPENDRQSTSTSTRRVRSA
RSBREFNEGRSBREFNZRORSKRSLRSLOVF
RS_LSS_ACRSSRSTRSV_ERRRSZRSZ
RT11_BADDIRECTRT11_BADFILERT11_BIGBADFILERT11_DIRSIZE
RT11_ERRLOCKRT11_EXTRART11_NOENDRT11_OVERFLOW
RT11_STBLOCKRT11_TOOMANYBLKRT11_TOOMANYSEGRT11_UNKENT
RTBRTLRTLRTNERRORRTOUTEOFRTPROTECT
RTSRUCONFLICTRUFRVN1NOTMTRVU
SAMEDEVICESAMEFILESAVEAMBIGSYMSAVEERROR
SAVEUNDEFPROCSAVSETCLUSAVSETNAMSBIAERROR
SCANADVANCESCANDEADPTSCBRDERRSCHDWKSCRATCH_HEADER
SCRBUFOVFSDBSFFULLSDBSFRFAILSEARCHFAIL
SEARCHFAILSECINTFAISECOUTSECREFNEGSECTBLFUL
SECTRESTOREDSECTSAVEDSECTUNDEFPROCSEG
SEG_FAILSELRANGEZEROSEMALRMAXSEMANTICS
SEMININONSENDABORTSENDERRSENDFAILSEQSEQ
SEQNCESEQNCESEQUENCESEQUENCE2SERUNAVSERVE_ERR
SERVEREXITSERVEXISTSSESLIMSETIMRSETKEY
SETLIMITSETMAXSETMINSEVINVALDSHADBOOTFAILSHADDETINCON
SHARCONFSHASINGMBRSHMGSNOTMAPSHMNOTCNCT
SHOFILSHOIOSHORTBLOCKSHORTDUMPSHOW_ERR
SHOWERRSHOWERRSHRSHRCNTNEGSHRCPYIGN
SHRIDMISMATSHRINSYSSHRPSCLNGSHRPSCREF
SHRSEPCLUSHRSYMREFSHRSYMTRASHUT
SHUTDOWNSIGNAL_Q_FULLSIGNO_ARGSIZ
SKCSKPDATSLOWRESPSMALLPAGESOFTRERRS
SOFTWERRSSOLCONNECTSOLOPENSOLREADLINE
SOLTIMEOUTSOLWAITINGSORTALLOCMEMSOURCELINE
SPAWNEDSPCIVCSPCIVDSPCIVFSPCIVISPCIVKSPCIVP
SPCIVSSPCIVXSPCMISSPCOVRSPCSISSPDNOTSET
SPECDEVSPECDIRSPECIFYSPECNODESPECWILDSPLSPLACQERR
SPLIPLHIGHSPLIPLLOWSPLRELERRSPLRSTERR
SPNAMLNGSPTERRSSPTFULLSPTNOTFNDSPWNIOSQO
SQUALERRSQUROONEGSRCLINSRCMEMSRTIWASRVALLOAD
SRVCNODESRVDISSRVMISMATCHSSCHANGESSERRORSSFAIL
SSRSSRVEXCEPTSTABLEEXCSTACKDUMP
STACKOVERSTACKOVFSTALITUDFSTARTDELETESTARTED
STARTRECORDSTARTUPSTARTVERIFYSTASMALLMEM
STATENTSVDSTATE_UNKSTATOOLONGSTD
STDISPICSTGTRUNCSTILLKEYSSTKNOTCHANGESTKOVFSTKOVFLO
STMRECFMTSTNOTAVAILSTPCLUSTPINVALDSTRCPYERR
STRIS_INTSTRLVLSTRLVLSTRLVLSTRNOTFOUNDSTRNOTWCB
STRTERESCSTRTERESCSTRTNOMULTISTRTOOLARGE
STRTOOLNGSTRTOOLNGSTRTOOLONSTRTRU
STRUCLEVSTRUCT_LEVELSUBABORTSUBALREXISUBINTERR
SUBLOCKSSUBMITERRSUBRNGSUBSCHERRSUBSPNERR
SUBSTSERRSUBTRACEDSUCCDUPACESUCCESS
SUPSUPERSEDESUPERSEDESUPERSEDE
SUPPORTSUSPENDSUSPENDSUSPENDEDSWAPAGINS
SWAPWSLESYITSTERRSYMABRSYMCREPRCSYMDCLEXTR
SYMDEFINMOSYMDELSYMDELSYMDELETESYMINSERT
SYMLNGSYMNAMLNGSYMNOTABSSYMNOTFOU
SYMOUTPHASSYMOVFSYMREPLACESYMTOOLNG
SYMTOOLNGSYMTOOLNGSYMTOOLONGSYMTRUNC
SYNSYNCHSYNERRSYNTAXSYNTAXSYNTAXSYNTAX
SYNTAXSYNTAXSYNTAXSYNTAXERRSYNTAXERROR
SYSSYSADJWSLSYSDEVSYSDIRSYSDISKSYSERROR
SYSERRORPCSYSFAILSYSFAOERRSYSIDSYSJNLFULL
SYSJNLNACSYSLOADSYSMGTSYSMSG2SYSNAMSYSNOTUPD
SYSPWDMODSYSSRVERRSYSTRMERRSYSVERCHK
SYSVERDIFSYSVERDIFSYSVERDIFSZTOOBIGTABEXISTTABID_MISTABLEFULL
TABNOTFNDTABSUPERTAMPERTAPECLASSTAPEFULLTAPEPOSLOST
TAPESTARTBITTBKBUGTERMDSBLTERMENABTERMFAIL
TEROUTTEXTTEXTTEXTTEXTDTEXTDTFE
TFRSYSTHIRDPARTYTIMED_OUTTIMEOUTTIMEOUT
TIMEOUTTIMEOUTTIMEOUTTIMEOUTTIPCUFLOWTIRLNG
TIRNYITITLETITLETRUNCTKNOVFTLKINUSETMF
TMOTMPTMPMBXTMRTMSTMSCPLDERR
TMTTMVTNSTODISCONTOODEEPTOOFEWTOOLONG
TOOMANCLSTOOMANDISTOOMANNODTOOMANPAS
TOOMANYTOOMANYARGSTOOMANYCOLTOOMANYLEV
TOOMANYLNAMTOOMANYPARAMTOOMANYREDSTOOMANYSUB
TOOMANYVERTOO_MNYTOOMNYARGTOOMNYARGS
TOOMNYDLMTOOMNYENDRTOOMNYFILTOOMNYFILES
TOOMNYGSTTOOMNYLIBTOOMNYOPNDTOOMNYOUT
TOOMNYPSECTOOMUCHDATATOOMUCHINFOTOPLINETRUNC
TOQUITTOTALTOTALTPSFAOERRTPSINVBLKTPSTERM
TPSUTCERRTRACEBACKTRACIGNTRETRMMBX
TRMNOTANSTRUTRUNCTRUNCTRUNCATETRUNCATE
TRUNCATEDTRUNCDATTSRVALLOADTSTPHSNAM
TTLTWICETWOWIDTHSTYPTYPMISMCH
UAEERRUAFGETERRUAFOPNERRUBFUBMAPEXCED
UDAPORTUDEFPSCUDF_BKSUDF_BLKUDFENVUDFSYMUDS
UICERRUID_INVUID_LENGTHUKNFACILITYUME
UNABLCREVAUNABLEUNABLEUNABLEUNARYOPER
UNASEFCUNDEFINEDPROCUNDEFLINKUNDEFOUTPUT
UNDEFSYMUNDEFSYNTAXUNDEFTYPEUNDEFXFRAD
UNDEXPUNDFILUNDKEYUNDOPTIONUNDSYMUNDTERNAM
UNDTERNOPUNDTERNOSUNDTERTYPUNDWIDCLA
UNECLIERRUNEXPECTEDUNEXPERRUNEXPERRUNEXPERR
UNEXPIOINTUNIMPUNINITEXCUNINITVARUNIVSTARUNKADAP
UNKCLASSUNKCPUUNKCPUUNKDEVUNKENTRYUNKESCAPE
UNKESCSEQUNKKEYWORDUNKMSGUNKNFAILUNKNOPR
UNKNOWNCLEARINGHOUSEUNKNOWN_TAGUNKNPRQUNKOBJECT
UNKOPCODEUNKPKTFMTUNKREPLYUNKRSTRTUNKTYPE
UNKTYPEUNKWNDESCUNLKVOLUNLOCKEDUNLOCKEDUNLOCKERR
UNPRIKWUNPROPARMUNPROQUALUNPROQUAL
UNQUAKWUNRCMDUNRCMPUNREACHABLEUNREACHABLE
UNREACHABLEUNRECSTAUNRECSTMTUNRELVOLUNRFORCOD
UNRFUNUNRKEYUNRKEYUNRPTYUNSAFEUNSECKWUNSOLICIT
UNSTLEVUNSUPRTCPUUNSVRSUNTERMARGUNTERMCOND
UNWINDUNWINDINGUNXINTEXCUNXPCTSTS
UNXSIGNALUPDATEUPDATEDUPDURTRAVUPI
UREURRUSCALLUSEANSUSE_ERRORUSEFLORES
USERDSABLUSERQSTUSERSPECUSERVALUSEUDFEN2
USEUDFENVUSEUDFLSYUSEUNDEFUSEUNDEF2
USGOSUBUSGOTOUSRINPERRUSRTFRUSZV2COMP
VA_IN_USEVALERRVALPRIVALREQVALTOOBIG
VALUEVALUEVARITHVASFULVASOVFVBNERRORVBNMAPFAIL
VBNMISSINGVBNPASTEOFVCALNORCVVCLIM
VCSESLIMVECALIGNVECCTXERRVECDISVECEMULTR
VEC_FLOOVEMATVEC_FLOUNDMATVECFULLVECINUSEVEC_INVARGMAT
VEC_LOGZERNEGVEC_SQUROONEGVECTORVEC_UNDEXP
VERVERBNOTFNDVERIFYERRVERS_MISMATCH
VETOEDVFCVOIALREXIVOLALRMNTVOLIDENTVOLINSET
VOLINSETVOLINVVOLMOUNTVOLNAMEVOLOERRVOLSETSTS
VOLSHDWMEMVOLSTATUSVOLUME_FULLWACKQEMPTY
WAITERRWAITIDLEBCBWANTOSENDWARNINGWARNISUE
WASECCWBEWCBFCBMNGWCCWCSCORRWDW_MAXPREV
WDW_MAXPRMWERWFRWIDMISMATCHWILDCONCAT
WILDOVTVERWILUSERMSWINDNOTMAPPEDWINDNOTVIS
WINEXISTSWINKWINTRUNCFITWKQERRWLDWLDNOTALWD
WLKWORK_DEVWORKINGWPLWRIRSPMSG
WRISMBMBXWRITEACTWRITEATTRWRITEBACK
WRITEBLOCKWRITEBOOTWRITECHECKWRITECHECKREC
WRITECURWRITE_ERRWRITEERRWRITEERRWRITEERRWRITEERR
WRITEERRWRITEERRRECWRITEFILEWRITEHEADERWRITEHOME
WRITEIBMAPWRITEJNLACEWRITELOCKWRITEMON
WRITENABLEWRITERRSWRITESBMAPWRITESCBWRITESCB
WRITLCKWRNERSWRONGACMODEWRONGACPWRONGDATASET
WRONGMUTEXWRONGOWNERWRONGSTATEWRONGVOL
WRONGVOLWRONGVOLWRONUMARGWRONUMARG
WRONUMARGWRONUMARGWRONUMARGWRTEVT
WRTFILWRTHOMBLKWRTINVBUFWRTINVHDR
WRTPGSBAKWSLENOVALWSLPAGCNTWSLVANVAL
WSLXVANMATWSSIZEERRXABXNFXORERRSXQPERR
YESYESNOZEROLENZEROLINKZERONODEZEROPAGEZEROSERVICE
AAA
'filespec' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This message should never be displayed. User Action: Submit a Software Performance Report (SPR).
ABEND
'string' aborted Facility: Shared by several facilities Explanation: A program phase terminated prematurely. User Action: None.
ABENDD
'string' aborted at 'date' Facility: Shared by several facilities Explanation: A program phase aborted prematurely. User Action: None.
ABENDT
'string' aborted at 'time' Facility: Shared by several facilities Explanation: A program phase aborted prematurely. User Action: None.
ABFNAM
ambiguous lexical function name - supply more characters Facility: CLI, Command Language Interpreter (DCL) Explanation: Too few characters were used to truncate a lexical function name to make the function name unique. User Action: Reenter the command; specify at least 4 characters of the function name.
ABKEYW
ambiguous qualifier or keyword - supply more characters Facility: CLI, Command Language Interpreter (DCL) Explanation: Too few characters were used to truncate a keyword or qualifier name to make the keyword or qualifier name unique. User Action: The rejected portion of the command is displayed between backslashes (\ \). Reenter the command; specify at least 4 characters of the keyword or qualifier name.
ABKW
ambiguous keyword in statement 'number '<CRLF>'reference-text' Facility: FDL, Edit/FDL Utility and FDL, Create/FDL Utility Explanation: You have used an ambiguous abbreviation for an attribute keyword. User Action: Enter a more specific abbreviation.
ABNORMAL_EXIT
abnormal exit Facility: PPL, Parallel Processing Facility Explanation: This code indicates the occurrence of the abnormal participant termination event. User Action: Since the application requested this notification, your response is application-dependent.
ABORT
abort Facility: SYSGEN, System Generation Utility Explanation: This message is issued with other messages to indicate that the action is aborted. User Action: Take corrective action based on the accompanying messages.
ABORT
abort
Facility: SYSTEM, VMS System Services
Explanation: This message is returned under either of the
following conditions:
o It is returned by $START_TRANS if the DECdtm services are
disabled on the local node or if the node does not have a
transaction log.
o It is returned by $END_TRANS if the transaction was aborted
during processing.
User Action: On returns from $START_TRANS, make sure the local
node has a transaction log and the DECdtm transaction services are
enabled. On returns from $END_TRANS, check the abort reason code
in the I/O status block to find out why the transaction aborted.
ABORT
abort
Facility: SYSTEM, VMS System Services
Explanation: An attempted operation is aborted by the $CANCEL
system service.
o An I/O request is canceled before it is completed.
o Following a network request, this status indicates that a
logical link is disconnected.
o A fatal hardware error occurred.
User Action: The operating system does not normally display this
message. User programs should be coded to detect and respond
to the status return. If this message is associated with a
status code returned by a request to a DMP11 interface, examine
the device-dependent longword in the IOSB to determine if the
controller is dead. (The controller is dead if the XM$V_ERR_FATAL
bit is set.) If the controller is dead, restart the controller.
Next, check if the tributary is dead. (The tributary is dead
if the SM$V_STS_ACTIVE bit is clear.) If the tributary is dead,
restart the tributary.
ABORT
'testname' aborted at 'date' or 'time' Facility: UETP, User Environment Test Package Explanation: A test ended abnormally. User Action: Investigate the reason for the abnormal termination of the test. Take corrective action based on the accompanying message.
ABORT
operator requested abort on fatal error Facility: BACKUP, Backup Utility Explanation: In response to a BACKUP-I-SPECIFY prompt, the user or operator entered the QUIT option; the Backup Utility terminates. User Action: None.
ABORTC
'testname' to abort this test, type Ctrl/C Facility: UETP, User Environment Test Package Explanation: The image displaying this message responds to Ctrl/C by terminating gracefully (deassigning all logical names and deleting all files) and passing control to the command language interpreter. You cannot restart the image after pressing Ctrl/C. Use Ctrl/Y to temporarily interrupt an image. User Action: None.
ABORTED
application aborted transaction via $ABORT_TRANS service Facility: DDTM, DECdtm Transaction Manager Explanation: The user program has aborted the transaction using the $ABORT_TRANS service. User Action: None. Aborted by CTRL/C Facility: EDT, EDT Editor Explanation: You pressed Ctrl/C after entering a command in keypad change-mode. Pressing Ctrl/C causes all text to disappear from the screen. User Action: If the text is not restored to the screen, press Return.
ABPRIKW
ambiguous primary keyword in statement 'number'<CRLF>'reference- text'. Facility: FDL, Create/FDL Utility Explanation: You have used an ambiguous abbreviation for an attribute keyword. User Action: Provide a more specific abbreviation.
ABSENT
entity or value absent from command string Facility: CLI, Command Language Interpreter (DCL) Explanation: This status is returned by the CLI$PRESENT CLI interface routine. This indicates that the entity value has not been specified in the command line. User Action: None.
ABSTIMREQ
absolute time required, delta time supplied Facility: LIB, Library Facility Explanation: A delta time is passed to the routine when an absolute time is required. User Action: Examine each argument and change the delta time to an absolute time.
ABSYMD
abbreviated symbol definition conflict - rename symbol Facility: CLI, Command Language Interpreter (DCL) Explanation: A new abbreviated symbol is ambiguous with an existing symbol. The new symbol is not entered. User Action: Display the current symbols and adjust the abbreviation of the ambiguous symbol.
ABVERB
ambiguous command verb - supply more characters Facility: CLI, Command Language Interpreter (DCL) Explanation: Too few characters were used to truncate a command name to make the command name unique. User Action: Reenter the command; specify at least 4 characters of the command name.
ACC
ACP file access failed Facility: RMS, VMS Record Management Services Explanation: An error occurred during an attempt to open a file. This message is associated with a status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
ACCCIR
access control specified with loop circuit Facility: NCP, Network Control Program Explanation: Access control with a LOOP command may be specified only with a LOOP NODE or with a LOOP EXECUTOR command, not with a LOOP CIRCUIT command. User Action: Reenter the LOOP CIRCUIT command without the access control.
ACCDISERR
accounting disabled due to file errors Facility: JBC, Job Controller Explanation: Accounting has been disabled because of previously reported errors in the accounting file. User Action: Correct the condition that caused the errors, and reenable accounting with the SET ACCOUNTING/ENABLE command.
ACCERR
nonblank accessibility field in volume labels on 'device-name' Facility: MOUNT, Mount Utility Explanation: The accessibility field on the magnetic tape, which is mounted on the device indicated, has a nonblank accessibility field. This field denies access to the tape. User Action: Mount the magnetic tape with the /OVERRIDE=ACCESSIBILITY qualifier. (The user must be the owner of the volume or have VOLPRO privilege.)
ACCESSFAIL
access has failed for 'device-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility is unable to access the named device. A second error message should follow the ACCESSFAIL message, giving more information. User Action: Retry the command, after taking corrective action suggested by the second line of the message.
ACCLIN
access control specified with loop line Facility: NCP, Network Control Program Explanation: Access control information may be specified only with the LOOP NODE or LOOP EXECUTOR commands, and not with the LOOP LINE command. User Action: Reenter the LOOP LINE command without the access control.
ACCONFLICT
'filename' is open for write by another user Facility: BACKUP, Backup Utility Explanation: The Backup Utility opened the specified file while another user is writing the file because the /IGNORE=INTERLOCK qualifier is specified with the DCL command BACKUP. User Action: Note that the saved copy of the file may be inconsistent.
ACCONFLICT
file access conflict
Facility: SYSTEM, VMS System Services
Explanation: An attempt to access a file failed because the type
of access requested conflicted with the current file access. This
message is also returned when an execute-only shareable image is
referenced in the context of a main program that is not installed
with the /EXECUTE_ONLY qualifier.
User Action: Possible actions include the following:
o Establish who opened the file and wait until it is closed.
o Check for a programming error. Begin debugging procedures to
verify the type of problem and to find a method to correct it.
o Install the main program with the /EXECUTE_ONLY qualifier.
ACCOUNT
this installation creates an account named 'account-name' Facility: VMSINSTAL, Install Procedures Explanation: The product being installed (or updated) has created an account with the specified name. The user authorization file (SYSUAF) has been updated accordingly. User Action: None.
ACCQUOTA
ACCOUNT had inadequate quota at remote node Facility: SYSTEM, VMS System Services Explanation: This error message is associated with a status code returned from a system service request. An attempt is made to initiate a DECnet-VAX logical link connection. The target object is already using its quota of logical links or some other resource. User Action: This condition is not usually permanent. Try initiating the connection later. Consult the VMS Networking Manual for additional information.
ACCVIO
access violation, reason mask = xx, virtual address = location,
PC = location, PSL = xxxxxxxx
Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal
Explanation: An image attempted to read from or write to a memory
location that is protected from the current mode. This message
indicates an exception condition and is followed by a register and
stack dump to help locate the error. The reason mask is a longword
whose lowest 3 bits, if set, indicate that the instruction caused
a length violation (bit 0), referenced the process page table
(bit 1), attempted a read/modify operation (bit 2), was a vector
operation on an improperly-aligned vector element (bit 3), or was
a vector instruction reference to an I/O space address (bit 4).
This message is also displayed when an attempt has been made to
make the user stack larger than the user's virtual address space
permits. For example, the automatic user stack expansion algorithm
reports an access violation with the following two conditions
which should serve as hints that automatic expansion has failed:
o The reason mask has the low-order bit set. This indicates a
memory reference which is not described in any page table.
o The relatively small P1 address space virtual address is
referenced.
User Action: Examine the PC and virtual address displayed in the
message. The virtual address is often the address to which the
access attempt was made. However, in the case of vector-related
access violations and in some processor implementations, the
reported virtual address may be some other address in the same
page as that address to which the access was attempted. Check the
program listing to verify that instruction operands or procedure
call arguments are correct.
If this message is displayed because of insufficient virtual
memory for automatic user stack expansion, reduce the user stack
requirements of the image or increase the virtual address space
available to the process in which the image is executed.
ACCVIO
access violation, reason mask='xx', virtual address='xxxxxxxx', PC='xxxxxxxx', PSL='xxxxxxxx' Facility: VAXTPU, VAX Text Processing Utility Explanation: Internal VAXTPU failure. User Action: Submit a Software Performance Report (SPR).
ACCWAIT
waiting to access files in 'directory' Facility: QMAN, Queue Manager Explanation: When a node is booting, the queue manager can start up before the disk that contains queue and journal files is mounted. In such cases, all queueing related requests wait and this message displays periodically to alert the system manager of the situation. An accompanying message describes the disk related error. User Action: Make sure the disk is mounted. Consult the accompanying message to diagnose any problems.
ACCWAITDONE
no longer waiting to access files in 'directory' Facility: QMAN, Queue Manager Explanation: When a node is booting, the queue manager can start up before the disk that contains queue and journal files is mounted. This message indicates that the queue manager is no longer waiting because the disk has been mounted or startup has completed. User Action: None.
AC_LSS_MP
ACOFFSET field less than MPOFFSET Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message is issued along with the BADHEADER message and gives a more detailed reason why the specified file header is corrupt. In this case, the Access Control List Offset field of an ODS-2 header (FH2$B_ACOFFSET) contains a value less than the Map Area Offset field (FH2$B_MPOFFSET), wrongly implying that the Access Control List precedes the Map Area in the header. User Action: None. See the BADHEADER message.
ACPINIT
LATACP initialized Facility: LAT, LAT Facility Explanation: The LATACP has been initialized. User Action: None.
ACPMBFAIL
ACP failure to read mailbox Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system automatically reboots if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ACPNAME
ACP file name is too long Facility: MOUNT, Mount Utility Explanation: The file name specified for an ACP image has more than 9 characters. User Action: Reenter the command and specify the correct ACP file name.
ACPNOCTL
insufficient resources - ACP CTL/P1 space limit reached Facility: LAT, LAT Facility Explanation: A request to add more information to the LATACP's database has been rejected because LATACP has insufficient resources to service the request. User Action: Increase the value of SYSGEN parameter CTLPAGES or refer to the VMS LAT Control Program (LATCP) Manual for information on how to set a node limit to decrease LATACP's consumption of P1 space.
ACPNOKSTK
insufficient resources - ACP kernel stack limit reached Facility: LAT, LAT Facility Explanation: A request to add more information to the LATACP's database has been rejected because LATACP has insufficient resources to service the request. User Action: Refer to the VMS LAT Control Program (LATCP) Manual for information on how to set a node limit to decrease LATACP's consumption of the kernel stack.
ACPNOVIRT
insufficient resources - ACP P0 space limit reached Facility: LAT, LAT Facility Explanation: A request to add more information to the LATACP's database has been rejected because LATACP has insufficient resources to service the request. User Action: Refer to the VMS LAT Control Program (LATCP) Manual for information on how to set a node limit to decrease LATACP's consumption of P0 space, or determine the cause of the resource exhaustion and attempt to correct it by tuning the LATACP process.
ACPRECURS
attempted recursion in ACP secondary operation Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ACPSHO
an error is returned from a NETACP SHOW function Facility: EVL, Event Logger Explanation: A network SHOW function used to obtain database information from the network returned an unexpected error. This could be caused by a software error. User Action: Submit a Software Performance Report (SPR).
ACPTIME
ACP does not respond Facility: MOUNT, Mount Utility Explanation: The ACP that is requested in the DCL command MOUNT cannot be initialized. Either the specified image is not an ACP or a system error has occurred. User Action: Verify that the image is an ACP. If it is an ACP, consult your system manager to determine what events in the system might prevent the ACP from starting.
ACPUNSTAK
attempted unstack in ACP primary context Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ACPVAFAIL
ACP failure to return virtual address space Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ACPVAFUL
MTAACP's virtual address space is full Facility: SYSTEM, VMS System Services Explanation: Additional volumes cannot be serviced by the ACP because it does not have enough memory to allocate control information for a new volume. User Action: Start a different ACP using the /PROCESSOR qualifier with the DCL command MOUNT.
ACS
error in access control string Facility: RMS, VMS Record Management Services Explanation: The access control string in the file specification is invalid. Either too many characters or too many subfields were specified. User Action: Correct the syntax of the access control string and retry the operation. Limit the number of characters to 42 (not including quotation marks) and the number of subfields to 3.
ACSIGN
access control string ignored Facility: REM, Set Host Facility Explanation: The access control string specified on a SET HOST command is ignored by the remote terminal facility. User Action: None.
ACT
file activity precludes operation Facility: RMS, VMS Record Management Services Explanation: An RMS operation is attempted while other RMS activity is in progress. This can occur when a record or file operation is attempted while that record stream or file has an operation in progress. It may also indicate that a record operation was attempted while a file operation was active, or a file operation was attempted while a record operation was active. User Action: Correct the program logic to avoid conflicting concurrent operations.
ACTIVE
the following processes are still active: Facility: VMSINSTAL, Install Procedures Explanation: When VMSINSTAL begins an installation, it makes sure that no user processes are active. This check has failed. VMSINSTAL lists active processes. User Action: The Install Utility asks you if you want to continue the installation. Digital recommends that you correct this situation before continuing.
ACTIVEBCB
buffer active during reel switch Facility: BACKUP, Backup Utility Explanation: A software error occurred in the Backup Utility. User Action: Submit a Software Performance Report (SPR).
ACVINORCV
expected access violation exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate memory management exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
ADDERR
unable to add user record Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
ADDFIL
error adding file 'filename' to job Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command Explanation: The system encountered an error adding the specified file to a batch or print job. The accompanying message provides additional information. User Action: Correct the error and reenter the command.
ADDFILE
error adding file 'file-name' to job 'job-name' for user 'user-name' in queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to add a file to the job The file was not restored to the job list during the upgrade. User Action: The accompanying message gives information why the operation failed. Correct the problem and retry the upgrade, or after the upgrade has completed, print or submit the file as originally desired using the DCL command PRINT or SUBMIT.
ADDMSG
user record successfully added Facility: AUTHORIZE, Authorize Utility Explanation: This message is informational. User Action: None.
ADDQUOTA
error adding quota record for ['uic'] Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to add an entry to the quota file for the specified UIC. An accompanying message provides additional information. User Action: Correct the condition specified in the accompanying message and reenter the command line.
ADJSCROLLREG
scrolling parameters altered to top: 'top', bottom: 'bottom', amount: 'amount' Facility: VAXTPU, VAX Text Processing Utility Explanation: The window you have just adjusted is not big enough to handle the current scrolling region, so the scrolling region has been altered. User Action: None.
ADRLSTSYNX
address list syntax error Facility: MACRO, VAX MACRO Assembler Explanation: The address list in the .ADDRESS directive contains a syntax error. User Action: Correct the syntax.
ADRWRTDAT
address data in shareable, writeable section in psect 'psect-name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The object language equivalent of the VAX MACRO .ADDRESS directive is encountered in a COMMON section, such as those found in VAX BASIC, VAX FORTRAN, or VAX PL/I. This would cause the section to be nonshareable; so the linker bases the image. User Action: Remove the address data from the command and initialize it at run time.
ADVADVCOMP
device error while advertising Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred on the network device while advertising clearinghouse information. User Action: The device in which the error occurred is included in the error text, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
ADVADVERSEND
multicast error while advertising clearinghouse Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to build an advertisement protocol or send the protocol via multicast. User Action: This error should only be seen on systems that contain a DNS server. Stop the server and restart it. If the problem persists, contact the Digital Services Group.
ADVALLOC
failed to allocate space for cache entry Facility: DNS, Distributed Name Service Clerk Service Explanation: There is not enough room in the DNS clerk cache for a namespace nickname. The namespace will not be added to the clerk cache. User Action: None. Advance past bottom of buffer Facility: EDT, EDT Editor Explanation: You attempted to move the cursor past the end of the buffer ([EOB]). User Action: Press the up arrow key to move the cursor above the [EOB] mark.
ADVBADFORMAT
bad advertisement message received from device Facility: DNS, Distributed Name Service Clerk Service Explanation: The message that the DNS$ADVER process read from the network device was an invalid clearinghouse advertisement. User Action: Make sure no other process is using multicast ID numbers 09-00-2B-02-01-00 and 09-00-2B-02-01-01. If not, check that the multicasting device is operating correctly.
ADVBTIM
error converting time string in $BINTIM Facility: DNS, Distributed Name Service Clerk Service Explanation: An internal error occurred in the DNS$ADVER process. The image might be corrupt. User Action: Submit a Software Performance Report (SPR).
ADVCACHEINIT
could not initialize DNS clerk cache Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to initialize the DNS caches. This message is usually accompanied by a message indicating the reason for the failure. User Action: Make sure no other DNS$ADVER process is running on the system. Also, make sure that the DNS$CLIENT or DNS$SHARE executables are not installed as shareable images. Take corrective action based on the accompanying VMS error message.
ADVCANTIM
error canceling multicast timer Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to cancel a local timer (used to determine when a multicast of local DNS server information is performed). User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVCHUID
failed to add clearinghouse to cache Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while trying to add DNS clearinghouse information to the DNS global cache. The actual DNS error that caused this error accompanies this error message. The clearinghouse will not be entered in the global cache. User Action: None.
ADVCLILOADFAIL
error while loading client clearinghouses Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while the DNS$ADVER process attempted to load clearinghouse information into the client cache. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVDEASGN
error deassigning device Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to deassign a device that was no longer needed. User Action: The device in which the error occurred is included in the error message, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
ADVDEFCONN
error connecting DNS$DEFAULT_FILE.DAT, no default namespace defined Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was able to open the configuration file, but was unable to connect to the file and read it. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVDEFLOAD
error closing DNS$DEFAULT_FILE.DAT Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to close the configuration file. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVDEFOPEN
error opening DNS$DEFAULT_FILE.DAT, no default namespace defined Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to open the file containing configuration information for this system. The DNS clerk can still execute, but names that use default namespaces will be marked invalid. User Action: Make sure the file DNS$DEFAULT_FILE.DAT exists in the SYS$SYSTEM directory. If it does not, then use the SYS$STARTUP:DNS$CHANGE_DEF_FILE.COM command file to configure default information for the local system. If the file does exist, make sure it has WORLD readable protection.
ADVDEFPARSE
error parsing DNS$DEFAULT_FILE.DAT, no default namespace defined Facility: DNS, Distributed Name Service Clerk Service Explanation: One or more of the entries in the DNS configuration file was invalid. The advertiser was unable to determine the default namespace. User Action: You may need to edit the configuration file DNS$DEFAULT_FILE.DAT in SYS$SYSTEM so it only contains configuration information for the DNS clerk. You can reconfigure the system using the SYS$STARTUP:DNS$CHANGE_DEF_FILE.COM command file. After making corrections, stop the DNS clerk (using SYS$STARTUP:DNS$CLERK_STOP.COM) and then restart it (using SYS$STARTUP:DNS$CLERK_STARTUP.COM).
ADVDEVCHECK
error checking Ethernet devices Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while checking the status of a network device. User Action: The device in which the error occurred is included in the error text, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
ADVDUMPFAIL
error while dumping DNS server clearinghouses Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while the DNS$ADVER process attempted to create a configuration file on the local system. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVETHERMEM
no memory for write to device Facility: DNS, Distributed Name Service Clerk Service Explanation: There is not enough memory available for the DNS$ADVER process to allocate space to build a protocol. User Action: Check process and system memory quotas.
ADVMBX
could not create mailbox DNS$SOLICIT_MBX Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred on the local system that prevented the DNS$ADVER process from creating the DNS$SOLICIT_MBX mailbox. This mailbox is used by the DNS clerk to log errors. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVNICKUID
failed to add NICKNS entry to cache Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while trying to associate a UID with a namespace nickname in the DNS global cache. The actual DNS error that caused the error is included in the error message. An entry will not be made in the global cache for this namespace. User Action: None.
ADVPRIV
not enough privs to run DNS$ADVER Facility: DNS, Distributed Name Service Clerk Service Explanation: The process executing the DNS$ADVER process does not have the necessary privileges. User Action: The DNS$ADVER process needs SHMEM, PFNMAP, EXQUOTA, PRMGBL, SYSGBL, SYSLCK, SYSPRV, LOG_IO, NETMBX, TMPMBX, SYSNAM and CMKRNL privileges. Restart DNS$ADVER using these privileges.
ADVRANDOM
error generating random number Facility: DNS, Distributed Name Service Clerk Service Explanation: Random numbers are used by the DNS$ADVER process to help prevent congestion of multicasts on the network. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVRECBUF
device error while receiving message Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process encountered an error while receiving a message through the network. User Action: The device in which the error occurred is included in the error text, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
ADVRECREATE
recreation of mailbox DNS$SOLICIT_MBX failed Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while receiving a message on the mailbox. Another error occurred when the DNS$ADVER process tried to remedy the error by re-creating the mailbox. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVREREAD
reread of DNS$SOLICIT_MBX failed Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while receiving a message on the mailbox. After a new mailbox had been successfully created, another error occurred while trying to reread the mailbox. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVSETIMR
error setting timer for multicasts Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process was unable to set a local timer. This timer is used to determine when a multicast of local DNS server information is performed. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVSOLCOMP
device error while soliciting DNS servers Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process encountered an error while multicasting a solicitation message to DNS servers on the network. User Action: The device in which the error occurred is included in the error text, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
ADVTIMERR
cannot create timeout value Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS$ADVER process attempted to create a DNS timeout value, but received an error from the $GETTIM service routine. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
ADVUIDNICK
failed to add NSNAME entry to cache Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while trying to associate a UID with a namespace nickname in the DNS global cache. The actual DNS error that caused this error is included in this error text. No entry will be made in the global cache. User Action: None.
ADVWRITETHER
error writing on device Facility: DNS, Distributed Name Service Clerk Service Explanation: An error occurred while DNS$ADVER was trying to write to an Ethernet device. User Action: The device in which the error occurred is included in the error text, along with the VMS status from the device. Take corrective action based on the accompanying VMS error message.
AGAIN
another data analysis pass is needed Facility: DCX, Data Compression/Expansion Utility Explanation: This status, returned by DCX$MAKE_MAP, indicates that DCX must see all data records again before it can compute a map. User Action: The application program should again present data to DCX for analysis.
AID
invalid area id = 'nnn' Facility: RMS, VMS Record Management Services Explanation: An allocation XAB for a $CREATE, $DISPLAY, $EXTEND, or $OPEN operation contains an invalid area identification number field. User Action: The status value (STV) field of the FAB provides the area identification value in error. Verify that the call to the VMS RMS service is coded correctly.
ALCPHD
allocate process header error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ALCSMBCLR
ACP tried to allocate space already allocated Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ALERTED
thread execution has been canceled Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A thread has been requested to terminate by either the cma_thread_alert or pthread_cancel routine. DECthreads uses an alert to request that a thread terminate after first performing cleanup and shutdown operations. User Action: If you do not want threads to terminate at the point where this alert is being delivered, you can use several routines (cma_alert_disable_general, cma_alert_disable_asynch, cma_alert_ restore, pthread_setcancel, and pthread_setasynccancel) to specify points in the thread process where alerts cannot be delivered to the thread.
ALERT_NESTING
improper nesting of alert scope Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: An attempt was made to restore an inner scope after an enclosing outer scope had already been restored. User Action: Examine the code to determine where the incorrect alert state variable was passed to the cma_alert_restore routine.
ALI
invalid alias identification Facility: NCP, Network Control Program Explanation: The format of the alias indentifier is incorrect. User Action: Check the syntax rules for alias identifiers and reenter your command with the correct alias identifier.
ALIGNDISK
'device-name' contains an alignment cartridge Facility: BAD, Bad Block Locator Utility Explanation: The device specified contains an alignment cartridge. User Action: Replace the cartridge with a data cartridge and reinvoke the utility.
ALIGNXCEED
alignment exceeds PSECT alignment Facility: MACRO, VAX MACRO Assembler Explanation: The .ALIGN directive specified an alignment larger than the program section alignment. For example, the .PSECT directive specified byte alignment (the default) and the .ALIGN directive specified a longword alignment, or a .PSECT directive specified an invalid alignment. User Action: Correct the conflicting alignments. The .PSECT directive should specify the largest alignment required by the program section.
ALLOC
'device-name' allocated Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified device is allocated. User Action: None.
ALLOCCLR
blocks incorrectly marked allocated LBN 'n' to 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The specified logical blocks on the specified relative volume were marked allocated in the storage bit map but were not allocated to a file. User Action: None. The utility marks the specified blocks as free in the storage bit map. The /CONFIRM qualifier is ignored in this operation.
ALLOCEXT
blocks allocated to lost extension file header LBN 'n' to 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The specified logical blocks on the specified relative volume were allocated to a lost extension file header. User Action: None. The utility marks the specified blocks as free in the storage bit map. The /CONFIRM qualifier is ignored in this action.
ALLOCFAIL
file structure allocation failure for 'device-name' Facility: BACKUP, Backup Utility Explanation: Insufficient contiguous space is available on the specified volume to allocate the files necessary to initialize the volume as a Files-11 structured volume. This error may be caused by an excessive number of bad blocks. User Action: Retry the operation using another volume.
ALLOCFAIL
index file allocation failure Facility: INIT, INITIALIZE Command Explanation: The DCL command INITIALIZE failed to allocate space on the volume for the index file. This message usually indicates that too much space is requested for file headers. User Action: Reenter the command; specify a smaller value for the /HEADERS qualifier.
ALLOCMEM
error allocating virtual memory Facility: BACKUP, Backup Utility and ANALDISK, Analyze/Disk_ Structure Utility Explanation: An error was encountered during an attempt to allocate dynamic virtual memory. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command. You may need to increase the page file quota of the account or the SYSGEN parameter VIRTUALPAGECNT.
ALLOCMEM
error allocating virtual memory Facility: JBC, Job Controller and QMAN, Queue Manager Explanation: The job controller or queue manager encountered an error while allocating virtual memory. An accompanying message provides additional information. User Action: Take action based on the accompanying message. You might need to run AUTOGEN to increase the SYSGEN parameter VIRTUALPAGECNT. If the accompanying message does not require you to keep the process dump, you can delete it.
ALLOCSET
blocks incorrectly marked free LBN 'n' to 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The specified logical blocks on the specified relative volume were marked free in the storage bit map but were allocated to a file. User Action: None. The utility marks the specified blocks as allocated in the storage bit map. The /CONFIRM qualifier is ignored in this action.
ALN
alignment options error for area id = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The allocation XAB for a $CREATE or $EXTEND operation contains an invalid alignment boundary type (ALN field). User Action: The status value (STV) field of the FAB provides the area identification of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
ALPBFOVF
active looper buffer exceeded Facility: MOM, Maintenance Operation Module Explanation: An attempt to allocate a buffer to be used for a LOOP CIRCUIT command has failed. This may be because virtual memory has been exhausted. User Action: Take steps to increase the amount of virtual memory available for the process.
ALQ
invalid allocation quantity (negative, or 0 on $EXTEND) Facility: RMS, VMS Record Management Services Explanation: An invalid allocation quantity is specified in an allocation XAB or FAB for a $CREATE or $EXTEND operation. User Action: Verify that the call to the VMS RMS service is coded correctly. For file creation operations, the error indicates that the value specified is less than zero. For file extension operations, the error indicates that the value specified is less than or equal to zero.
ALRCURTID
a default transaction is currently defined Facility: SYSTEM, VMS System Services Explanation: An attempt was made to start a default transaction when the process already had a default transaction. User Action: Either terminate the default transaction already in progress before starting a new one, or start a new transaction as a nondefault transaction.
ALREDEF
multiple .TRANSFER for symbol 'symbol-name' illegal psect 'psect- name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An attempt is made to use a .TRANSFER directive on a symbol name more than once. User Action: Remove all but the first .TRANSFER directive for the symbol.
ALTIHDBAD
invalid alternate index file header, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The alternate index file header on the specified relative volume is corrupted. User Action: None. The utility refreshes the alternate index file header from the primary index file header.
AMBCMD
ambiguous command Facility: NCP, Network Control Program Explanation: A keyword in the command has not been specified with enough characters to distinguish it from another keyword acceptable in this context. User Action: Reenter the command and expand upon the specified keyword.
AMBDATTIM
ambiguous date-time Facility: LIB, Library Facility Explanation: The date-time input string did not match the specified input format. User Action: Examine the date-time input string and input format.
AMBIG
ambiguous field name or class name 'class-name' Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The field or class name entered is not unique. User Action: Reenter the field or class name with additional characters or enter the HELP FIELDS or HELP CLASSES commands to get a list of available fields or classes.
AMBIGNAME
variable 'name' cannot be a procedure Facility: VAXTPU, VAX Text Processing Utility Explanation: You previously used an identifier as a variable; you are now attempting to use the same identifier as a procedure. User Action: Use a different name for the procedure.
AMBIGSYMUSED
ambiguous symbol 'name' used as procedure parameter Facility: VAXTPU, VAX Text Processing Utility Explanation: The named symbol could be either an undefined procedure or a variable; its correct usage has not yet been determined. When an ambiguous symbol is used as a parameter in a call, the compiler is forced to generate nonoptimal code. User Action: Define the named symbol as either a procedure or a variable before using it as a call parameter.
AMBKEY
'keyword' is an ambiguous keyword Facility: LIB, Library Facility Explanation: Too few characters were used to truncate the keyword indicated to make it unique within its context. This message is associated with a status code returned from the VMS Run-Time Library. User Action: Reenter the keyword, specifying enough characters to make it unique.
AMBSYMDEF
ambiguous symbol definition Facility: LIB, Library Facility Explanation: The specified symbol name is ambiguous when compared with existing symbol names. This condition can occur when abbreviated symbols have been previously defined. User Action: Refer to the VMS DCL Dictionary for more information about abbreviated symbols.
ANI
not ANSI "D" format Facility: RMS, VMS Record Management Services Explanation: The records in a magnetic tape file do not conform to the ANSI standard for magnetic tape (D format). User Action: Modify the program that writes the magnetic tape file so that the file is in the correct format, or verify that the tape is an ANSI-labeled tape. If the tape is not in ANSI "D" format, use an alternative method of reading the file such as mounting the tape as a foreign tape or using VMS RMS block I/O.
AOP
allocation options error for area id = 'nnn' Facility: RMS, VMS Record Management Services Explanation: An allocation XAB for a $CREATE or $EXTEND operation specifies an invalid allocation option (AOP field). User Action: The status value (STV) field of the FAB provides the area identification of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
APPENDEDB
'input-filespec' appended to 'output-filespec' (nnn blocks) Facility: Shared by several facilities Explanation: An input file is being appended to an output file. This informational message displays the number of blocks or the number of records appended, based on the size of the input file. User Action: None.
APTREFHIGH
inconsistent active page table reference count Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
APTWRTERR
active page table swap write error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
AQBTIME
ACP queue is unstable Facility: MOUNT, Mount Utility Explanation: The system cannot start the ACP specified in the DCL command MOUNT request. This message indicates an error in the operating system software. User Action: Consult the system manager to determine what events in the system might be preventing ACPs from starting.
ARBTOOBIG
access rights block too big Facility: SYSTEM, VMS System Services Explanation: The access rights block (ARB) for the current process is too large to package and send to another subsystem. User Action: Have your system manager use the Authorize Utility to remove unnecessary rights identifiers from the process and reenter the command.
ARCHIVEDSB
archiving disabled Facility: AUDSRV, Audit Server Explanation: Archiving is disabled. User Action: None. This is an informational message.
ARCHIVEMOVE
archiving ending on: 'filename'; archiving starting on: 'filename' Facility: AUDSRV, Audit Server Explanation: Archiving has been successfully redirected to a new archive file. User Action: None. This is an informational message.
ARCHIVENEW
archiving starting on: 'filename' Facility: AUDSRV, Audit Server Explanation: Archiving has been successfully enabled to the specified archive file. User Action: None. This is an informational message.
ARCNOTDISK
archive file open failure; archiving is directed to an invalid device type Facility: AUDSRV, Audit Server Explanation: Archiving could not be enabled because the archive journal is not directed to a file-structured disk device. User Action: Redirect the archive journal to a file-structured disk device.
ARCOPENFAIL
archive file open failure (status: 'status') Facility: AUDSRV, Audit Server Explanation: The audit server could not open the system audit archive file. The specified status code indicates the exact cause of the problem. User Action: Correct the indicated error, and try again.
ARGMISMATCH
parameter 'numbers', 'data-type', and 'type' are unsupported Facility: VAXTPU, VAX Text Processing Utility Explanation: The data type of the indicated parameter is not supported by the built-in procedure that is being called. User Action: To find the correct data types for this built-in procedure, refer to the VAX Text Processing Utility Manual or to online help.
ARGREQ
missing argument - supply all required arguments Facility: CLI, Command Language Interpreter (DCL) Explanation: When you invoked a lexical function, you did not specify all the required arguments. User Action: Supply all the required arguments.
ARGTOOLONG
argument too long Facility: MACRO, VAX MACRO Assembler Explanation: An argument is more than 1000 characters long. User Action: Reduce the length of the argument.
ARTRES
reserved arithmetic trap at PC location, PSL = xxxxxxxx Facility: SYSTEM, VMS System Services Explanation: An unknown arithmetic exception has occurred. User Action: This message should not occur. If it does occur, inform the system manager. 'AS' required Facility: EDT, EDT Editor Explanation: You omitted the word as from the syntax in the DEFINE KEY command. User Action: Reenter the command specifying the correct syntax.
ASCEFCFER
error associating to UETP common event flag cluster Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error associated with the vector event flag cluster during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
ASCTOOLONG
ASCII string too long Facility: MACRO, VAX MACRO Assembler Explanation: Either the string in an .ASCIC directive is more than 255 characters or the string in an .ASCID directive is more than 65535 characters. User Action: Reduce the length of the string.
ASGNMNTSYN
assignment syntax error Facility: MACRO, VAX MACRO Assembler Explanation: A direct assignment statement contains a syntax error. User Action: Refer to the VAX MACRO and Instruction Set Reference Manual for information on syntax errors and correct the syntax error.
ASGNQUE
could not assign logical queue 'queue-name' to execution queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to assign the queue to another executor queue. This error changes the first queue into a logical queue. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade, or after the upgrade has completed, assign the logical queue to the execution queue using the DCL command ASSIGN.
ASSIGN
error assigning channel to 'device-name' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to assign a channel to the volume to be verified. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command line.
ASSIGN
error assigning channel to 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: The utility encountered an error while attempting to assign a channel to the device. User Action: Examine the associated message for a clue to the problem, correct the trouble, and reinvoke the utility.
ASSIGNFAIL
could not assign 'device' as system disk Facility: BACKUP, Backup Utility Explanation: Standalone BACKUP could not assign a channel to the disk from which it was booted. User Action: Determine why the channel assign failed. If possible, correct the problem and retry the BACKUP operation. Otherwise, submit a Software Performance Report including full configuration details and a log of the output.
ASTFLT
AST fault, SP = 'xxxxxxxx' param = 'xxxxxxxx', PC = location, PSL = 'xxxxxxxx', target PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: The system attempted to deliver an asynchronous system trap (AST) to an image, but the user stack pointer either is invalid or did not have sufficient space for the AST call frame. This message indicates an exception condition and is usually followed by a display of the condition arguments, the registers, and the stack at the time of the exception. User Action: Examine the parameters displayed in the message to determine the instruction that caused the error. Locate the programming error that modified the stack.
ASTRPDFER
error disabling Ctrl/C and Ctrl/Y AST reception Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
ASUSPECT
customer defined text Facility: LAVC, Local Area VAXcluster Explanation: The local area VAXcluster network failure analysis has located a network problem and reported this network component as suspect. User Action: Several PEDRIVER channels that were using this network component have failed. The analysis indicates that this component or something connected to it is likely to have caused the network problems. Have the system manager or network manager look into the network problem.
ASYNCACTIVE
journal file prohibited with asynchronous handlers declared Facility: VAXTPU, VAX Text Processing Utility Explanation: Creating a journal file is prohibited. Asynchronous action routine handlers have been declared. User Action: You must choose between journaling and action routines.
ASYNCWRTER
asynchronous write memory failure Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ATLINE
at line 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message indicates the line number of the error. User Action: None.
ATPC
at PC 'xxxxxxxx' Facility: Shared by several facilities Explanation: This message generally accompanies a message indicating a software failure. User Action: Take corrective action based on the accompanying messages.
ATPROCLINE
at line 'integer' of procedure 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: Line number of error in the procedure. User Action: None.
ATR
file attributes read error Facility: RMS, VMS Record Management Services Explanation: A read error occurred on a file header. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a system status code that provides additional information about the condition. Take corrective action based on this status code. Check the status of the device and repeat the request. The header block may be bad. If the error occurs on many files, the disk or drive may be bad. In that case, notify the system manager.
ATTACHED
terminal now attached to process 'process-name' Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is output by the DCL command ATTACH when it attaches to a process. User Action: None.
ATTCONSTO
attempt to continue from stop Facility: LIB, Library Facility Explanation: A condition handling routine attempted to continue from a call to LIB$STOP; that is, the routine attempted to continue from an error from which continuation is impossible by returning a successful completion status. User Action: Using the traceback information or PC displayed in the message, locate the condition handler that incorrectly tried to continue execution. Condition handlers can return success only for continuable errors and should return success only for errors that they have corrected. Otherwise, they should resignal the error. Attempt to CUT or APPEND to current buffer Facility: EDT, EDT Editor Explanation: While trying to perform a CUT or APPEND operation, you named the current text buffer as the destination text buffer. The default destination is the PASTE text buffer. User Action: Copy the text to an intermediate buffer. Attempt to PASTE the current buffer Facility: EDT, EDT Editor Explanation: The EDT command PASTE attempted to paste text into the same text buffer containing the text to be pasted. User Action: Copy the text to an intermediate buffer. Attempt to reenter EDT Facility: EDT, EDT Editor Explanation: While using callable EDT, you attempted to recall EDT without having exited. User Action: Exit from EDT before attempting to recall EDT.
ATTREQREF
attach request refused Facility: LIB, Library Facility Explanation: The specified process could not be attached to. Either it is not detached or it did not belong to the caller's job. User Action: Ensure that the specified process is detached and belongs to the caller's job.
ATW
file attributes write error Facility: RMS, VMS Record Management Services Explanation: A write error occurred during an attempt by VMS RMS to write a file header. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a status code that provides additional information about the condition. Take corrective action based on this status code. Check the status of the device and repeat the request. The header block may be bad. If the error occurs on many files, the disk or drive may be bad. Notify the system manager.
AUTOMEMCOPY
'device-name' automatically added to the shadow set with a copy operation Facility: MOUNT, Mount Utility Explanation: The /INCLUDE Mount qualifier was specified allowing members that were previously part of the shadow set to be automatically added to the set. The indicated device was successfully added to the shadow set. A copy operation was initiated making this device a target for all blocks. User Action: None.
AUTOMEMERGE
'device-name' automatically added to the shadow set with a merge operation Facility: MOUNT, Mount Utility Explanation: The /INCLUDE Mount qualifier was specified allowing members that were previously part of the shadow set to be automatically added to the set. The indicated device was successfully added to the shadow set with merge semantics. The device is identical to the other members of the set except for possible incomplete writes for which the shadowing software will check. User Action: None.
AUTOMEMSUCC
'device-name' automatically added to the shadow set Facility: MOUNT, Mount Utility Explanation: The /INCLUDE Mount qualifier was specified allowing members that were previously part of the shadow set to be automatically added to the set. The indicated device was successfully added to the shadow set as a consistent member. User Action: None.
AUTONOTSTART
queue is autostart active, but not started Facility: JBC, Job Controller Explanation: You tried to start an autostart queue when none of its available nodes has autostart enabled. User Action: Enter an ENABLE AUTOSTART [/QUEUES] command on the nodes in the queue's autostart node list.
AUTOSYNC
auto-answer file is not synchronized to the current question Facility: VMSINSTAL, Install Procedures Explanation: You have specified the auto-answer option, and VMSINSTAL is using the answers from an existing answer file. The question being asked by the installation procedure does not match the next question and answer in the answer file. User Action: The installation procedure has changed. Delete the existing answer file and begin the installation again.
BACKLINK
incorrect directory back link 'filespec' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The back link of the specified file did not contain the file identification of the directory file in which the file is cataloged. This condition is normal if the file is cataloged in more than one directory. User Action: Set the back link pointer to point to the directory file. If the file is cataloged in more than one directory, you may want to use the /CONFIRM qualifier to direct the Analyze/Disk_ Structure Utility not to repair the back link. Backup past top of buffer Facility: EDT, EDT Editor Explanation: You attempted to move the cursor to a position preceding the first line (top) of the buffer. User Action: Press any key to move the cursor below the top of the buffer.
BACKUPERR
an error has occurred in re-creating the save set Facility: VMSINSTAL, Install Procedures Explanation: A BACKUP error occurred while re-creating the save sets in the processing of the GET option. The operation is aborted. User Action: Make sure the specified output device holds media that is not write protected.
BADACC
unable to CREATE/UPDATE account named "name" Facility: VMSINSTAL, Install Procedures Explanation: The product being installed has tried to either create an account that already exists or modify a nonexistent account. User Action: If you can determine and resolve the problem, reinstall the product. Otherwise, contact the Digital Services Group.
BADACP
invalid syntax on /PROCESSOR qualifier Facility: MOUNT, Mount Utility Explanation: The keyword or file specification value specified for the /PROCESSOR qualifier is not specified correctly. User Action: Reenter the command; refer to the VMS DCL Dictionary for the correct syntax.
BADACTRL
remote access control info invalid
Facility: SMI, System Management Integrator/Server
Explanation: The SYSMAN user cannot be validated on the indicated
node due to one or more of the following reasons:
o The password is invalid.
o The user name (current or as overidden with a /USERNAME
qualifer) cannot be found in the remote system UAF.
o The remote system UAF cannot be accessed.
o The remote UAF record does not have either SETPRV or OPER
privileges authorized.
o The account is disabled.
User Action: Determine why the account is invalid on the remote
system by trying to log in directly with a DCL SET HOST command.
BADALORQSZ
bad memory allocation request size Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADARGS
unrecognized argument to procedure Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU error occurred. User Action: Submit a Software Performance Report (SPR).
BADASSIGN
target of the assignment cannot be a function/keyword Facility: VAXTPU, VAX Text Processing Utility Explanation: The left-hand side of an assignment statement must be a variable. It cannot be a procedure name or a keyword. User Action: Use a different variable name to the left of the operator : = in this assignment statement.
BADATTRIB
bad attribute control list Facility: SYSTEM, VMS System Services Explanation: An invalid code or size is specified in the read or write attribute list for a file system ACP QIO function. User Action: Check for a programming error. Begin debugging procedures to verify the source of the problem and to correct the problem. Note that when using ANSI magnetic tapes, the block size must be 4 bytes larger than the largest record in a variable record length file, and the largest record that can be written is 2048 bytes.
BADBITMAP
BITMAP.SYS too small or not contiguous, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The storage bit map file, [000000]BITMAP.SYS;1, on the specified relative volume is not large enough to accommodate the volume size and volume cluster factor, or that it is not contiguous. This error can result from an erroneous volume size in the storage control block or from an erroneous volume cluster factor in the home block. User Action: If the volume can no longer be mounted by the operating system, it is corrupted and must be reconstructed from backup media. If the volume can be mounted, the damage can be repaired by copying the volume to fresh media.
BADBLK
invalid option block Facility: CONVERT, Convert Utility Explanation: You have made an error in constructing the option block used in the CONV$PASS_OPTIONS routine. User Action: Refer to the VMS System Services Reference Manual for instructions on building an option block.
BADBLKSIZE
'save-set-spec' has inconsistent block size Facility: BACKUP, Backup Utility Explanation: The volume mounted as a continuation volume of a multivolume save set is not recorded with the same block size as previous volumes of the save set. This volume is probably not part of the same save set. User Action: Locate and mount the correct continuation volume.
BADBLOADR
bad block address Facility: LIB, Library Facility Explanation: The library routine LIB$FREE_VM is called with an invalid virtual storage address. User Action: Begin debugging procedures to verify the problem and to correct the problem.
BADBLOCK
bad blocks on 'device-name' do not match input Facility: BACKUP, Backup Utility Explanation: In a COPY or RESTORE operation with the /PHYSICAL qualifier, a bad block is present on the output volume in a location where the input volume had a good block. The backup operation will not result in a valid Files-11 volume. User Action: Reevaluate the operation; another mode of operation, such as the /IMAGE qualifier, may be appropriate. Or retry the operation using either the original input volume or an error-free output volume.
BADBLOCKS
invalid syntax in bad block list Facility: INIT, INITIALIZE Command Explanation: The command syntax for the /BAD_BLOCKS qualifier is invalid. User Action: Reenter the command; use the DCL command HELP or refer to the VMS DCL Dictionary for the correct syntax. If the list of blocks is long, place the command in a command procedure file.
BADBLOSIZ
bad block size Facility: LIB, Library Facility Explanation: Either the library routine LIB$GET_VM is called with a request for zero blocks or the requested block size is too large. User Action: If the requested block size is zero, correct the source program. If the specified block size is too large, use the DCL command SET WORKING_SET to increase the current working set limit for your process and retry the program.
BADBOOTCB
corrupted Boot Control Block Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADBUFADR
ACP buffer address out of range of buffer pool Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADBUFTYP
bad ACP buffer type code Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADBUFWRITE
error occurred writing buffer 'buffer name' Facility: VAXTPU, VAX Text Processing Utility Explanation: An I/O error occurred while writing the the contents of the buffer to a file. This could be due to operating system or VMS RMS errors. This message should be accompanied by another message specifying the reason for the error. The creation of the file stopped at the point of the error. User Action: Correct the specified problem and reenter your command.
BADBUG
please report TRACE bug no. 'nnn' Facility: TRACE, Traceback Facility Explanation: This message indicates an internal programming error in the Traceback Facility. User Action: Collect as much information as possible and submit a Software Performance Report; include the bug number (nnn) displayed in the message.
BADBYTE
invalid data ('xx') at 'location'
Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: None.
BADCACHE
invalid syntax on /CACHE qualifier Facility: MOUNT, Mount Utility Explanation: The options given with the /CACHE qualifier have invalid syntax. User Action: Verify the command and reenter the correct syntax.
BADCASE
unrecognized CASE constant Facility: VAXTPU, VAX Text Processing Utility Explanation: Case constants can only be integers, keywords, or 1-character strings. User Action: Check your case labels or your FROM . . . TO limits to ensure that the case constants follow the stated rules.
BADCASELIMIT
CASE constant outside of CASE limits Facility: VAXTPU, VAX Text Processing Utility Explanation: A case constant used as a case label (inside [ . . . ]) does not fall within the range specified by the FROM . . . TO limits of your case statement. User Action: Modify your CASE limits or correct the case labels and recompile your program.
BADCASERANGE
invalid CASE range Facility: VAXTPU, VAX Text Processing Utility Explanation: Either the case range or at least one case selector other than INRANGE or OUTRANGE must be specified. User Action: Specify a case range or specify at least one case selector other than INRANGE or OUTRANGE.
BADCCC
bad compilation completion code ('decimal-number') in module
'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An illegal compilation completion code is found in
the specified module.
User Action: Recompile the module and relink.
BADCCC
illegal compilation code 'code' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an internal error in the operating system, submit a Software Performance Report (SPR).
BADCHAR
unrecognized character in input Facility: VAXTPU, VAX Text Processing Utility Explanation: A control character or some other character that is not recognized by the parser exists in the program you are trying to compile. User Action: Remove the unrecognized character and recompile your program.
BADCHECKSUM
message checksum failure Facility: SYSTEM, VMS System Services Explanation: A VAXcluster node has received a service request that contains user or object security profile information with questionable data integrity. The request cannot be serviced without potentially compromising system security. User Action: Contact the Digital Services Group or file a Software Performance Report (SPR).
BADCHKSUM
bad file header checksum Facility: SYSTEM, VMS System Services Explanation: The checksum in the file header is invalid or the file header may be corrupt. User Action: Repair the volume using the Analyze/Disk_Structure Utility. Recover the file from the backup medium.
BADCHKSUM
shared memory data structures corrupted - reinitialization necessary Facility: SYSGEN, System Generation Utility Explanation: A CRC check of the constant fields in the shared memory datapage has detected an error. User Action: Reboot all processors using the shared memory.
BADCONDEV
please specify an existing console device. Facility: VMSINSTAL, Install Procedures Explanation: The device you specified is not a console device. User Action: Specify a valid console device.
BADCOPIES
'nnn' is an invalid number of copies Facility: Shared by several facilities Explanation: The number of copies is not within a valid range. User Action: Reenter the command; specify a different number of copies.
BADCSP
scope setting not module or routine Facility: PATCH, Patch Utility Explanation: The symbol specified as the new scope value is not a module name or routine name. User Action: Reenter the command using the corrected scope value.
BADCTLMSK
bad control character enable/disable mask Facility: CLI, Command Language Interpreter (DCL) Explanation: You specified a control character sequence other than Ctrl/T or Ctrl/Y to enable or to disable a mask. User Action: Specify Ctrl/T or Ctrl/Y to enable or to disable the mask.
BADDALRQSZ
bad memory deallocation request size or address Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADDATA
error in block 'nn' of 'filespec' detected during save Facility: BACKUP, Backup Utility Explanation: A read error for the specified block of the specified file occurred when the save set is created. Data in this block may be corrupted. User Action: Examine the file for corruption and reconstruct as necessary. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility. In this case, submit a Software Performance Report (SPR).
BADDATCHK
invalid keyword on /DATACHECK qualifier Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The keyword specified for the /DATACHECK qualifier is neither READ nor WRITE. User Action: Reenter the command; specify either READ or WRITE.
BADDATDAT
data echoed invalid Facility: DTS, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test.
BADDATLEN
not enough data sent/received Facility: DTS, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test.
BADDELETE
cannot modify constant integer, keyword or string Facility: VAXTPU, VAX Text Processing Utility Explanation: You are attempting to modify an integer, keyword, or string constant. User Action: Check your program for this error and remove the problem statement.
BADDELIM
invalid delimiter following 'command' Facility: Shared by several facilities Explanation: An invalid character was entered as part of a command. This message displays the rejected portion of the command. User Action: Check the command for a spelling or syntax error; reenter the command.
BADDENS
unknown value on /DENSITY qualifier Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The value specified for a tape density is not 800, 1600, or 6250. The value specified for a diskette is not single or double. User Action: Reenter the command; specify either 800, 1600, or 6250 for the density.
BADDEV
device is unsupported for transfer Facility: EXCHNET, EXCHANGE/NETWORK Command Explanation: You attempted to transfer the file either to or from a device that is not supported by the device (such as magnetic tape). User Action: Correct an error in the device specification or try using a different device.
BADDIR
bad directory spec - should be dev:[dir] Facility: SMI, System Management Integrator/Server Explanation: A SYSMAN SET PROFILE/DEFAULT command specified an invalid device or directory, or both. User Action: Correct the directory specification according to the VMS DCL Concepts Manual.
BADDIR
directory 'directory' has invalid format Facility: BACKUP, Backup Utility and ANALDISK, Analyze/Disk_ Structure Utility Explanation: The specified directory file is not in the expected format for a directory file. The file is corrupted. User Action: Use the DCL command SET FILE/NODIRECTORY to delete the corrupted directory file. Then use the DCL command ANALYZE /DISK_STRUCTURE /REPAIR to place the lost files in the [SYSLOST] directory. You can then copy the lost files to a new directory.
BADDIRENT
invalid file identification in directory entry 'filespec' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The specified directory entry does not contain a valid file identification. Probably the file has been deleted. The directory entry is removed. User Action: None.
BADDISDEV
please specify a disk or tape device Facility: VMSINSTAL, Install Procedures Explanation: You specified a device on which to mount the distribution media that is neither a disk nor a tape. User Action: Specify a disk or tape device.
BADDISDIR
directory "directory-name" does not exist Facility: VMSINSTAL, Install Procedures Explanation: You are trying to restore the distribution kit from a nonexistent directory. User Action: Specify the correct directory when you start VMSINSTAL.
BADDST
no symbols in image Facility: TRACE, Traceback Facility Explanation: The image header in an executable image file does not contain symbols required by the Traceback Facility. The message indicates an operating system problem. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADDSTMAP
failure to map symbol table, CREMAPSEC status = 'xxxxxxxx' Facility: TRACE, Traceback Facility Explanation: The system could not perform a symbolic traceback because the system could not map the symbol table. The hexadecimal status code is the return status from an internal call to the Create and Map Section ($CRMPSC) system service. User Action: Determine the reason associated with the indicated status code. If the reason is anything other than a lack of virtual address space, assume that the problem is a system problem. Collect as much information as possible and submit a Software Performance Report (SPR).
BADDSTVBN
image symbol table VBN = 'nnn' Facility: TRACE, Traceback Facility Explanation: The Traceback Facility cannot interpret the image header for an executable file. This message indicates an internal operating system error or an error in the linker. User Action: Collect as much information as possible and submit a Software Performance Report; include the virtual block number (VBN) number (nnn) displayed in the message.
BADECO
illegal eco level of 'nn' in 'filespec' Facility: PATCH, Patch Utility Explanation: An illegal ECO level is specified. The legal ECO level range is between 1 and 128, inclusive. User Action: Retry using a legal ECO level.
BADEFBLK
file ('file-id') 'filename' inconsistent EFBLK and map area
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The end-of-file pointer recorded in the VMS RMS
record attributes for the specified file does not lie within the
space actually allocated to the file.
User Action: None. The utility sets the end of file pointer to
point to the end of the allocated space.
BADENTRY
bad format for .ENTRY statement Facility: MACRO, VAX MACRO Assembler Explanation: The .ENTRY directive did not specify an entry point name and a correct entry mask. User Action: Correct the .ENTRY directive syntax.
BADESCAPE
syntax error in escape sequence Facility: SYSTEM, VMS System Services Explanation: A terminal escape sequence is invalid. This message is associated with a status code returned by I/O functions. User Action: Check for a programming error. Correct the escape sequence syntax.
BADEVTYP
bad device type, 'value' in text library module, 'module-name' Facility: ERF, Error Log Utility Explanation: A value in the specified library module is out of the required range. User Action: Submit a Software Performance Report (SPR).
BADEVVAL
bad device table value, 'value' in text library module, 'module-name' Facility: ERF, Error Log Utility Explanation: A value in the specified library module is out of the required range. User Action: Submit a Software Performance Report (SPR).
BADEXCL
directory or device not allowed in /EXCLUDE = exclude-item Facility: SEARCH, SEARCH Command Explanation: The listed exclude item contains a network node name, a device name, or a directory name. User Action: Reenter the command, specifying only a file name, a file type, and a version number
BADEXCLNAM
invalid filename in /EXCLUDE = exclude-item Facility: SEARCH, SEARCH Command Explanation: The listed exclude item is not a valid VMS RMS file specification. User Action: Reenter the command with a correct file specification.
BADEXE
failure to open image file 'filename' Facility: TRACE, Traceback Facility Explanation: The operating system rejected the format of the indicated executable image file. The file cannot be opened. This message indicates an internal operating system error. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADEXECLO
failure to close image file 'filename' Facility: TRACE, Traceback Facility Explanation: The operating system rejected the format of the indicated executable image file. The file cannot be closed. This message indicates an internal operating system error. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADEXERAB
failure to connect image file 'filename' Facility: TRACE, Traceback Facility Explanation: The operating system rejected the format of the indicated executable image file. This message indicates an internal operating system error. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADEXITIF
EXITIF occurs outside of a LOOP Facility: VAXTPU, VAX Text Processing Utility Explanation: An EXITIF statement must be inside the boundaries of LOOP . . . ENDLOOP statements. User Action: Remove EXITIF statements that do not follow the stated rule.
BADFID
ACP file number out of range for this volume Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADFIELD
'name' field invalid at 'location' Facility: Shared by several facilities Explanation: The specified data is invalid at the given location. User Action: Retry the operation. If the error persists, submit a Software Performance Report (SPR).
BADFILE
invalid startup file name Facility: STDRV, System Startup Driver Explanation: The named startup component file name is invalid. The specific reason for the error is printed before this message. User Action: Use the STARTUP MODIFY FILE command at the SYSMAN> prompt to correct the file name.
BADFILEHDR
bad file header Facility: SYSTEM, VMS System Services Explanation: The file header has failed validity checks and is corrupted. User Action: Repair the volume using the Analyze/Disk_Structure Utility and recover the file from backup media.
BADFILENAME
bad file name syntax Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned from a file system ACP QIO request. The file name string for a file specification contains illegal characters or is longer than 39 characters. User Action: Check for a programming error. Verify that the file name strings consist only of the characters A through Z and 0 through 9, and are no longer than 9 characters.
BADFILENAME
name 'filename' not suitable for 'volume-type' volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility is given a file name that is not in the correct format for the target volume type. User Action: Reenter the command, using a valid file name for the volume shown in the message.
BADFILEVER
bad file version number Facility: SYSTEM, VMS System Services Explanation: The message indicates that the file version number in a file specification is greater than 32767 or contains nonnumeric characters. Or the file system may have attempted to create a file with a version higher than 32767 through defaulting rules. User Action: Check for a programming error. Verify that existing file versions are less than 32767. Rename if necessary.
BADFIRSTLINE
first line = 'integer', must be between 'integer' and 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: You gave a first line argument to the built-in procedure CREATE_WINDOW that is outside the physical screen limits. User Action: Pick a valid first line value (between 1 and pagelength) and reenter your command.
BAD_FIXUPVEC
the fixup vector contains inconsistent data Facility: IMGACT, Image Activator Explanation: There are inconsistencies in the structure of the fixup vector in the image. This usually indicates a corrupted or invalid image. User Action: Relink the image.
BADFLAG
bad enable/disable flag Facility: STDRV, System Startup Driver Explanation: The enable/disable flag describing how the list of nodes associated with a startup component file should be used is invalid. User Action: Use the SYSMAN command STARTUP ENABLE/DISABLE to modify this entry in the startup component file.
BADFORKIPL
bad FORK exit interrupt priority level Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADFORM
'form-type' is an invalid form type Facility: Shared by several facilities Explanation: The form type specified with the /FORMS qualifier is not one of the forms defined as follows: SYS$SYSROOT:[SYSMGR]FORMSTYPE.DAT.l User Action: Respecify the form type with a valid form name.
BADFORM
invalid option for /FORMAT = 'format-option' Facility: SEARCH, SEARCH Command Explanation: The option given for the /FORMAT qualifier is not valid. This message is issued with an accompanying message providing more information about why the format option is not acceptable. User Action: Reenter the command using one of the valid format options.
BADFORMAT
format version mismatch in file 'filespec' Facility: Shared by several facilities Explanation: The specified file is not formatted as expected. User Action: Verify that you specified the correct file.
BADFRMT
volume is not mounted with Files-11 format Facility: SET, SET Facility Explanation: The volume is mounted with the /FOREIGN qualifier; it cannot be modified. User Action: None.
BADFUNC
invalid function type received Facility: DTR, DECnet Test Program Protocol Explanation: The DECnet-VAX test program has a protocol incompatibility. User Action: Run the test against a compatible version of DTRECV or an equivalent.
BADGETDIR
directory 'directory-name' does not exist. Facility: VMSINSTAL, Install Procedures Explanation: You are trying to copy the specified product save set to a nonexistent directory. User Action: Specify the correct directory when you start VMSINSTAL.
BADGETJPI
unable to read process information Facility: LAT, LAT Facility Explanation: LATCP was unable to read process information before doing a SPAWN command. User Action: Take appropriate action based on information in the accompanying message.
BADGSD
unknown type of GSD entry: 'GSD' Facility: SDA, System Dump Analyzer Explanation: SDA encountered a type of global symbol that it does not recognize, either in the SYS.STB file or in a file specified in the SDA command READ. The type of global symbol definition GSD is represented by a byte. User Action: This message can occur during either initialization or operation of the SDA and usually means that the file being read has been corrupted. Check the integrity of the symbol table file.
BADHDR
an error is discovered in the image header Facility: IMGACT, Image Activator Explanation: The image header type word contains an invalid type code. This usually indicates a corrupted or invalid image. User Action: Relink the image.
BADHDR
no symbol table data in image header Facility: TRACE, Traceback Facility Explanation: The image header in the executable image file does not contain expected symbol table data. This message indicates an internal operating system error. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADHEADER
file ('file-id') 'filename' invalid file header
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file header is corrupt.
User Action: The file is rewritten with a deleted file header.
If the specified file header is currently in use, the file
can no longer be accessed by the operating system and must be
reconstructed from backup media. If the file header is not in use,
no action is necessary.
BADHIBLK
file ('file-id') 'filename' inconsistent HIBLK and map area
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The file size recorded in the VMS RMS record
attributes does not agree with the number of blocks actually
allocated to the file.
User Action: None. The utility corrects the record attributes by
changing the file size to reflect the correct number of blocks.
BADHOMBLK
bad home block encountered on volume Facility: MOUNT, Mount Utility Explanation: An I/O error occurred while reading a home block during /BIND processing. A subsequent message explains the nature of the error. The first occurrence of this message is a warning; the second is fatal. User Action: Repair using the Analyze/Disk_Structure Utility or reinitialize the volume and retry the operation.
BADIDENT
unable to patch image with ident of 'nn' Facility: PATCH, Patch Utility Explanation: PATCH does not recognize this version of the image file. User Action: Relink your image file. Ensure that the file being patched is a native mode image file.
BADIF
IF statement contains an assignment statement Facility: VAXTPU, VAX Text Processing Utility Explanation: The IF expression in an IF . . . THEN statement must contain logical operators only. This message is likely to occur if you used the expression x: = y instead of the the Boolean expression x = y. The IF expression in an IF . . . THEN statement makes a logical comparison. User Action: Change the operator : = to the operator =.
BADIMGHDR
bad image header Facility: SYSTEM, VMS System Services Explanation: An image to be executed with the DCL command RUN or within a process is not in the correct format and cannot be executed. User Action: Verify that the specified file is an executable image. If necessary, recompile or reassemble and relink the program to ensure that the image file is in the proper format.
BADIMGHDR
bad image header in shareable image file 'filename' Facility: LINK, Linker Utility Explanation: A shareable image contains a bad image header, or the file is not a shareable image. User Action: Correct and relink.
BADINDEX
invalid syntax on /INDEX qualifier Facility: INIT, INITIALIZE Command Explanation: The command syntax for the /INDEX qualifier is invalid. User Action: Reenter the command; use the DCL command HELP or refer to the VMS DCL Dictionary for the correct syntax.
BADINITSZ
illegal size value defaulting patch size to 'xxxxxxxx' bytes Facility: PATCH, Patch Utility Explanation: The size-expression input argument did not fall within the valid range. PATCH set the patch area to the address named in the SET PATCH_AREA command, and use the default patch area size to build the patch area descriptor. User Action: Continue to enter patches into the user-defined patch area. To see the current status of the patch area, enter the SHOW PATCH_AREA command.
BADIONAME
'name' has not been previously defined Facility: CDU, Command Definition Utility Explanation: There is an undefined name in the output list. User Action: Check the spelling of the name in the output list.
BADIRECTORY
bad directory file format Facility: SYSTEM, VMS System Services Explanation: The message indicates that the specified directory file is not valid. Either the file is not a directory or the directory file contains invalid data. User Action: Check for a programming error. Verify that the specified file is a directory. If necessary, repair the volume using the Analyze/Disk_Structure Utility.
BADISD
illegal image section descriptor Facility: SYSTEM, VMS System Services Explanation: This severe error message is associated with a status code returned from a system service request. An illegal image section descriptor is encountered. User Action: This file may be corrupted or may not be an executable image. There also may be a problem associated with the linker; in this case, submit a Software Performance Report (SPR).
BADITMPROC
failed to process item code 'hex-number' correctly Facility: QMAN, Queue Manager Explanation: The queue manager encountered an internal error. When this error message occurs, a user request terminates with an INVITMCOD error. User Action: Submit a Software Performance Report (SPR) and include the item code number cited in the message.
BADJOBID
'job-id' is an invalid job identifier Facility: Shared by several facilities Explanation: The job identifier specified by the /ENTRY qualifier is missing or not valid. User Action: Respecify a valid job identifier by using the DCL command SHOW QUEUE.
BADJOBNAME
'job-name' is an invalid job name Facility: Shared by several facilities Explanation: The job name specified by the /NAME qualifier is missing or not valid. User Action: Respecify the job name with one of the job names listed in the DCL command SHOW QUEUE.
BADJOUCHAR
expected character in journal file Facility: VAXTPU, VAX Text Processing Utility Explanation: Something other than a character is found in the journal file when a character is expected. User Action: If the recovered information is sufficient, resume editing from this point. VAXTPU has recovered as much as it can from your journal file.
BADJOUCOM
journaled command file is 'filename', recovering with 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different command file than is used during the original editing session. User Action: Stop the recovery session, and restart using the correct (the original) section and command files.
BADJOUCPOS
journaled starting character was 'character number', recovering with 'original character number' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different starting character number than was used during the original editing session. User Action: Stop the recovery session, and restart it using the original starting character number.
BADJOUEDIT
journaled edit mode was 'mode-setting', recovering with 'original mode-setting' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different edit mode setting than was used during the original editing session. User Action: Stop the recovery session, and reset the terminal characteristics to those used in the original editing session.
BADJOUEIGHT
journaled eightbit was 'eightbit setting', recovering with 'original eightbit setting' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different 8-bit setting than was used during the original editing session. User Action: Stop the recovery session, and reset the terminal characteristics to those used in the original editing session.
BADJOUFILE
operation terminated due to error in journal file access Facility: VAXTPU, VAX Text Processing Utility Explanation: The journal file operation stopped because the journal file could not be accessed. User Action: Correct the problem preventing access to the journal file and try again.
BADJOUINIT
journaled init file was 'init-filename', recovering with 'original- init-filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different initialization file than was used during the original editing session. User Action: Stop the recovery session, and restart it using the original initialization file.
BADJOUINPUT
journaled input file was 'input-filename', recovering with 'original-input-filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different input file than was used during the original editing session. User Action: Stop the recovery session, and restart it using the original input file.
BADJOUKEY
expected key in journal file Facility: VAXTPU, VAX Text Processing Utility Explanation: Something other than a key is found in the journal file when a key is expected. User Action: If the recovered information is sufficient, resume editing from this point. VAXTPU has recovered as much as it can from your journal file.
BADJOULINE
journaled with line editing 'string', recovering with line editing 'string' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different line editing setting than is used during the original editing session. User Action: Stop the recovery session and reset the terminal characteristics to those used in the original editing session.
BADJOULPOS
journaled starting line was 'line-number', recovering with 'original-line-number' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different starting line number than was used during the original editing session. User Action: Stop the recovery session, and restart it using the original starting line number.
BADJOUPAGE
journaled page length is 'integer', recovering with page length 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different page length than was used during the original editing session. User Action: Stop the recovery session, and reset the terminal characteristics to those used in the original editing session.
BADJOUSEC
journaled section is 'string', recovering with 'string' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different section file than was used during the original editing session. User Action: Stop the recovery session, and restart it using the correct (original) section file.
BADJOUSTR
expected string in journal file Facility: VAXTPU, VAX Text Processing Utility Explanation: Something other than a string is found in the journal file when a string is expected. User Action: If the recovered information is sufficient for your needs, resume editing from this point. VAXTPU has recovered as much as it can from your journal file.
BADJOUTERM
journaled terminal type was 'string', recovering with a 'string' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a terminal different from that used in the original editing session. This might result in journal file inconsistencies. User Action: Stop the recovery session and reset the terminal characteristics to those used in the original editing session.
BADJOUWIDTH
journaled width is 'integer', recovering with width 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: The editing session is being recovered with a different screen width than was used during the original editing session. User Action: Stop the recovery session and reset the terminal characteristics to those used in the original editing session.
BADJRNL
invalid syntax on /JOURNAL qualifier Facility: MOUNT, Mount Utility Explanation: You have entered the wrong command line syntax. User Action: Correct the syntax and reenter.
BAD_KEY
invalid key specification Facility: SORT, Sort/Merge Utility Explanation: The key field size, position, data type, or order is incorrect within the key definition. Positions start at 1 and cannot be greater than the maximum record size. Record size must be less than or equal to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less than or equal to 31 for decimal. User Action: Check the command string key specifiers.
BADKEY
illegal key Facility: LIBRAR, LIBRARY Command Explanation: This severe error message is generated by the DCL command LIBRARY. The specified module is illegal. User Action: Reenter the command line specifying a legal module.
BADKEY
'keyword' is an invalid keyword Facility: Shared by several facilities Explanation: An invalid keyword was specified. The message displays the rejected portion of the command. User Action: Check the command for a spelling or syntax error. Use the DCL command HELP or refer to the VMS DCL Dictionary for the valid keywords and reenter the command.
BADKEY
'keyword' is an invalid keyword Facility: VAXTPU, VAX Text Processing Utility Explanation: An invalid keyword was specified as an argument to a built-in procedure. User Action: Correct the statement and reexecute the procedure.
BADLABELQ
invalid keyword on /LABEL qualifier Facility: INIT, INITIALIZE Command Explanation: An invalid keyword is specified with the /LABEL qualifier. The only keyword compatible with the /LABEL qualifier is shown as follows: /LABEL=VOLUME_ACCESSIBILITY:"single-character" User Action: Specify the following keyword and retry: =VOLUME_ACCESSIBILITY:"single-character"
BADLCKWSLE
bad locked working set list entry, not a page table Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADLEXARG
illegal lexical function argument Facility: MACRO, VAX MACRO Assembler Explanation: The argument to a macro string operator is invalid. String arguments can be macro arguments or strings delimited by angle brackets or the circumflex delimiters. Symbol arguments can be absolute symbols or decimal integers. User Action: Correct the argument syntax.
BADLEXFORM
illegal format for lexical function Facility: MACRO, VAX MACRO Assembler Explanation: The macro string operator contained a syntax error. User Action: Correct the macro string operator syntax.
BADLOGIC
internal logic error detected Facility: Shared by several facilities Explanation: This message indicates an internal software error. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BADLOGIC
internal logic error detected, please report error 'errorcode' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an unexpected condition and terminated. User Action: Submit a Software Performance Report (SPR), describing the error number and the commands that resulted in the message. If the error is only reproducible using a particular piece of media, please send a copy of the media with the SPR (use the BACKUP/PHYSICAL command to make the copy).
BADLOGICPC
internal logic error detected at PC 'location' Facility: Shared by several facilities Explanation: An internal error has occurred; the location field contains the value of the PC at the time the error is detected. The assembler does not produce an object module or listing file. User Action: Retry the operation. If the error is reproducible, notify your system manager and submit a Software Performance Report (SPR); include the address displayed with the error message and the source program.
BADLOGVER
transaction log file format version is unsupported Facility: SYSTEM, VMS System Services Explanation: The format of the transaction log file is not supported. User Action: Use the LMCP facility to create a new transaction log file.
BADLONG
invalid data ('xxxxxxxx') at 'location'
Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: None.
BAD_LRL
record length n greater than specified longest record length Facility: SORT, Sort/Merge Utility Explanation: In reading the input file, SORT encountered a record longer than the specified LRL (longest record length specified in bytes). The record will be truncated to the LRL and sorted. User Action: Reexecute the SORT command with a longer LRL.
BADMARGINS
margins specified incorrectly Facility: VAXTPU, VAX Text Processing Utility Explanation: The margin arguments passed to FILL or SET (MARGINS, . . . ) are invalid. The left margin must be less than the right margin and greater than 0. The right margin must be less than or equal to the maximum record size for the buffer. User Action: Correct the margin specifications and reenter your command.
BADMATCH
invalid option for /MATCH = match-option Facility: SEARCH, SEARCH Command Explanation: The option specified for the /MATCH qualifier is not valid. This message is issued with an accompanying message providing more information about why the match option is not acceptable. User Action: Reenter the command using one of the valid match options.
BADMCKCOD
bad machine check code Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and that includes a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADMODE
invalid mode for startup file Facility: STDRV, System Startup Driver Explanation: A startup component file in the startup component database has an execution mode that is not DIRECT, BATCH, CALLED, SPAWN, or ANY. User Action: To correct the component execution mode, use the STARTUP MODIFY FILE command at the SYSMAN> prompt.
BADMODNAM
bad module name key 'key-name' Facility: ERF, Error Log Utility Explanation: The specified library module was not found. User Action: Submit a Software Performance Report (SPR).
BADMOPFCT
bad MOP function received from target Facility: MOM, Maintenance Operation Module Explanation: A MOP message is rejected because the MOP Code field contains an invalid value. User Action: Correct the MOP Code field in the device transmitting the MOP message.
BADMOPPGM
bad MOP program type received from target Facility: MOM, Maintenance Operation Module Explanation: A MOP message is rejected because the MOP Program Type field contains an invalid value. User Action: Correct the MOP Program Type field in the device transmitting the MOP message.
BADMOPPROC
bad MOP processor type received from target Facility: MOM, Maintenance Operation Module Explanation: A MOP message is rejected because the MOP Processor field contains an invalid value. User Action: Correct the MOP Processor field in the device transmitting the MOP message.
BADMOPSID
bad MOP software ID received from target Facility: MOM, Maintenance Operation Module Explanation: A MOP message is rejected because the MOP Software ID field contains an invalid value. User Action: Correct the MOP Software ID field in the device transmitting the MOP message.
BADMOPVER
incompatible MOP version Facility: MOM, Maintenance Operation Module Explanation: A MOP message is rejected because the MOP Format Version field contains an invalid value. User Action: Correct the MOP Format Version field in the device transmitting the MOP message.
BADMSG
invalid management message Facility: NCP, Network Control Program Explanation: The form of the data from NML could not be parsed correctly. The information accompanying this message explains the reason. User Action: Use the SET EXECUTOR NODE command to reestablish a link for the executor because the reception of messages might be out of synchronization with NML.
BADMSG
unknown sub-message type Facility: REM, Set Host Facility Explanation: This message indicates an internal software error. User Action: Submit a Software Performance Report (SPR).
BAD_NAME
unable to repair log with invalid name format Facility: LMCP, Log Manager Control Program Explanation: A log repair could not be performed on the specified log file either because the file does not exist in the SYS$JOURNAL directory or because the file is not named using the convention SYSTEM$node-name. User Action: Refer to the VMS Version 5.5 New Features Manual for information about naming and placing log files.
BADNODFORM
improper node::remoteuser format Facility: AUTHORIZE, Authorize Utility Explanation: You specified the format for the remote node and user incorrectly. The correct format consists of a node name, a pair of colons (::), and the user name of the remote user. A node name may consist of one to six alphanumeric characters and must contain at least one alphabetic character. If you use a wildcard character for either the node or user, you must still include the pair of colons. User Action: Reenter your command with the correct format.
BADOFFSET
image header offset is invalid Facility: IMGACT, Image Activator Explanation: One of the offsets within the image header to specific parts of the image header is invalid. This usually indicates a corrupted or invalid image. User Action: Relink the image.
BADOPCODE
opcode 'xx' is unrecognized Facility: PATCH, Patch Utility Explanation: You specified an instruction that PATCH did not recognize. Note: PATCH does not accept abbreviations for instructions. For example, ADDL cannot be substituted for ADDL2. User Action: Reenter the corrected command.
BADOPEN
unable to locate BOOT file Facility: VAXCLUSTER, VAXcluster Facility Explanation: SYSBOOT.EXE is not found or is not accessible in the specified satellite system root directory. User Action: Check the satellite system root for the file and verify that it has the proper protection.
BAD_ORDER
merge input is out of order Facility: SORT, Sort/Merge Utility Explanation: A MERGE input file is not in order on the specified key. In this message, 'number' refers to the number of the input file in the list of input files. User Action: Sort the specified file and resubmit the file to MERGE.
BADOUTBAND
invalid out of band AST specification Facility: REM, Set Host Facility Explanation: A protocol error has occurred. User Action: Submit a Software Performance Report (SPR).
BADOVR
unknown keyword on /OVERRIDE qualifier Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The command syntax for the /OVERRIDE qualifier is invalid. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for the legal keywords, and reenter the command.
BADPAD
bad format for PAD keyword on /RECORD_FORMAT qualifier Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility found an invalid value in the PAD option of the /RECORD_FORMAT qualifier. User Action: Reenter the command using a correct format for /RECORD_FORMAT=PAD, such as /RECORD_FORMAT=PAD=%XFF.
BADPAGFILA
bad page file address allocated Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADPAGFILD
bad page file address deallocated Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADPAGTYPE
bad page type Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADPARAM
bad parameter Facility: LBR, Librarian Subroutine Package Explanation: An illegal value is passed to an LBR routine. User Action: Check the values being passed and correct the illegal value.
BADPARAM
bad parameter value
Facility: SYSTEM, VMS System Services
Explanation: A value specified for a system function is not valid.
Several conditions can cause this error:
1. If this message occurs as a result of a call to a file system
ACP function, it indicates that parameter list options are not
valid.
2. If this message occurs as a result of a call to the Formatted
ASCII Output ($FAO) system service, it indicates that a control
string contained an unknown directive.
3. If this message occurs as a result of a call to a network
ACP control function, it indicates that one of the function
parameters is out of range or has an invalid format.
4. If this message is associated with a status code returned by
a request to a DR32 interface, an attempt is made to set the
data rate higher than the rate allowed by the SYSGEN parameter
/XFMAXRATE.
5. If this message is associated with a status code returned by
a request to a standard XADRIVER, an odd transfer count is
specified by the P2 argument.
6. If this message is associated with a status code returned by
a request to a DMP11 interface, the parameter code that is
rejected is given in the second longword of the IOSB. The
parameter could have been rejected for one of the following
reasons: (a) the parameter is not recognized, (b) the
parameter value is not legal, or (c) the state is inconsistent
with the parameter value requested.
7. If this message is associated with turning on fallback,
fallback may not be loaded or the virtual terminal may be
disconnected. Reconnect the virtual terminal and enter the
request again. If the FB driver is not loaded, ask your system
manager to enable fallback.
User Action: Using the debugger if necessary, determine the system
service call that returned the error. Verify that the call to
the service is coded correctly. Refer to the VMS System Services
Reference Manual for coding specifications.
BADPARAM
improperly coded NML parameter Facility: EVL, Event Logger Explanation: The event receiver detected an improperly coded NML parameter. User Action: None. The parameter is not displayed.
BADPARAM
insufficient shared memory to create specified data structures Facility: SYSGEN, System Generation Utility Explanation: The sum of all the data structures specified is more than the available amount of shared memory. User Action: Recalculate memory usage and reenter the command.
BADPARAM
parameter to DECthreads operation is invalid Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A parameter passed to a DECthreads routine is improper; for example, the value is of the wrong type or is out of range. User Action: Determine which routine raised the exception. Then consult the documentation to determine the correct parameters and value ranges. Update your code accordingly and retry the operation.
BADPARAM
unable to find load assist parameter Facility: VAXCLUSTER, VAXcluster Facility Explanation: Parameters defined in the MOP downline load database or the satellite's SYSGEN parameter file, VAXVMSSYS.PAR, were not set properly. User Action: Check the MOP database using the NCP command SHOW NODE 'node-name' CHAR and check the SYSGEN parameters for the satellite with the SYSGEN command SHOW/CLUSTER.
BADPARSETBL
internal error - invalid parsing table detected Facility: MOM, Maintenance Operation Module Explanation: An internal table is invalid. This is a program logic error and should be reported. User Action: Submit a Software Performance Report (SPR).
BADPAT
invalid data pattern received Facility: DTR, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test and submit a Software Performance Report (SPR).
BADPKT
internal error - Remote packet format bad Facility: SMI, System Management Integrator/Server Explanation: The packet received by SMISERVER is invalid for one of the following reasons: o The packet format is too short. o The object or function code is out of range. o The originator PID is zero. User Action: Submit a Software Performance Report showing all SYSMAN commands leading to this error.
BADPNAME
illegal parameter name, must be P1 through P8 Facility: CDU, Command Definition Utility Explanation: The specified parameter name is not P1 through P8. User Action: Edit the CLD file to include a legal parameter name.
BADPRO
invalid syntax on /PROTECTION qualifier Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The command syntax for the /PROTECTION qualifier is incorrect. User Action: Type the DCL command HELP SPECIFY PROTECTION or refer to the VMS DCL Dictionary for the correct syntax, and reenter the command.
BADPROC
no such process Facility: SDA, System Dump Analyzer Explanation: The process name specified in the DCL commands SHOW PROCESS or SET PROCESS refers to a process that does not exist. User Action: Specify the correct process.
BADPROCNAME
variable used as a procedure Facility: VAXTPU, VAX Text Processing Utility Explanation: A variable name is being used in a PROCEDURE statement or is being used as the name of a procedure being called. User Action: Change the name of the procedure.
BADPROG
procedure definitions must precede statements in a program Facility: VAXTPU, VAX Text Processing Utility Explanation: In a VAXTPU program, all procedure definitions must precede the executable program statements. User Action: Reorder your program so that all procedure definitions appear before the executable statements.
BADPROGDELETE
cannot delete current program Facility: VAXTPU, VAX Text Processing Utility Explanation: The currently active program is attempting to delete itself. User Action: Do not use DELETE 'current_program' from within the current program.
BADPROMPTLEN
Prompt area length = 'integer', must be between 'integer' and 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: The length argument you specified to the SET PROMPT_ AREA built-in goes beyond the screen's physical limits. User Action: Use valid arguments and reenter the command.
BADPRTY
'priority' is an invalid priority Facility: Shared by several facilities Explanation: Priority must be within the range of 0 to 31. User Action: Respecify the priority within the acceptable range.
BADPSC
transfer address in unknown psect ('decimal-number') in module
'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An object module specified a nonexistent psect for
the transfer address.
User Action: Correct the source and relink.
BADQFILE
invalid disk quota file format
Facility: SYSTEM, VMS System Services
Explanation: The quota file has an invalid format.
User Action: Delete and recreate the quota file [0,0]QUOTA.SYS
using the following steps:
1. Use the SYSMAN command DISKQUOTA DISABLE to disable the quota
file.
2. Use the DCL command DELETE to delete the quota file.
3. Use the SYSMAN command DISKQUOTA CREATE to create a new quota
file.
See the VMS SYSMAN Utility Manual for more information about
DISKQUOTA commands.
BADQHDR
interlocked queue header corrupted Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADQNAME
'queue-name' is an invalid queue name Facility: Shared by several facilities Explanation: The queue name is not an initialized device or batch queue. User Action: Respecify with one of the queues listed in the DCL command SHOW QUEUE.
BADQUAL
qualifier /'qualifier' is inconsistent with the operation type Facility: BACKUP, Backup Utility Explanation: The specified qualifier cannot be used with the type of BACKUP operation indicated by the BACKUP command. User Action: Reenter the BACKUP command without the specified qualifier or select a different operation type. For more information on how qualifiers affect the BACKUP command, see the VMS Backup Utility Manual.
BADQUEUEHDR
interlocked queue corrupted Facility: SYSTEM, VMS System Services Explanation: An interlocked queue is corrupted. If this message is associated with a status code returned by a request to a DR32 interface, an INPTQ or TERMQ interlock timeout has occurred. User Action: Determine why the queue became corrupted and correct the problem.
BADRANGE
bad block address not on volume Facility: INIT, INITIALIZE Command Explanation: A block number specified for the /BADBLOCKS qualifier is a nonexistent block. User Action: Verify the command line with the current bad block data and reenter the command. If the error persists, run the Bad Block Locator Utility to obtain the correct data.
BADRANGE
inconsistent START and END specifications Facility: DUMP, File Dump Utility Explanation: In the /BLOCKS or /RECORDS qualifier, the START value is greater than the END value. User Action: Reenter the command specifying a valid range.
BADRCT
Replacement and Caching Table unrecoverable I/O error Facility: SYSTEM, VMS System Services Explanation: The Replacement and Caching Table is unreadable or invalid. This message applies only to devices governed by the Mass Storage Control Protocol (MSCP). This message could indicate that the read mechanism on the disk is defective or that the data on the disk is corrupted. User Action: Try to copy user data from this volume to a new volume. If this fails, contact the Digital Services Group.
BADREAD
read next or read prev with current record of 0, dscb: 'address' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message indicates an internal VAXTPU failure. User Action: Submit a Software Performance Report (SPR).
BADREFCNT
ref count: 'ccc', zap count: 'zzz', address: 'xxxxxxxx' Facility: VAXTPU, VAX Text Processing Utility Explanation: Internal VAXTPU failure. User Action: Submit a Software Performance Report (SPR).
BADREPLY
unknown type of operator reply, reply is 'reply' Facility: BACKUP, Backup Utility Explanation: The operator's reply indicated in the message is an unknown type and cannot be processed. User Action: See the operator or your system manager for an indication of the problem.
BADREPLY
unknown type of operator reply, reply = 'text' Facility: MOUNT, Mount Utility Explanation: An error has occurred in OPCOM. User Action: Retry the MOUNT request.
BADREQUEST
request 'name' is not understood Facility: VAXTPU, VAX Text Processing Utility Explanation: The type of information you requested from GET_INFO is not understood or supported for that particular data type. User Action: Reenter with a request string that is valid for the data type of the first parameter.
BADRETURN
RETURN occurs outside of a procedure Facility: VAXTPU, VAX Text Processing Utility Explanation: A RETURN statement must be inside the boundaries of a PROCEDURE . . . ENDPROCEDURE block. User Action: Either remove the indicated RETURN statement, or place it within procedural boundaries.
BADRSEIPL
bad IPL at entrance to report schedule event Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADRVNWCB
inconsistent RVN in window map pointer Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADSBMBLK
ACP tried to reference off end of bitmap Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADSECTION
bad section file Facility: VAXTPU, VAX Text Processing Utility Explanation: The section file is invalid. User Action: Use a valid section file.
BADSEQNUM
invalid data sequence received Facility: DTR, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test.
BADSETAFF
attempt to set process affinity to primary CPU failed Facility: SYSGEN, System Generation Utility Explanation: SYSGEN cannot set process affinity to the primary CPU. User Action: Submit a Software Performance Report (SPR).
BADSETCNT
incorrect number of devices in output specification Facility: BACKUP, Backup Utility Explanation: The output specification for a copy, restore, or compare operation with the /IMAGE qualifier must be a list containing the same number of devices as the number of volumes in the input volume set. User Action: If the input is a save set, use the DCL command BACKUP/LIST to determine how the save set was created; reenter the command.
BAD_SIZE
log file size invalid - permitted minimum is 100 blocks Facility: LMCP, Log Manager Control Program Explanation: You attempted to create a log file that is too small to use. User Action: Recreate a log file specifying a file size of 100 blocks or more.
BADSORT
error trying to sort input file Facility: CONVERT, Convert Utility Explanation: This message will be accompanied by a SORT error message that explains the error. User Action: Correct the error described in the SORT error message and try again.
BADSPC
no user matched specification Facility: AUTHORIZE, Authorize Utility Explanation: You entered a user specification that does not match any existing user account. User Action: Enter a user specification that matches at least one existing user account.
BADSPEC
file specification cannot be parsed using default specification. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL cannot locate the file because of an invalid file specification. User Action: Resolve the problem, and reinstall the product. Otherwise, contact the Digital Services Group.
BADSPLINDEX
invalid spin lock index Facility: SDA, System Dump Analyzer Explanation: You specified an invalid spin lock index to the SDA command SHOW SPIN LOCKS. The index specified does not correspond to any spin lock in the system. User Action: Reenter the command. Specify a valid spin lock index or a spin lock name.
BADSPLNAME
no spin lock could be found by that name Facility: SDA, System Dump Analyzer Explanation: You specified an incorrect name to the SDA command SHOW SPIN LOCKS. User Action: Reenter the command. Specify a valid spin lock name or a spin lock index.
BAD_SRL
record length 'number' is too short to contain keys Facility: SORT, Sort/Merge Utility Explanation: A record passed to SORT/MERGE is too short to contain all the keys. The record is discarded, and processing continues. User Action: Check your input records and key specification.
BADSTA
bad stack Facility: LIB, Library Facility Explanation: The user stack has an invalid format or cannot be accessed. User Action: Recompile your program with the /CHECK=BOUNDS qualifier to determine whether an array reference is out of bounds. If this does not correct the problem, use the debugger to determine where your program modifies the stack.
BADSTACK
bad stack encountered during exception dispatch Facility: SYSTEM, VMS System Services Explanation: An exception condition occurred during the execution of an image; the exception dispatcher noted an inconsistency in the call stack while searching for condition handlers. User Action: Check for a programming error. Locate the error that caused the stack pointers to be overwritten or modified.
BADSTACK
stack has been overwritten Facility: TRACE, Traceback Facility Explanation: The Traceback Facility cannot display the user stack because it has determined that the frame pointers are inconsistent. User Action: Check for the programming error that caused the stack to be overwritten. Correct the source program.
BADSTART
starting block beyond maximum legal block 'number' Facility: DUMP, File Dump Utility Explanation: You have attempted to dump beyond the maximum block size of the device. User Action: Use the $GETDVI System Service to verify that the starting block is within the legal boundary of the device.
BADSTATUS
return status 'xxxxxxxx' different than last signal 'xxxxxxxx' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message indicates an internal VAXTPU error. User Action: Submit a Software Performance Report (SPR).
BADSTRCNT
invalid string count found in journal file Facility: VAXTPU, VAX Text Processing Utility Explanation: An invalid string is found in the journal file. User Action: If the recovered information is sufficient, resume editing from this point. VAXTPU has recovered as much as it can from your journal file.
BADSTRLVL
structure level in command tables not recognized Facility: CDU, Command Definition Utility Explanation: Either the input tables file is corrupt or the CLI tables are not valid. User Action: If the input tables file is corrupt, it cannot be used again. To determine whether the CLI tables are valid, check for incompatible versions of the CLI and SET COMMAND.
BADSTRLVL
unrecognized structure level for command tables Facility: CLI, Command Language Interpreter (DCL) Explanation: Obsolete command tables (DCLTABLES) were used. User Action: Use the correct version of tables in the SYS$LIBRARY:DCLTABLES file.
BADSTRUCT
invalid value on /STRUCTURE qualifier Facility: INIT, INITIALIZE Command Explanation: The only legal values for the /STRUCTURE qualifier are 1 and 2. User Action: Correct the command. Specify either 1 or 2 for the /STRUCTURE qualifier.
BADSUBFCN
invalid subfunction received Facility: DTR, DECnet Test Program Protocol Explanation: The DECnet-VAX test program has a protocol incompatibility. User Action: Run the test against a compatible version of DTRECV or an equivalent.
BADSWPVBN
swap VBN specified for non-process page Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADSYM
unknown symbol 'symbol-name' Facility: SDA, System Dump Analyzer Explanation: The SDA cannot identify a specified symbol. User Action: Correct the spelling of the symbol.
BADSYMTAB
bad symbol table Facility: VAXTPU, VAX Text Processing Utility Explanation: The symbol table is invalid. User Action: Correct the symbol table.
BADTAGVAL
bad boundry tag value Facility: LIB, Library Facility Explanation: A call to LIB$FREE_VM has overwitten memory locations. Tags are longwords appended to the end of each block that store the size of the block. Before a block is freed, LIB$FREE_VM checks that these blocks have not been overwritten. User Action: Modify your program to ensure that it writes only to the memory locations that it has access to.
BADTIME
'time-spec' is an invalid time specification Facility: Shared by several facilities Explanation: An invalid time specification is entered. User Action: Respecify the time specification using the rules listed in the VMS DCL Dictionary.
BADTYPE
invalid file type in startup file Facility: STDRV, System Startup Driver Explanation: A startup component file in the startup component database has a file type which is not COM or EXE. User Action: Use the SYSMAN command STARTUP MODIFY FILE to correct the file name.
BADTYPE
invalid sink type 'sink-name', record ignored Facility: EVL, Event Logger Explanation: The event receiver received an event record that had an invalid sink type. The record is ignored. User Action: None. This message displays the name of the sink.
BAD_TYPE
invalid sort process specified Facility: SORT, Sort/Merge Utility Explanation: You passed one of the following sort type codes to the routine package: o Less than 1 or greater than 4 if file I/O o Not equal to 1 if record I/O o An invalid key word in command /PROCESS Legal values are 1 through 4 for file I/O; 0 for record I/O; and RECORD, TAG, INDEX, or ADDRESS for the /PROCESS command parameter. User Action: Specify a different sorting process.
BADUIC
invalid UIC syntax Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The command contains an invalid UIC. The group and member portions of a UIC must both be specified and separated by a comma. User Action: Reenter the command; use the DCL command HELP or refer to the VMS DCL Dictionary for the correct syntax.
BADUSERDESC
descriptor from user routine invalid or memory inaccessible Facility: VAXTPU, VAX Text Processing Utility Explanation: The routine called from CALL_USER incorrectly filled in the return descriptor. It either is not a valid VAX descriptor or references memory that is not accessible by your access mode. User Action: For information on how to use descriptors, refer to the Introduction to VMS System Routines.
BADUSR
username does not exist Facility: AUTHORIZE, Authorize Utility Explanation: The user name you specified does not exist in the system user authorization file (SYSUAF.DAT). User Action: Correct the user name and reenter your command. You can display the records in the user authorization file by using the AUTHORIZE command SHOW.
BADUSRDAT
connect/disconnect userdata invalid Facility: DTS, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test.
BADUSRLEN
connect/disconnect userdata is wrong length Facility: DTS, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Retry the test.
BADVALUE
error in value specification Facility: AUTHORIZE, Authorize Utility Explanation: You specified an incorrect value. User Action: See the VMS Authorize Utility Manual for information on value specifications.
BADVALUE
illegal qualifier value Facility: CDU, Command Definition Utility Explanation: Either the qualifier value in the command string is invalid or the qualifier value in the CLD file is incorrect. User Action: Either enter a valid qualifier value in the command string or modify the qualifier value contained in the CLD file.
BADVALUE
illegal qualifier value Facility: MESSAGE, Message Utility Explanation: An illegal numeric value has been used in one of several contexts within a MSG file (for example, bad facility numbers, bad base numbers, or a bad FAO count). User Action: Replace the illegal value with one within the valid range.
BADVALUE
integer value 'integer' is outside of specified limits Facility: VAXTPU, VAX Text Processing Utility Explanation: The argument that you supplied is outside of the valid boundaries. User Action: Reenter your command with a valid integer value for the argument.
BADVALUE
'value' is an invalid keyword value Facility: Shared by several facilities Explanation: An invalid value is specified for the indicated command qualifier. User Action: Check the command string for a spelling or syntax error. Verify the values or syntax and reenter the command.
BADVALUE
'value' is an invalid keyword value Facility: DSR, DIGITAL Standard Runoff Explanation: DSR encountered an invalid keyword value. User Action: Specify the correct value and reenter the command.
BADVEC
invalid change mode or message vector Facility: SYSTEM, VMS System Services Explanation: This severe error message is associated with a status code returned from a system service request. An invalid change mode or message vector is encountered. User Action: Correct the change mode or message vector.
BADVOL1
bad VOL1 ANS label Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The protection encoded on a magnetic tape volume label is invalid or the label itself is invalid; the magnetic tape ACP cannot process the tape. The tape is defective, it is not an ANSI-labeled tape, or the hardware device is not reading the tape properly. User Action: Verify the tape volume. If necessary, mount the tape as a foreign volume and try to read it.
BADVOLACC
invalid value on /LABEL:VOLUME_Accessibility qualifier Facility: INIT, INITIALIZE Command Explanation: An invalid ANSI "a" character is specified in the volume accessibility field of the tape volume label. For example, the following command specifies an invalid ANSI "a" character-a dollar sign ($): $ INITIALIZE/LABEL:VOLUME_ACCESSIBILITY:$ User Action: Specify a valid ANSI "a" character in the single- character field of the command. The set of valid ANSI "a" characters includes: digits 0..9, uppercase A..Z, space, and ! " % & ' ( ) * + , - . / : ; < = > ?
BADVOLLBL
invalid value for ANSI tape volume label Facility: INIT, INITIALIZE Command Explanation: You used one or more invalid ANSI "a" characters in the volume label. The set of valid ANSI "a" characters includes: digits 0..9, uppercase A..Z, space, and ! " % & ' ( ) * + , - . / : ; < = > ? User Action: Respecify the command with valid ANSI "a" characters.
BADWCBPT
bad WCB pointer in IRP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BADWIDTHCHANGE
terminal will not support change of width Facility: VAXTPU, VAX Text Processing Utility Explanation: Window widths may not be changed on non-DEC terminals or terminals without advanced video. User Action: Use a different terminal or do not change window widths.
BADWINDADJUST
attempt to make window less than 1 line long, no adjustment Facility: VAXTPU, VAX Text Processing Utility Explanation: You have attempted to use the built-in procedure ADJUST_WINDOW to make a window less than one physical screen line in length. User Action: Check the integer arguments and reenter the values. Make the window one or more lines long if there is no status line for the window. Make the window two or more lines long if there is a status line.
BADWINDLEN
window length = 'integer', must be between 'integer' and 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: You specified a window length in an argument to the built-in procedure CREATE_WINDOW, which goes beyond the screen's physical limits. User Action: Try your command again with a valid window length.
BADWORD
invalid data ('xxxx') at 'location'
Facility: Shared by several facilities
Explanation: The specified data is invalid at the given location.
User Action: Collect as much information as possible and submit a
Software Performance Report (SPR).
BADZONE
bad zone Facility: LIB, Library Facility Explanation: LIB$SHOW_VM_ZONE, LIB$STAT_VM_ZONE, or LIB$VERIFY_ VM_ZONE is called with a zone identifier that does not represent a valid VM zone. Either the zone or one of its associated data structures is invalid. User Action: Begin debugging procedures to verify and correct the problem.
BASDUERRS
basing image due to errors in relocatable references Facility: LINK, Linker Utility Explanation: Failure to use the .ADDRESS directive and general addressing mode in reference to shareable images. The linker must base the shareable images to resolve the references. User Action: The image will execute properly; however, you should correct the specified references.
BASESYM
base address symbol 'symbol-name' is undefined or relocatable Facility: LINK, Linker Utility Explanation: A symbol used to specify a base address symbolically is not defined or is relocatable. User Action: You must use a defined, absolute symbol for specifying symbolic base addresses.
BASSHRBEL
shareable image 'image-name' has base of 'address' which is below image base of 'address' Facility: LINK, Linker Utility Explanation: A shareable image specified as input in the creation of a based shareable image has a lower base address than the address specified in the BASE= option. User Action: None; however, note that the linker places the input shareable image at a lower base address than the address specified in the BASE= option.
BATCHNOOPR
no operator available to service batch request Facility: MOUNT, Mount Utility Explanation: The MOUNT request is aborted because the batch job requires operator assistance and no operator is present. User Action: Call the operator and retry the request.
BATIS_OFF
batching is off Facility: SMG, Screen Management Facility Explanation: A program tried to turn off batching when batching is already off. User Action: Make sure that there is one call to turn on batching for each call to turn it off.
BATIS_ON
batching is on Facility: SMG, Screen Management Facility Explanation: A program tried to turn on batching when batching is already on. This is normal in a modular environment. User Action: Make sure that there is one call to turn off batching for each call to turn it on.
BATSTIPRO
batching is still in progress Facility: SMG, Screen Management Facility Explanation: A user tried to end batching (updating) with a call to SMG$END_DISPLAY_UPDATE or SMG$END_PASTEBOARD_UPDATE. This action did not terminate batching because there were more calls to begin batching than to end batching. User Action: None. An outer level routine probably still needs batching to be in effect.
BBFOVF
bad block file overflow on 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: This message indicates that during the analysis of the medium, the SDBSF became full. It could be as a result of a large number of bad blocks specified to the /BAD_BLOCKS qualifier or as a result of an unreliable medium. User Action: Rerun the ANALYZE/MEDIA command without as many bad blocks entered to the /BAD_BLOCKS qualifier, or in the default mode of the /NOKEEP qualifier, which will re-create the SDBSF.
BBFWRT
failed to write the bad block file on 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: Failed to write an updated SDBSF on the media. User Action: Examine the associated messages for a clue to the problem and correct it if possible. An example of this type of error would be updating the bad block file without exercising the medium, but the device is write locked.
BBLHEADER
file ('file-id') 'filename' contains suspected bad blocks
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file is marked as containing suspected
bad blocks. When the file is deleted, the blocks will be verified
and returned to the bad block file if necessary.
User Action: If desired, examine the contents of the file and
reconstruct from backup media as necessary.
BDPPURGERR
buffered datapath purge incomplete Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BEGIN
'string' beginning Facility: Shared by several facilities Explanation: A program phase is being started. User Action: None.
BEGIND
'string' beginning at 'date' Facility: Shared by several facilities Explanation: A program phase began. User Action: None.
BEGINT
'string' beginning at 'time' Facility: Shared by several facilities Explanation: A program phase began. User Action: None.
BEGNLEND
beginning time not earlier than ending time Facility: MONITOR, Monitor Utility Explanation: Monitoring is requested to begin at a time that is the same as or later than the requested end time. This error occurs most frequently when specifying a delta time specification for the /BEGINNING or /ENDING qualifiers. Delta time specifications must always be preceded by a plus or minus sign. If a plus sign is used, the entire time specification must be enclosed in double quotes. For live monitoring and playback, delta time specifications are offset from the current system time. User Action: Reenter the MONITOR request with the correct time specifications for the /BEGINNING or /ENDING qualifiers.
BEGOFBUF
attempt to move past the beginning of buffer 'buffer-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You have attempted to move backward past the first character in the buffer. VAXTPU assumes that the current editing position is the first character in the buffer. User Action: Stop trying to move backward. You are already positioned at the beginning of the buffer.
BEGOFFILE
beginning of file Facility: SYSTEM, VMS System Services Explanation: A backspace operation backed up to the beginning of the file. User Action: If you are reading backwards or backspacing a tape, this message indicates that the end-of-the-data area has been reached. Modify the program to recognize and correct this condition.
BEGRAN
requested beginning time beyond range of input file Facility: MONITOR, Monitor Utility Explanation: Monitoring of an input recording file is requested to begin at a time later than the ending time indicated in the file. This error occurs most frequently when a delta time is specified in the /BEGINNING qualifier. Delta time specifications must always be preceded by a plus or minus sign. If a plus sign is used, the entire time specification must be enclosed in double quotes. For both live monitoring and playback, delta time specifications are offset from the current system time. User Action: Reenter the MONITOR command with the correct time specifications for the /BEGINNING qualifier.
BES
bad escape sequence Facility: RMS, VMS Record Management Services Explanation: A terminal escape sequence is invalid. User Action: The characters read up to the escape sequence are returned in the user record buffer. Modify the program to detect and respond to the condition, or reenter the input specifying the correct escape sequence. BIIC failure - BICSR/BER/CNF 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line. User Action: Call the Digital Services Group to check the port hardware.
BINARYOPER
operand combination 'type' 'oper' 'type' unsupported Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified operator does not support the specified data type combination. User Action: Use only supported data types with the operator.
BINCHKSUM
a binary record failed checksum in 'record' Facility: EXCHANGE, Exchange Utility Explanation: While reading a formatted-binary record, the Exchange Utility found a record whose computed checksum did not match the actual checksum stored in the record. User Action: EXCHANGE ignores this error and copies the file as if all the checksums are correct. If the output file is a formatted- binary file, the checksum in the output record is correct. Make sure that the output file is usable.
BINRECFMT
an illegal binary record found in 'filename' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility found a record in the named file which is not a valid formatted-binary record. User Action: Retry the command after checking whether the file is really a PDP-11 formatted binary file. If it is not a binary file, use the correct /RECORD_FORMAT qualifier. For example, the console file CI780.BIN is assumed to be a formatted binary file, since it has the file type BIN. CI780.BIN is really a fixed-length file, so it should be copied with a /RECORD_FORMAT=FIXED qualifier.
BITMAPERR
I/O error on storage bitmap; volume locked Facility: MOUNT, Mount Utility Explanation: An I/O error is encountered during a mount operation. Existing files on the volume can be accessed but other operations, for example, CREATE and DELETE, are not possible. User Action: Repair the volume using the Analyze/Disk_Structure Utility.
BITMAPINV
storage bitmap is invalid, volume locked Facility: MOUNT, Mount Utility Explanation: The volume's storage bit map contains invalid data. User Action: Use the Analyze/Disk_Structure Utility to repair the bit map.
BKS
bucket size too large (FAB) Facility: RMS, VMS Record Management Services Explanation: The bucket size specified in the FAB is larger than 63. If the bucket size is specified as zero, the maximum record size is too large. User Action: Verify that the call to the VMS RMS service is coded correctly. Refer to the formulas and rules for calculating bucket size in the VMS Record Management Services Manual.
BKZ
inconsistent bucket size for area id = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The bucket size field specified in an allocation XAB is larger than 63 or is too small for the record size. User Action: The status value (STV) field of the FAB provides the area identification of the XAB in error. Verify that the call to the VMS RMS service is coded correctly. Refer to the formulas and rules for calculating bucket size in the VMS Record Management Services Manual.
BLK0BAD
block 0 is bad, do not use 'device-name' as a system device Facility: BAD, Bad Block Locator Utility Explanation: Block zero (0) is defective on the medium. User Action: Do not use the medium as a system device, because block zero is used to contain the boot strap.
BLKDIRSYNX
block directive syntax error Facility: MACRO, VAX MACRO Assembler Explanation: A conditional block or a repeat block directive contained a syntax error. User Action: Correct the directive syntax.
BLKEXPNABS
block expression not absolute Facility: MACRO, VAX MACRO Assembler Explanation: The expression specifying the amount of storage to be allocated in a .BLKA, .BLKB, .BLKD, .BLKF. .BLKG, .BLKH, .BLKO, .BLKQ, OR BLKW directive contained an undefined symbol or is a relative expression. User Action: Replace the expression with an absolute expression that does not contain any undefined symbols.
BLKZERO
block zero is bad; volume not bootable Facility: INIT, INITIALIZE Command Explanation: This message is generated by the DCL command INITIALIZE as a warning message. The volume cannot be bootstrapped on a PDP-11. The volume is usable on a VMS system disk. User Action: Note that the volume probably cannot be used as a system volume for a VAX-11 processor model that requires access to the boot block during a bootstrap operation.
BLKZERO
block zero of 'device-name' is bad - volume not bootable Facility: BACKUP, Backup Utility Explanation: The boot block of the specified volume is not usable. User Action: Note that the volume probably cannot be used as a system volume for a VAX-11 processor model that requires access to the boot block during a bootstrap operation.
BLN
invalid block length for control block (RAB/FAB) Facility: RMS, VMS Record Management Services Explanation: An invalid value is specified in a VMS RMS FAB or RAB block length field. User Action: Verify that the call to the VMS RMS service is coded correctly. Specifically, ensure that the control block is properly initialized and that the block length field is not modified after initialization.
BLOCKCHECK
block check, please report error 'error' and the following: address = 'number', size (found,expected) = 'size' type = 'type' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a control block of an unexpected format, and has terminated. User Action: Submit a Software Performance Report (SPR), including the error number and other information, and the commands which resulted in the message. If the error is only reproducible using a particular piece of media, please send a copy of the media with the SPR (use BACKUP /PHYSICAL to make the copy).
BLOCKCHECK0
block check, please report error 'error' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility failed to find a control block when one is expected, and has terminated. User Action: Please submit a Software Performance Report (SPR), describing the error number and the commands which resulted in the message. If the error is only reproducible using a particular piece of media, please send a copy of the media with the SPR (use BACKUP /PHYSICAL to make the copy).
BLOCKCNTERR
block count error Facility: SYSTEM, VMS System Services Explanation: The message indicates that the number of blocks read differs from the number of blocks recorded in the trailer labels when a file that is opened for a read operation is deaccessed. User Action: This message indicates that either a noise record is read or a valid record is not read. Either the magnetic tape is defective or a hardware problem exists. Mount the magnetic tape on another drive/controller and perform the same operation again. If the problem persists, the magnetic tape is probably defective.
BLOCKCRC
software block CRC error Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the block CRC field of a save set block. Data in the save set is corrupted. User Action: None. Save set data has been lost.
BLOCKLOST
block of 'filespec' lost due to unrecoverable error Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an irrecoverable error in reading the specified save set and cannot correct the error using the redundancy information. User Action: None. Save set data has been lost.
BLPRSP
bad loopback response Facility: NCP, Network Control Program Explanation: A loopback message did not match either the length or content that the system expected. User Action: Use another form of testing to determine why the loopback failed.
BMS
bad margin specification: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: An illegal value is used for a margin setting. User Action: Correct the margin setting in the input file.
BOF
beginning of file detected Facility: RMS, VMS Record Management Services Explanation: During a backspace operation, the file is positioned at the beginning of the file before the specified number of blocks is backspaced. The status value (STV) field in the FAB or RAB contains the number of blocks actually spaced. User Action: This is a warning status. Modify the source program, if necessary, to detect and respond to the condition. BOOT-F-Bootfile not contiguous Facility: VMB, Virtual Memory Boot Explanation: The file [SYSEXE]SYSBOOT.EXE is located but is not contiguous. User Action: The disk you are attempting to bootstrap cannot be bootstrapped. Obtain another copy of the system disk. BOOT-F-Failed to initialize device Facility: VMB, Virtual Memory Boot Explanation: Encountered an error in the load path while VMS was trying to initialize the boot device, User Action: Try initializing again. If this fails, call the Digital Services Group. BOOT-F-I/O error reading boot file Facility: VMB, Virtual Memory Boot Explanation: An uncorrectable read error occurred while the file [SYSEXE]SYSBOOT.EXE is being read. User Action: Try rebooting the disk. If subsequent attempts fail, obtain another copy of the system disk. BOOT-F-Nonexistent drive Facility: VMB, Virtual Memory Boot Explanation: The specified drive number does not exist. User Action: Specify an appropriate device unit to the console program, or use a different console bootstrap command procedure. BOOT-F-Unable to locate BOOT file Facility: VMB, Virtual Memory Boot Explanation: The file [SYSEXE]SYSBOOT.EXE could not be found. User Action: You are attempting to bootstrap a volume that does not contain a VMS binary system. Attempt to reboot using an appropriate disk volume. BOOT-F-Unexpected exception Facility: VMB, Virtual Memory Boot Explanation: An unexpected exception occurred while the primary bootstrap (VMB.EXE) is being executed. This condition probably indicates a corrupted SYSBOOT.EXE file or a hardware failure. User Action: Determine the source of the error, and either obtain a new copy of the system disk or call your local field service representative. BOOT-F-Unexpected machine check Facility: VMB, Virtual Memory Boot Explanation: An unexpected machine check occurred while the primary bootstrap (VMB.EXE) is being executed. This condition probably indicates a corrupted SYSBOOT.EXE file or a hardware failure. User Action: Determine the source of the error, and either obtain a new copy of the system disk or call your local field service representative.
BOTLINETRUNC
calculated new last line 'integer', changed to 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: You have adjusted a window. The new last line of the window, however, would have been greater than the actual number of physical screen lines. Therefore, VAXTPU has calculated the number of available screen lines and truncated the window accordingly. User Action: None is required. However, you may reexecute the built-in procedure ADJUST_WINDOW with different arguments.
BRDCST
unable to write to console device 'sink-name' Facility: EVL, Event Logger Explanation: An error occurred while writing to the console sink. The event is discarded. This message displays the name of the console. User Action: None.
BRDESTRANG
branch destination out of range Facility: MACRO, VAX MACRO Assembler Explanation: The address specified in the branch instruction is too far from the current PC. Branch instructions with byte displacements have a range of -128 bytes to +127 bytes from the current PC. Branch instructions with word displacements have a range of -32768 bytes to +32767 bytes from the current PC. User Action: Use a branch instruction with a word displacement instead of one with a byte displacement; use a jump (JMP) instruction instead of a branch instruction; or change the program logic so that the branch destination is closer to the branch instruction.
BRDMSGLOST
broadcast queue pointer has no related entry Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
BREAK
breakpoint fault at PC location, PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: A breakpoint instruction is encountered. This message indicates an exception condition that is not handled by the condition handler and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to correct the instruction that caused the error.
BRKNLIB
library 'library-name' not properly closed, compress or rebuild Facility: LIBRAR, LIBRARY Command Explanation: An error occurred during a previous update to the library that interrupted the write operation, leaving the library in an inconsistent state. User Action: This library can no longer be modified, but it can be read. Uncorrupted data can be reclaimed by compressing the library or by extracting modules and re-creating a new library.
BRTOOFAR
destination 'addr' is too far for branch operand Facility: PATCH, Patch Utility Explanation: The relative displacement for the branch instruction is not large enough to reach the specified destination address. User Action: Correct the destination address and retry the operation.
BUFBLKREQ
buffer count or block count required Facility: SET, SET Facility Explanation: You specified either the /BLOCKS_COUNT or /BUFFER_COUNT qualifier (with the SET RMS command) without specifying numeric values. User Action: Reenter the command and qualifier specifying a numeric value for the qualifier.
BUFBYTALI
device does not support byte-aligned transfers Facility: SYSTEM, VMS System Services Explanation: Some devices do not support buffers that are not aligned on word boundaries or byte counts that are not an even number. User Action: Recode the program using the .ALIGN macro directive or change the byte count to an even number.
BUFFEROVF
output buffer overflow Facility: SYSTEM, VMS System Services Explanation: An output string returned by a system service is larger than the user buffer provided to receive the string, and the string is truncated. User Action: Reenter the QIO with a larger buffer or ignore the error if you have received enough information.
BUFFEROVF
output buffer overflow Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont format routine indicating buffer overflow has been detected. User Action: None.
BUFFERSLOST
all buffers are lost Facility: BACKUP, Backup Utility Explanation: A software error occurred in the Backup Utility. User Action: Submit a Software Performance Report (SPR).
BUFNOTALIGN
buffer incorrectly aligned Facility: SYSTEM, VMS System Services Explanation: A table, list, or buffer area is not correctly aligned. If this message is associated with a status code returned by a request to a DR32 interface, the command block address in the Data Transfer Command Table is not quadword aligned (only for start data transfer functions). If this message is associated with a status code returned by a request to a LPA11-K driver and this error occurs for an initialize LPA11-K request, the initialize command table is not word-aligned. If this error occurs for a start data transfer request, there are several possible causes: o User status word (USW) not word-aligned o Buffer area not longword-aligned o Random Channel List (RCL) not word-aligned User Action: Determine which data area is incorrectly aligned and align it on the appropriate boundary, that is, word, longword, and so forth.
BUFOVF
command buffer overflow - shorten expression or command line Facility: CLI, Command Language Interpreter (DCL) Explanation: A command string, including continuation lines, is longer than the buffer used by the command interpreter to store a command. User Action: Shorten and reenter the command; possibly enter more than one command.
BUFOVFL
buffer overflow for output file name string Facility: PPL, Parallel Processing Facility Explanation: Buffer could not contain the complete output string. User Action: Recode to pass a larger buffer.
BUFOVR
internal error - Packet has overflowed buffer Facility: SMI, System Management Integrator/Server Explanation: The packetizer has produced a buffer larger than 4096 bytes. User Action: Submit a Software Performance Report showing all SYSMAN commands leading to this error. Also submit the output of a SHOW CLUSTER command.
BUFTOOSMALL
request could not be completely satisfied due to limited buffer size Facility: JBC, Job Controller Explanation: Your $GETQUI or $SNDJBC request was not fully satisfied because the amount of information retrieved in response to the query exceeds the amount of data the queue manager can return in response to a single request. User Action: Replace your large request with several smaller requests.
BUG
internal RMS error condition detected Facility: RMS, VMS Record Management Services Explanation: This message indicates an internal software error occurred in VMS RMS. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BUGCHECK
internal consistency failure Facility: SYSTEM, VMS System Services Explanation: The operating system noted an internal software failure. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BUGCHECK
internal error detected in DECthreads Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The DECthreads run-time program has discovered an internal inconsistency. User Action: Run the program with the debugger. Use the SET OUTPUT LOG command so that the debugger outputs the results to a file. Type GO to run the program. When the bugcheck occurs, type SHOW CALLS. Submit a Software Performance Report (SPR) with the file produced by the debugger.
BUG_DAP
Data Access Protocol error detected; DAP code = 'xxxxxxxx' Facility: RMS, VMS Record Management Services Explanation: A Data Access Protocol (DAP) violation is detected either by VMS RMS or by the File Access Listener (FAL) at the remote node during a DECnet-VAX file access operation. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BUG_DDI
invalid default directory Facility: RMS, VMS Record Management Services Explanation: An internal software error occurred in VMS RMS. User Action: Collect as much information as possible and submit a Software Performance Report (SPR).
BUSY
a busy signal is detected on the phone line Facility: DTK, DECtalk Facility Explanation: The routine DTK$DIAL_PHONE is called to dial a phone number and the line is busy. User Action: Try calling again.
BUSY
user structure (FAB/RAB) still in use Facility: RMS, VMS Record Management Services Explanation: A VMS RMS operation is executed from an AST routine while the specified FAB or RAB is still in use from non-AST level, or the user called VMS RMS illegally from executive mode at AST level or from kernel mode and interrupted another VMS RMS operation. User Action: Verify that the call to the VMS RMS service is coded correctly. Use multiple I/O streams or include $WAIT requests as necessary. Because the control block is still in use, no STS or STV value can be returned in the FAB or RAB, so this status value is returned only in R0.
BVN
missing or illegal variable name: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The name specification for a DSR command (.VARIABLE, .IF, .IFNOT, .ENDIF, or .ELSE) is missing or illegal. User Action: Supply the missing specification, or check to see that it is typed correctly. BVP failure - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Call the Digital Services Group to check the port hardware. BVP timeout - Status/Error/Data 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Call the Digital Services Group to check the port hardware. Cables have gone from CROSSED to UNCROSSED Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: None. Cables have gone from UNCROSSED to CROSSED Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: Check for crossed-cable pairs.
CACLS
the 'class-name' class cannot be added to this report Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The class name entered does not apply to the currently selected report and, therefore, cannot be added to the report. The name is, however, valid in a different report. User Action: Select a different report or enter the HELP CLASSES command to get a list of available classes.
CAFINVGROUP
group number is invalid or out of range Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION command specified an invalid group number. User Action: Reenter the command with a numeric group number between 1 and 65535.
CAFNEITHER
neither GROUP nor PASSWORD given - no action taken Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION command do not supply either a group number or a password. User Action: Reenter the command with the /GROUP or /PASSWORD qualifiers, or both, as necessary.
CAFNOTCLU
*Warning* - Environment not CLUSTER - check all system disks for consistency Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SET/SHOW CLUSTER_AUTHORIZATION command is entered in a non-CLUSTER environment. To ensure consistency of the CAF database throughout the cluster, these commands should normally be entered from a CLUSTER environment. User Action: Change the environment and reenter the command, if desired.
CAFOLDGROUP
existing group will not be changed Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION command specified a new password but did not specify a new group number. The old group number is retained. User Action: None, if the group number is correct.
CAFOLDPASS
existing password will not be changed Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION command specified a new group number but did not specify a new password. The old password is retained. User Action: None, if the password is correct.
CAFPASSLEN
password is null or too long Facility: SYSMAN, Cluster System Management Utility and CAF, Cluster Authorization File Service Explanation: A CONFIGURATION SET CLUSTER_AUTHORIZATION command specified an invalid password. User Action: Reenter the command with a valid password.
CAFREBOOT
cluster authorization file updated. The entire cluster should be rebooted. Facility: SYSMAN, Cluster System Management Utility Explanation: When you update the CAF, you must reboot the cluster. User Action: Reboot the cluster.
CALLOVER
stack overflow Facility: VAXTPU, VAX Text Processing Utility Explanation: A nested procedure call caused the program to exceed the maximum call depth of 100. User Action: Recode the program so that the nesting depth is less than 100.
CALLUSERFAIL
CALL_USER routine failed with status %X 'status' Facility: VAXTPU, VAX Text Processing Utility Explanation: The CALL_USER routine returned the indicated failure status. User Action: Your action depends on the routine returned.
CANCEL
I/O operation canceled Facility: SYSTEM, VMS System Services Explanation: An input or output operation was canceled by the $CANCEL system service before it started. Usually, the image cancels the request. The operating system does not normally display this message. If this message is associated with a status code returned by a request to a DR11-W interface and if the $CANCEL system service is requested while a block mode request is active, then the driver performs a device reset to the DR11-W. User Action: None.
CANCELED
command is canceled by keyboard action Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received a Ctrl/C key sequence while processing a command; it canceled the command and returned to the prompt. User Action: None.
CANCELQUIT
QUIT canceled by request
Facility: VAXTPU, VAX Text Processing Utility
Explanation: Execution of the built-in procedure QUIT is canceled
when you respond "no" to the REALLYQUIT question.
User Action: None.
Cannot set terminal type from change mode
Facility: EDT, EDT Editor
Explanation: You attempted to enter a SET TERMINAL
{VT100|VT52|HCPY} command while working in a screen mode.
User Action: To change the terminal type with the SET TERMINAL
command, you must shift to line mode.
CANNOTUNSEL
cannot unselect item from unselect action routine Facility: VAXTPU, VAX Text Processing Utility Explanation: You tried to unselect the global selection within the action routine called when the global selection is being unselected. User Action: The global item is already unselected; remove the code which attempts to unselect it again.
CANTATTACH
unable to ATTACH to target process Facility: LAT, LAT Facility Explanation: LATCP was unable to attach to the process specified by the ATTACH command for the reason described in an accompanying message. User Action: Correct the situation based on the information in the accompanying message.
CANTBAL
can't balance last page Facility: DSR, DIGITAL Standard Runoff Explanation: An internal error has occurred. User Action: Submit a Software Performance Report (SPR). Please include the file that caused the error.
CANTCOPYSTR
unable to copy character string Facility: LAT, LAT Facility Explanation: An internal LATCP error occurred. User Action: Take appropriate action based on information in the accompanying message.
CANTEXPREG
cannot expand virtual address space Facility: BACKUP, Backup Utility Explanation: Standalone BACKUP attempted unsuccessfully to expand its virtual address space. User Action: If this error can be reliably reproduced, the BACKUP command used and a description of the circumstances should be submitted along with a Software Performance Report (SPR).
CANTLOCK
cannot lock pages into memory. If the system disk goes off line, reboot Facility: BACKUP, Backup Utility Explanation: Standalone BACKUP could not lock the required pages into the working set. User Action: Normally, no action is necessary. However, if the system disk goes off line, it will be necessary to reboot the system. The operation of standalone BACKUP is likely to be very slow because there is insufficient memory to lock down a small portion of the working set.
CANTLOCMAC
can't locate macro in macro libraries Facility: MACRO, VAX MACRO Assembler Explanation: A macro name specified in an .MCALL directive is not defined in the macro libraries searched. User Action: Specify the macro library that defines the macro in the DCL command MACRO.
CANTSPAWN
unable to SPAWN due to captive account Facility: LAT, LAT Facility Explanation: You cannot spawn out of LATCP using the SPAWN command when LATCP is being run from a captive account. User Action: None.
CAPTINQ
captive account - inquire command not valid Facility: CLI, Command Language Interpreter (DCL) Explanation: The INQUIRE command is not valid for captive accounts. User Action: See your system manager to have the INQUIRE command removed from the login command procedure and replaced with the READ/PROMPT command.
CAPTINT
captive account - interactive access denied Facility: CLI, Command Language Interpreter (DCL) Explanation: Interactive access (in other words, access to the $ prompt) is not allowed for captive accounts. User Action: There is an error in the captive login command procedure that has been established for this account, causing it to end unintentionally. Or, the captive login command procedure has not been set up correctly for this account. See your system manager to have the situation corrected.
CAPTIVE
this command cannot be executed; Your account is CAPTIVE Facility: MAIL, Mail Utility Explanation: You attempted to enter a SPAWN command, and your account is CAPTIVE. User Action: Contact your system manager if your your account should not be CAPTIVE.
CAPTIVE
unable to create a subprocess in a captive account Facility: VAXTPU, VAX Text Processing Utility and REM, Set Host Facility Explanation: Captive accounts are not allowed unrestricted access to CLIs, which the SPAWN or CREATE_PROCESS built-ins would allow. User Action: Do not use the SPAWN or CREATE_PROCESS built-ins from a captive account.
CARDS
cards Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for the "CARDS" class operations. User Action: None.
CASETOOLARGE
CASE limits distance too large Facility: VAXTPU, VAX Text Processing Utility Explanation: Your CASE statement contains FROM . . . TO limits that exceed the maximum number allowed. User Action: Break your CASE statement range into multiple, smaller CASE statements.
CBT
insufficient contiguous space, file copied noncontiguously Facility: Shared by several facilities Explanation: There is insufficient disk space to copy the file contiguously; the file is copied, but the output file may not be contiguous. User Action: None.
CCF
cannot close file Facility: RMS, VMS Record Management Services Explanation: The system could not close an output file during a call for I/O run-down. User Action: The user-specified buffer contains the device, directory, and file identifications of the file that could not be closed. Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
CCR
cannot connect RAB
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS could not connect a record access block
(RAB) to the specified file access block (FAB). This error usually
results from one of the following actions:
o Specifying block I/O (setting the RAB$V_BIO option of the
RAB$L_ROP field) with multistreaming (setting the FAB$V_MSE
option of the FAB$B_SHR field)
o Attempting to connect multiple RABs to a FAB when the
multistreaming option (FAB$V_MSE) of the file sharing field
(FAB$B_SHR) has not been set
o Attempting a DECnet operation when the multistreaming option is
set
The multistreaming option is not supported for DECnet operations.
User Action: Modify the program. Do not attempt to use unsupported
operations.
CDA
cannot deliver AST Facility: RMS, VMS Record Management Services Explanation: Either the applications program exceeds its AST quota, or not enough system dynamic memory is available for VMS RMS to deliver an error or successful completion AST, and the applications program has disabled resource wait mode. User Action: The status value (STV) field in the FAB or RAB contains the system status code of the operation that provides additional information about the condition. Take corrective action based on this status code. Raise the process's AST quota and modify the source program, if necessary, to detect and respond to the condition.
CEBREFNEG
negative reference count on shared memory CEB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CEM
comma expected, missing: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A required comma is missing from the command string. User Action: Supply the missing comma.
CENTRL
central Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "CENTRAL" class operations. User Action: None.
CHAINW
chained write status Facility: SYSTEM, VMS System Services Explanation: The block just received by the 3271 Protocol Emulator is part of a chained write sequence. User Action: Normally, the information received by the 3271 Protocol Emulator in a chained write sequence is appended to the information received in the previous sequence. Your action will vary for each application.
CHAN
error assigning or deassigning channel Facility: CNF, NI Configurator Explanation: An error occurred while assigning or deassigning a channel. User Action: See the accompanying message to determine the appropriate action.
CHANGE_INV
selected change of state is not permitted Facility: LMCP, Log Manager Control Program Explanation: An attempt was made to change the transaction state, with the REPAIR subcommand, using an invalid transition. Valid transitions include: PREPARE to COMMIT, PREPARE to ABORT, and COMMIT to FORGET. User Action: See the REPAIR command description in the LMCP documentation. Change mode can be entered only from a terminal Facility: EDT, EDT Editor Explanation: You cannot enter change mode (keypad, nokeypad, or hardcopy change mode) from a network, a batch command file, or a startup command file. User Action: Use the EDT command SET MODE CHANGE in the startup file to make EDT enter change mode at the end of the startup file.
CHANINTLK
channel usage interlocked Facility: SYSTEM, VMS System Services Explanation: An application attempted to perform a terminal I/O request to a pseudoterminal that has a virtual terminal linked to it. User Action: Do not use the channel for terminal I/O until the virtual terminal is no longer linked.
CHG
invalid key change in $UPDATE (CHG not set) Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $UPDATE operation specified a record that contained one or more changed key values for keys that do not have the 'keys may change' attribute set in the XAB key option flag. User Action: Either reorganize the file and specify the 'keys may change' attribute to be set in the XAB key option flag, if necessary, or modify the source program to detect and respond to the condition.
CHK
bucket format check failed for VBN = 'nnn' Facility: RMS, VMS Record Management Services Explanation: VMS RMS detected a corrupted bucket in an indexed file. The bucket address check or bucket checksum is incorrect. User Action: Reorganize the file, if possible; otherwise, re- create the file. The status value (STV) field of the FAB or RAB contains the starting virtual block number of the bucket in error. This error can be caused by hardware errors, VMS RMS or system software errors, or modifications of files by non-RMS programs. If RMS errors are suspected, submit a Software Performance Report (SPR).
CHKALTHOME
invalid alternate home block, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The alternate home block at the specified virtual block of the index file on the specified relative volume is corrupted. User Action: None. The utility refreshes the alternate home block from the primary home block.
CHKPRIHOME
invalid primary home block, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The primary home block at the specified virtual block of the index file on the specified relative volume is corrupted. The utility reconstructs the block. User Action: If the volume can no longer be mounted by the operating system, it is corrupted and must be reconstructed from backup media. If the volume can be mounted, the damage can be repaired by copying the volume to fresh media.
CHKSCB
invalid storage control block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The storage control block on the specified relative volume is corrupted. The utility reconstructs the block. User Action: If the volume can no longer be mounted by the operating system, it is corrupted and must be reconstructed from backup media. If the volume can be mounted, the damage can be repaired by copying the volume to fresh media.
CHMONIS
change mode instruction while on interrupt stack Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CHMVEC
CHM vector bits <1:0> not 0 Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CHN
assign channel system service request failed Facility: RMS, VMS Record Management Services Explanation: VMS RMS failed to assign a channel to a device specified for an input or output operation. This message is usually accompanied by a system message that indicates the reason for the failure. User Action: The status value (STV) field in the FAB contains the system status code that indicates the reason for the failure. Take corrective action based on these codes. If the error results from the DCL command OPEN, or following the DCL command @ (execute procedure) or the DCL command RUN, verify that the volume containing the specified file is on line and mounted.
CINBAD
connect not accepted/rejected as expected Facility: DTS, DECnet Test Program Protocol Explanation: This message indicates a test error. User Action: Ensure that the correct DTRECV or equivalent is available at the target node.
CINREJ
connect aborted, nsp reason is 'number' Facility: DTS, DECnet Test Program Protocol Explanation: The logical link to DTRECV could not be established. User Action: Interpret the Network Services Protocol (NSP) reason.
CIPORT
fatal error detected by VAXport driver (PADRIVER) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CJFERR
journaling error; volume dismounted to ensure data integrity Facility: MOUNT, Mount Utility Explanation: The attempt to activate the Recovery Unit Journal (RUJ) on the volume failed. Because the RUJ might contain an active recovery unit, the volume is dismounted to minimize the danger of corrupting the data on the volume. This message is usually followed by another message that describes the error condition that caused RUJ activation to fail. User Action: Correct the error conditon and reenter the MOUNT command, or reenter the MOUNT command including the /NOJOURNAL qualifier. With the latter approach, MOUNT will not attempt to activate the RUJ. This approach removes the symptom but not the cause of the failure and may leave the volume in an inconsistent state.
CJL
can't output line correctly - margins too narrow. Line will not be justified Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The text and spacing are greater than the number of character positions available between the margins. User Action: Truncate the line or use the Break flag to divide it.
CLASDISAB
class disabled Facility: MONITOR, Monitor Utility Explanation: One or more of the specified class names is not a valid MONITOR class. User Action: Check the list of valid MONITOR classes by entering the DCL command HELP MONITOR. Reenter the MONITOR command requesting only valid classes.
CLASMISS
requested class record missing from input file Facility: MONITOR, Monitor Utility Explanation: The class data records in the input recording file do not match information in the header for the file. This can only occur if the input file has been corrupted in some way. User Action: If you can demonstrate that a MONITOR recording file can be created with one MONITOR request, then, using that file as input, immediately run a second MONITOR request that produces this message. Submit a Software Performance Report (SPR).
CLASNP
some requested classes not present in input file Facility: MONITOR, Monitor Utility Explanation: One or more of the requested MONITOR classes is not present in the input file. This situation may result from having specified an incorrect input file with the /INPUT qualifier. User Action: The MONITOR request continues execution, monitoring only those requested classes that are present in the input recording file. If an incorrect input file has been specified, reenter the command, specifying the correct input file.
CLASUNK
some requested classes have file structure levels incompatible with the current version of MONITOR Facility: MONITOR, Monitor Utility Explanation: One or more of the requested MONITOR classes in the specified input recording file has a structure level incompatible with the current version of MONITOR. This situation may result from reading a file that is created by a version of MONITOR higher than the one currently running. User Action: No action is required. The MONITOR request will continue to execute, monitoring only those requested classes that are compatible with the version of MONITOR currently running.
CLIERR
CLI error parsing command line Facility: PATCH, Patch Utility Explanation: The command line that invokes PATCH is incorrectly entered. User Action: Reenter the command line correctly.
CLIFAIL
error activating command interpreter 'interpreter' Facility: LOGIN, Login Processor Explanation: An error occurred while attempting to invoke the command interpreter for your process. An accompanying message will provide more information. User Action: Correct the problem described by the accompanying message, and try again.
CLIFRCEXT
CLI forced exit Facility: SYSTEM, VMS System Services Explanation: The command interpreter forced an image to terminate abnormally. The debugger displays this informational message when an image is interrupted by Ctrl/Y and another command is entered. User Action: None.
CLIMISMATCH
CLI type of image does not match /CLI qualifier Facility: CDU, Command Definition Utility Explanation: CDU returns this message when you try to use the SET COMMAND/CLI=CLI-type command to modify command tables created by a CLI-type other than the one you have specified.
CLIPBOARDFAIL
unexpected clipboard failure Facility: VAXTPU, VAX Text Processing Utility Explanation: An unexpected clipboard failure has occurred. User Action: A software error has occurred. Please submit a Software Performance Report (SPR).
CLIPBOARDLOCKED
clipboard is locked by another process Facility: VAXTPU, VAX Text Processing Utility Explanation: The clipboard is locked by another process. User Action: Repeat the clipboard operation after the other process has finished with the clipboard.
CLIPBOARDNODATA
clipboard does not contain the requested data Facility: VAXTPU, VAX Text Processing Utility Explanation: The clipboard does not contain the requested data. User Action: Repeat the clipboard operation after the other process has finished with the clipboard.
CLIPBOARDZERO
clipboard data has 0 length Facility: VAXTPU, VAX Text Processing Utility Explanation: The data to be written to the clipboard has zero length. User Action: Only specify nonzero length data to be written to the clipboard.
CLIPROT
error protecting command interpreter pages Facility: LOGIN, Login Processor Explanation: An error occurred while trying to protect the command interpreter pages. An accompanying message will provide more information. User Action: Correct the problem described by the accompanying message, and try again.
CLIQUAL
the /CLI qualifier value conflicts with CLI type in tables Facility: CDU, Command Definition Utility Explanation: The CDU outputs this message when you try to use the SET COMMAND/CLI=cli-type command to modify command tables created by a CLI-type other than the one you have specified. User Action: Specify different command tables, generated by the appropriate CLI, or use a different CLI-type in the command.
CLISYMTBL
error creating space for command interpreter symbol table Facility: LOGIN, Login Processor Explanation: An error occurred while trying to create virtual address space for the command interpreter symbol table. An accompanying message will provide more information. User Action: Correct the problem described by the accompanying message, and try again.
CLIWARNMSG
Warning: /CLITABLES field may need to reflect changes to /CLI field Facility: AUTHORIZE, Authorize Utility Explanation: If you modify the command language interpreter (CLI) field of a record in the system user authorization file, you may have to modify the CLITABLES field to reflect the change. If you have set the CLI field to DCL or MCR, however, the CLITABLES field defaults to the correct value. User Action: If you have changed the CLI field to a value other than DCL or MCR, use the AUTHORIZE command MODIFY/CLITABLES to set the CLITABLES field to the corresponding tables. Refer to the description of the LOGIN procedure in the VMS DCL Dictionary for further information about specifying CLI tables.
CLOSEDEL
error closing 'filename' Facility: Shared by several facilities Explanation: An error occurred while a file is being closed after a delete operation. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
CLOSEERR
an error occurred closing 'filename' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received an error from RMS while trying to close a Files-11 file. User Action: This message will be followed by one or two error messages reporting the actual condition discovered by RMS. Take corrective action suggested by the RMS error messages, then retry the command.
CLOSEERR
error closing 'filespec' Facility: Shared by several facilities Explanation: The specified file cannot be closed. Usually an accompanying RMS message indicates why the file cannot be closed. User Action: Take corrective action based on the accompanying message.
CLOSEERR
error closing 'filespec' Facility: SET, SET Facility Explanation: An error occurred while trying to close a file whose characteristics have just been set. This message is accompanied by a message explaining why the file could not be closed. User Action: Respond to the accompanying message.
CLOSEFILE
error closing event file 'file-id' Facility: EVL, Event Logger Explanation: An error occurred while closing an event file. User Action: None. This message displays the name of the file.
CLOSEFOREIGN
an error occurred closing the volume 'volume' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received an error from RMS while trying to close a connection to a foreign-mounted volume. User Action: This message will be followed by one or two error messages reporting the actual condition discovered by RMS. Take corrective action suggested by the RMS error messages, then retry the command.
CLOSEIN
error closing 'input-filespec' as input Facility: Shared by several facilities Explanation: During a VMS RMS operation, an error is encountered while closing an input file. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
CLOSEIN
error closing input file 'filespec' Facility: VAXTPU, VAX Text Processing Utility Explanation: A VMS RMS error occurred while closing the specified input file. The message should be accompanied by a VMS RMS message indicating the reason for the error. User Action: Follow the recovery procedure for the specified VMS RMS message.
CLOSEIN
unable to close input Facility: ACCOUNTING, Accounting Utility Explanation: During a VMS RMS operation, an error is encountered while closing an input file. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
CLOSEJOB
error closing job 'job-name' for user 'user-name' in queue 'queue- name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempt to close the job. User Action: The accompanying message gives information about the failed operation. Correct the problem and retry the upgrade.
CLOSEMON
error disconnecting monitor process 'sink-name' Facility: EVL, Event Logger Explanation: An error occurred while disconnecting a monitor process. User Action: None. This message displays the name of the monitor program.
CLOSEOUT
error closing 'output-filespec' as output Facility: Shared by several facilities Explanation: During a VMS RMS operation, an error is encountered while closing an output file. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the accompanying message.
CLOSEOUT
error closing output file 'filespec' Facility: VAXTPU, VAX Text Processing Utility Explanation: A VMS RMS error occurred while closing the specified output file. The message should be accompanied by a VMS RMS message indicating the reason for error. User Action: Follow the recovery procedure for the specified VMS RMS message.
CLOSEOUT
unable to close output Facility: ACCOUNTING, Accounting Utility Explanation: During a VMS RMS operation, an error is encountered while closing an output file. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the accompanying message.
CLREFCFER
error clearing UETP common event flag cluster Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error prior to its termination. This error is received in relation to a previously displayed error condition. User Action: Ignore this error if UETP completed successfully or correct the condition leading to this problem and re-run the test. If the error persists, submit a Software Performance Report (SPR).
CLSERR
close error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: The $CLOSE request failed due to the error represented as xx. User Action: Correct the error (represented as xx) and retry.
CLSTBLERR
device class value, 'value' not in class tables Facility: ERF, Error Log Utility Explanation: The specified class value is unsupported. User Action: Submit a Software Performance Report (SPR).
CLUBELBAS
base address of 'address' for cluster 'cluster-name' is below image base of 'address' Facility: LINK, Linker Utility Explanation: In the creation of a based shareable image, a cluster is specified with a lower base address than the address specified in the BASE= option. User Action: Specify a base address for the cluster that is higher than the address specified in the BASE= option.
CLUEXIT
node Exiting Cluster Facility: BUGCHECK, System Bugcheck Explanation: To avoid partitioning of the VAXcluster, this system exited the VAXcluster by crashing. Generally, this is a normal condition. If the condition persists, this processor is most probably configured incorrectly into two distinct VAXclusters. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. Explanation: Ensure that the VAXcluster is properly configured.
CLUGDIFF
*Warning* - CAF for node 'nnnnnn' has group 'm' Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SHOW CLUSTER_AUTHORIZATION command is entered in a CLUSTER environment, and not all nodes in the cluster have the same group number. User Action: Enter a CONFIGURATION SET CLUSTER_AUTHORIZATION command to ensure that system disks for all members indicate the same group number and password.
CLULIST
CLUSTER is invalid with a list of nodes Facility: SYSMAN, Cluster System Management Utility Explanation: In a SET ENVIRONMENT command, a /CLUSTER qualifier cannot be specified if a /NODE qualifier includes more than one node. SYSMAN cannot perform clusterwide operations on more than one cluster at a time. User Action: If a clusterwide environment is desired, it is only necessary to specify one node in the cluster, or omit the NODE qualifier if the local cluster is desired.
CLUPDIFF
*Warning* - CAF for node 'nnnnnn' has different password Facility: SYSMAN, Cluster System Management Utility Explanation: A CONFIGURATION SHOW CLUSTER_AUTHORIZATION command is entered in a CLUSTER environment, and not all nodes in the cluster have the same password. User Action: Enter a CONFIGURATION SET CLUSTER_AUTHORIZATION command to ensure that system disks for all members indicate the same group number and password.
CLUSTER
unsuitable cluster factor Facility: INIT, INITIALIZE Command Explanation: The cluster size specified for a DCL command INITIALIZE is either too small or too large for the volume. The maximum cluster size for any volume is 1/100 the size of the volume. The minimum size is calculated by dividing the disk size by 1,044,480 (that is, 255 x 4096). User Action: Recalculate a cluster size for the volume that is within the valid range and reenter the command.
CLUSTER
unsuitable cluster factor for 'device-name' Facility: BACKUP, Backup Utility Explanation: During an attempt to initialize an output volume, the Backup Utility found that the cluster factor is too large or too small for the specified device. User Action: If the input is a save set, use the BACKUP/LIST command to determine the volume initialization parameters of the input volumes. Refer to the description of the DCL command INITIALIZE, determine a suitable cluster factor, and initialize the output volumes using the DCL command INITIALIZE. Then, reenter the command specifying the /NOINITIALIZE qualifier.
CMDCAN
command canceled Facility: NCP, Network Control Program Explanation: Ctrl/C is typed in response to a prompt. This cancels the current command and returns you to the NCP> prompt. User Action: Retry the operation.
CMDERR
I/O error reading commands Facility: NCP, Network Control Program Explanation: RMS returned an error while reading commands from SYS$INPUT. The RMS error message describes the error condition. User Action: Take corrective action based on the accompanying RMS message.
CMDERROR
error reported by command executor Facility: LAT, LAT Facility Explanation: The command executor module for LATCP cannot execute the command for the reason given in the accompanying message. User Action: Correct the situation based on the information in the accompanying message.
CMDINPUT
error reading command input Facility: LOGIN, Login Processor Explanation: An error occurred while attempting to read the input file. An accompanying message will provide more information. The most common cause is a read timeout while trying to obtain the user name or password. User Action: Correct the problem described by the accompanying message, and try again.
CMDLIN
command line segment in error 'error' Facility: DIFF, DIFFERENCES Command Explanation: Part of the command line is syntactically incorrect. User Action: Specify the correct syntax in the command line.
CMDNOTFND
command not found - use RECALL/ALL to display saved commands Facility: CLI, Command Language Interpreter (DCL) Explanation: The command that you tried to find using RECALL is not found. User Action: Use the RECALL/ALL to display all the saved commands and then modify and reenter your RECALL command.
CMDNOTVLD
command not valid on the running system Facility: SDA, System Dump Analyzer Explanation: You entered an SDA command while analyzing the running system. The command is valid only when analyzing a dump file. User Action: None. The command is not valid while analyzing the running system.
CMDOBS
command obsolete - ignored Facility: LAT, LAT Facility Explanation: The specified LATCP command is obsolete; the command is ignored. User Action: Discontinue use of this command.
CMDOBS
MSCP server must be loaded by setting SYSBOOT parameter MSCP_LOAD Facility: SYSGEN, System Generation Utility Explanation: The MSCP command within SYSGEN is now obsolete. The proper way for loading the MSCP server is to set the SYSGEN parameter MSCP_LOAD. This will load the MSCP server during SYSBOOT. User Action: Setting the SYSGEN parameter to load the MSCP server during SYSBOOT will result in a warning when the MSCP command within SYSGEN is entered. If this error is printed as the result of a startup command procedure, changing the parameter to load the server earlier will enable the old command procedure to complete successfully with only a warning message.
CMDSYNTAX
command line syntax error Facility: LINK, Linker Utility Explanation: A command syntax error is detected by the command interpreter. User Action: Reenter the command correctly.
CMDSYNTAX
command syntax error Facility: DIFF, DIFFERENCES Command Explanation: The syntax of the DIFFERENCES command line is incorrect. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary to determine the correct command syntax and reenter the command.
CMDTOOLONG
command line exceeds maximum length Facility: AUTHORIZE, Authorize Utility Explanation: The length of your command, after any symbols and logical names have been expanded, exceeds the maximum allowable length. User Action: Reenter a shorter form of the command.
CMDTOOLONG
command line too long in options file 'filename' Facility: LINK, Linker Utility Explanation: An options file line is too long. User Action: Shorten the line and relink.
CMODSUPR
change mode to supervisor trap, code = 'nnn', PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An image attempted to execute a change mode to supervisor instruction, but the image did not have a change mode handler declared. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. The code displayed in the message is the change mode code specified in the instruction. User Action: Examine the PC and virtual address displayed in the message to determine which instruction caused the error.
CMODUSER
change mode to user trap, code = 'nnn', PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An image attempted to execute a change mode to user instruction, but the image did not have a change mode handler declared. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine which instruction caused the error.
CMPOUTF11
the /COMPARE qualifier requires save set as first input Facility: BACKUP, Backup Utility Explanation: In a compare operation between a save set and a disk volume, you must specify the save set as the first input and the disk volume as the second input. User Action: Correct and reenter the command.
CNF
character string expected, not found: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A required character string is missing. User Action: Supply the missing string.
CNFOVR
internal error - Too many cluster members Facility: SMI, System Management Integrator/Server Explanation: The configuration table in SMIREMOTE has overflowed. User Action: Submit a Software Performance Report showing all SYSMAN commands leading to this error. Also, submit the output of the SHOW CLUSTER command.
CNFQUAVAL
conflicting qualifier values for 'qualifier', 'qualifier' Facility: ERF, Error Log Utility Explanation: Two or more conflicting qualifiers were specified. User Action: Use the DCL HELP command or refer to the VMS DCL Dictionary to determine the qualifiers in conflict and reenter the command.
CNS
command not supported: 'number' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The command is not supported by this version of DSR; the number in the message is an internal Digital number. User Action: Remove or replace the command.
CNTERR
connect error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: A VMS RMS $CONNECT request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry the request.
CNTRLY
Are you repeating ^Y to abort the remote session on node 'node- name'? Facility: REM, Set Host Facility Explanation: This message provides an opportunity to terminate the connection if logging out is not possible on the remote node. User Action: Enter YES or NO.
CNTRSOBS
counters command qualifier obsolete - command ignored Facility: LAT, LAT Facility Explanation: The LATCP command SHOW COUNTERS is obsolete; the command is ignored. User Action: Discontinue use of the SHOW COUNTERS command.
CNVRTING
'library filespec' is a copy of 'old library filespec' Facility: LIBRAR, LIBRARY Command Explanation: This informational message is generated by the DCL command LIBRARY. The specified modification to a Version 1.0 library automatically converts it to the new library format. User Action: None.
CNXMGRERR
error detected by Connection Manager Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
COB
can't open binary output file 'filespec' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR cannot create the BRN file required to generate a table of contents from the titles and header levels. User Action: Check to see if you have write access to your current default directory. If the problem continues, notify the system manager.
COD
invalid or unsupported type field in XAB at 'address' Facility: RMS, VMS Record Management Services Explanation: The XAB at the indicated address contains an invalid type code field, or the XAB is not valid. User Action: The status value (STV) field of the FAB provides the address of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
COF
can't open footnote work file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR cannot create the temporary file required to process the footnote information. User Action: Check to see if you have write access to your current default directory and enough quota. If the problem continues, notify the system manager.
COI
can't open input file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The input file specification is erroneous, the file is nonexistent, or you do not have read access to the file. User Action: Check the file specification for errors, or check to see if you have read access to the file. If the problem continues, notify the system manager.
COLLERR
error during data collection Facility: MONITOR, Monitor Utility Explanation: An unexpected error occurred while collecting the requested MONITOR data. More information can be obtained by examining the linked message that follows this one. User Action: Correct the error indicated by the linked message and rerun the MONITOR command. If the linked message is NOPRIV, it may indicate that the Monitor Utility is not installed with the required privileges. Please report such a problem to the system manager.
COMBCLU
cannot combine multiple classes with the cluster class Facility: MONITOR, Monitor Utility Explanation: The CLUSTER class cannot be combined with other classes. User Action: Reenter your command with only the CLUSTER class listed.
COMCOD
compilation 'error' in module 'module-name' file 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: This warning message is generated by the DCL command LIBRARY. The object module you are inserting contains a compilation error, warning, or an illegal compilation code. User Action: Recompile the module before reentering the command line.
COMFAIL_
a communication failure is detected Facility: DTK, DECtalk Facility Explanation: A communications malfunction occurred since the DECtalk device was turned on. User Action: Check the DECtalk hardware.
COMFIL
contents of component database Facility: SYSMAN, Cluster System Management Utility Explanation: The following output is being generated from the startup component file on the named system. User Action: None.
COMFILEMTY
startup component database is empty Facility: SMI, System Management Integrator/Server Explanation: The current startup component entry does not have any entries. User Action: Use the SYSMAN command STARTUP ADD FILE to add entries to this database before using commands to examine or modify entries.
COMMA
requested value is terminated by a comma Facility: CLI, Command Language Interpreter (DCL) Explanation: The returned value is terminated by a comma, implying that additional values are in the list. User Action: None. Command buffer exhausted Facility: EDT, EDT Editor Explanation: The string of change mode commands exceeds 255 characters. User Action: Divide the string into several lines and reenter the command. Command buffer exhausted during XLATE command processing Facility: EDT, EDT Editor Explanation: You have put too many characters in your XLATE procedure. EDT can handle only 255 characters per command line. User Action: Enter fewer characters. Command file could not be closed Facility: EDT, EDT Editor Explanation: The startup command file cannot be closed. The appropriate system message provides more information on the nature of the problem. User Action: Correct the problem indicated by the accompanying message. Command file could not be opened Facility: EDT, EDT Editor Explanation: The command file given in the command line cannot be opened. EDT will display an associated file system message for the error. User Action: Correct the problem indicated by the file system message. Command file does not exist Facility: EDT, EDT Editor Explanation: The command file parameter in the command line does not exist in the specified directory. User Action: Reenter the command specifying a command file parameter that does exist in the specified directory.
COMMERROR
unexpected error #'number' in communicating with node CSID 'number' Facility: QMAN, Queue Manager Explanation: The queue manager encountered an internal error. The accompanying message provides more information about the cause of the error. User Action: Submit a Software Performance Report (SPR) and include the message text. Create a copy of all *.QMAN$JOURNAL* files using the BACKUP/IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR, along with any SYS$SYSTEM:QMAN$QUEUE_MANAGER.DMP files. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_CONTROL username.
COMM_FAIL
DECdtm transaction manager communications failure prior to voting Facility: DDTM, DECdtm Transaction Manager Explanation: The transaction aborted because of a communications failure between two DECdtm transaction managers involved in the transaction. User Action: Check the network links between the nodes involved in the transaction.
COMMHARD
communications hardware error detected Facility: SYSTEM, VMS System Services Explanation: A hardware error has occurred on the DUP11, the local modem, or the line between the modem and the DUP11, while the 3271 Protocol Emulator is active. On a write request, there is a UNIBUS timeout returned by the DEUNA hardware. User Action: Check the lines for obvious hardware problems, for example, a disconnected plug. If the error still occurs, consult the Digital Services Group. The UNIBUS should be checked to make sure it is not overloaded and that all devices on the UNIBUS are working properly.
COMOREXE
filename not of type COM or EXE Facility: SYSMAN, Cluster System Management Utility Explanation: A startup component file name contains a file type other than COM or EXE. User Action: Use STARTUP MODIFY to correct the file name.
COMPARED
compared 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility has successfully completed a compare operation. This message is displayed only when the /LOG command qualifier is used. User Action: None.
COMPAT
compatibility mode fault (code 'nnn') at PC 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An RSX-11M image attempted to execute an illegal instruction, indicated by one of the following codes: Code Meaning 0 Reserved instruction execution 1 BPT instruction executed 2 IOT instruction executed 3 EMT instruction executed 4 TRAP instruction executed 5 Illegal instruction executed 6 Odd address fault 7 TBIT trap User Action: Check for a programming error and make any necessary corrections.
COMPBEGIN
comparing queue file 'filespec' to queue file 'filespec' beginning at 'date-and-time' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This informational message reports that the specified queue files are being compared. User Action: None.
COMPEND
comparing queue file 'filespec' to queue file 'filespec' ended at 'date-and-time' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This informational message reports that comparison of the specified queue files has completed. User Action: None.
COMPFAIL
comparison found differing values for field 'type-of-field' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: Different values for the specified field in the two queue files are being compared. This message is followed by a message that specifies the two different values for the field. User Action: If the specified difference is undesirable, attempt to make appropriate changes according to the accompanying message.
COMPILED
compilation completed without errors Facility: VAXTPU, VAX Text Processing Utility Explanation: The execution of the built-in procedure COMPILE has been successfully completed; that is, a procedure, string, or buffer has been compiled without warnings or errors. User Action: None.
COMPILEFAIL
compilation aborted Facility: VAXTPU, VAX Text Processing Utility Explanation: A syntax error exists in the program you are trying to compile. The compilation of the program is prematurely terminated. User Action: Correct the syntax error and recompile your program.
COMPLETE
processing complete 'string' Facility: DSR, DIGITAL Standard Runoff Explanation: This informational message reports that the DSR Table of Contents Utility has completed processing the indicated input file. User Action: None.
COMPLX
expression too complex - simplify Facility: CLI, Command Language Interpreter (DCL) Explanation: The command interpreter cannot analyze an arithmetic expression in a command, because it contains too many operators and/or parentheses. User Action: Shorten the expression and reenter the command. If necessary, execute more than one command.
COMPSYNC
queue file 'filespec' is missing 'type-of-data' 'name-of-item' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: The specified queue file is missing the specified item. The item is skipped over in an attempt to resynchronize comparison of the remaining data in the two queue files. User Action: Specify the item in both queue file descriptions, retry the upgrade, or attempt to make appropriate changes at the DCL level.
COMREMJBC
error communicating with another job controller Facility: JBC, Job Controller Explanation: The job controller encountered an error communicating with a job controller on another processor in a VAXcluster. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
COMSTA
component in wrong state Facility: NCP, Network Control Program Explanation: A component is in a state inconsistent with the request; for example, a down-line load is attempted over a line with OFF status. User Action: Check the status of the component and reenter your command.
CONABORT
connection to node 'node-name' aborted by CTRL/C Facility: MAIL, Mail Utility Explanation: The user typed Ctrl/C while MAIL is attempting to connect to the specified node. The transmission of the message is aborted. User Action: None.
CONATMPT
continuing attempts to connect to 'service-name' Facility: LAT, LAT Facility Explanation: A SET HOST/LAT connection failed and is being retried. This informational message is seen only if the /AUTOCONNECT qualifier is specified on SET HOST/LAT. User Action: You can enter Ctrl/Y to cancel the retry.
CONCAT
requested value is terminated by a plus sign Facility: CLI, Command Language Interpreter (DCL) Explanation: The returned value is concatenated to the next value with a plus sign, implying that additional values are in the list. User Action: None.
CONCEALED
logical device name concealed physical device name Facility: SYSTEM, VMS System Services Explanation: This alternate success status indicates that the system service completed successfully, and the device name that is supplied as input to the service translated to a concealed device. User Action: None.
CONERR
connect error Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
CONFAIL
connection to 'service-name' not established Facility: LAT, LAT Facility Explanation: A SET HOST/LAT connection attempt was not successful. User Action: Take appropriate action based on information in the accompanying message.
CONFATTR
conflicting attributes in definition Facility: CDU, Command Definition Utility Explanation: The CLD file has conflicting attributes. Attributes are mutually exclusive (for example, a CLD file can name both an image and a routine). User Action: Remove one of the mutually exclusive attributes from the CLD file.
CONFBASADR
conflicting base address for image 'image-name' base of 'address' in file 'filename' conflicts with base of 'address' in file 'filename' Facility: LINK, Linker Utility Explanation: A shareable image contained in two other based shareable images, both of which were included in the link, is found to be at two separate virtual addresses. User Action: Either (1) correct one or both of the based shareable images giving the shareable image in question the same base address in both images, or (2) make both based shareable images position independent.
CONFCON
CONCATENATE has already been specified Facility: CDU, Command Definition Utility Explanation: CDU encountered a NOCONCATENATE clause after processing a CONCATENATE clause in the same value definition. NOCONCATENATE and CONCATENATE clauses cannot be specified in the same value definition. User Action: Edit the CLD file so that each value definition does not contain both CONCATENATE and NOCONCATENATE clauses.
CONFDEFREQ
only one DEFAULT or REQUIRED clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one DEFAULT or REQUIRED clause in a single value definition. Only one DEFAULT or REQUIRED clause is allowed per value definition. User Action: Edit the CLD file so that each value definition does not contain more than one DEFAULT or REQUIRED clause.
CONFDEL
'filename', delete? (Y or N): Facility: Shared by several facilities Explanation: This message requests interactive confirmation before deleting the indicated file. User Action: Type Y if you want the file deleted, and type N if you do not want it deleted.
CONFDIS
a DISALLOW clause has been specified Facility: CDU, Command Definition Utility Explanation: CDU encountered a NODISALLOWS clause after a DISALLOW clause is processed in a single verb/syntax definition. NODISALLOWS cannot be specified in a verb/syntax definition in which DISALLOWS is previously specified. User Action: Edit the CLD file so that each verb/syntax definition does not contain both DISALLOW and NODISALLOWS clauses.
CONFFAC
facility definition conflicts with previous definition Facility: MESSAGE, Message Utility Explanation: The same facility name or facility number is specified for two different facilities. User Action: Reenter the facility definitions so that each facility name corresponds to one facility number.
CONFIXMEM
conflicting virtual memory requirement for fixup section for image 'image-name' Restructure image or eliminate based shareable images Facility: LINK, Linker Utility Explanation: The linker is unable to allocate virtual memory for the fixup section because a based shareable image is taking up the space. User Action: Restructure the set of shareable images to be nonbased, or leave enough space between them for the object modules.
CONFLICT
illegal combination of command elements - check documentation Facility: CLI, Command Language Interpreter (DCL) Explanation: Two or more qualifiers, keywords, or parameters that cannot be used in combination were used in the same command line. User Action: Remove the offending element.
CONFLICT
the /PASSWORD and /GENERATE_PASSWORD qualifiers are mutually exclusive Facility: AUTHORIZE, Authorize Utility Explanation: The /PASSWORD qualifier and the /GENERATE_PASSWORD qualifier are mutually exclusive. User Action: Reenter the command with one qualifier.
CONFMEM
conflicting virtual memory requirement at 'address' for 'decimal- number' pages in cluster 'cluster-name' Facility: LINK, Linker Utility Explanation: Virtual memory required for a cluster has already been allocated. User Action: Correct and relink.
CONFNEG
NEGATABLE has already been specified Facility: CDU, Command Definition Utility Explanation: CDU has encountered a NONNEGATABLE clause after processing a NEGATABLE clause in the same keyword definition. A NEGATABLE clause and a NONNEGATABLE clause cannot be specified in the same keyword definition. User Action: Edit the CLD file so that each keyword definition does not contain both NEGATABLE and NONNEGATABLE clauses.
CONFNOCON
NOCONCATENATE has already been specified Facility: CDU, Command Definition Utility Explanation: CDU encountered a CONCATENATE clause after processing a NOCONCATENATE clause in the same value definition. CONCATENATE and NOCONCATENATE clauses cannot be specified in the same value definition. User Action: Edit the CLD file so that each value definition does not contain both CONCATENATE and NOCONCATENATE clauses.
CONFNODIS
NODISALLOWS has already been specified Facility: CDU, Command Definition Utility Explanation: CDU encountered a DISALLOW clause after a NODISALLOWS clause is encountered in a single verb/syntax definition. DISALLOW cannot be specified in a verb/syntax definition in which NODISALLOWS is previously specified. User Action: Edit the CLD file so that each verb/syntax definition does not contain both NODISALLOWS and DISALLOW clauses.
CONFNONNEG
NONNEGATABLE has already been specified Facility: CDU, Command Definition Utility Explanation: CDU has encountered a NEGATABLE clause after a NONNEGATABLE clause is processed in the same keyword definition. A NONNEGATABLE clause and the NEGATABLE clause cannot be specified in the same keyword definition. User Action: Edit the CLD file so that each keyword definition does not contain both NEGATABLE and NONNEGATABLE clauses.
CONFNOPARM
NOPARAMETERS has already been specified Facility: CDU, Command Definition Utility Explanation: CDU encountered a PARAMETER clause after a NOPARAMETERS clause is encountered in a single verb/syntax definition. A PARAMETER clause cannot be specified in the same verb/syntax definition as NOPARAMETERS. User Action: Edit the CLD file so that each verb/syntax definition does not contain both NOPARAMETERS and PARAMETER clauses.
CONFNOQUAL
NOQUALIFIERS has already been specified Facility: CDU, Command Definition Utility Explanation: CDU has encountered a QUALIFIER clause after a NOQUALIFIERS clause is processed in the same verb/syntax definition. A QUALIFIER clause cannot be specified in the same verb/syntax definition as the NOQUALIFIERS clause. User Action: Edit the CLD file so that each verb/syntax definition does not contain both NOQUALIFIERS and QUALIFIER clauses.
CONFOUTPUTS
only one OUTPUTS clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one OUTPUTS clause in a single verb/syntax definition. Only one OUTPUTS clause is allowed per verb/syntax definition. User Action: Edit the CLD file so that each verb/syntax definition does not contain more than one OUTPUTS clause.
CONFPARM
a parameter has already been defined Facility: CDU, Command Definition Utility Explanation: CDU encountered a NOPARAMETERS clause after a PARAMETER clause is processed in a single verb/syntax definition. A NOPARAMETERS clause cannot be specified in a verb/syntax definition in which PARAMETER is previously specified. User Action: Edit the CLD file so that each verb/syntax definition does not contain both PARAMETER and NOPARAMETERS clauses.
CONFQUAL
a qualifier has already been defined Facility: CDU, Command Definition Utility Explanation: CDU encountered a NOQUALIFIERS clause after a QUALIFIER clause is encountered in a single verb/syntax definition. A NOQUALIFIERS clause cannot be specified in a verb /syntax definition in which the QUALIFIER clause is previously specified. User Action: Edit the CLD file so that each verb/syntax definition does not contain both QUALIFIER and NOQUALIFIERS clauses.
CONFQUAL
conflicting qualifiers Facility: CONVERT, Convert Utility Explanation: You have specified qualifiers that are mutually exclusive. For example, the /MERGE and the /APPEND qualifiers cannot be specified at the same time since they operate with files of different organization. User Action: Change the qualifiers and try again.
CONFQUAL
conflicting qualifiers Facility: Shared by several facilities Explanation: Two or more conflicting qualifiers were specified. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary to determine the qualifiers in conflict and reenter the command.
CONFQUAL
conflicting qualifiers, request aborted Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN command AUTOCONFIGURE is entered specifying both the /EXCLUDE and /SELECT qualifiers. User Action: Reenter the command with only one qualifier.
CONFQUAVAL
values for /DISCONNECT and /BREAK must be different Facility: LAT, LAT Facility Explanation: The SET HOST/LAT command specified the same character for both the /DISCONNECT and /BREAK qualifiers. User Action: Specify different characters for the /DISCONNECT and /BREAK qualifiers.
CONFROUTIMG
only one routine or image clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one IMAGE or ROUTINE clause in a single verb/syntax definition. IMAGE and ROUTINE clauses are mutually exclusive. User Action: Edit the CLD file so that each verb/syntax does not contain more than one IMAGE or ROUTINE clause.
CONLOST
connection to 'service-name' terminated Facility: LAT, LAT Facility Explanation: After a SET HOST/LAT connection was established, an error condition occured that caused the connection to be abnormally terminated. User Action: Determine the availability of the node that had the connection broken.
CONNEC
unable to connect to listener Facility: NCP, Network Control Program Explanation: NCP is unable to connect to NML to perform network operations. Information accompanying this message explains any secondary reasons for this error. Your network may not be configured correctly, your access control information may be invalid, or all files may not be present. User Action: If you receive this message upon entering the SET EXECUTOR NODE command, then you should try the command again after correcting the problem or after supplying valid access control information. You may then resume entering NCP commands. Inspect the log file created by NML on the destination node to see if it provides additional information as to the cause of the problem.
CONNECFAIL
connect to network object timed-out or failed Facility: SYSTEM, VMS System Services Explanation: The remote node did not respond to the logical-link request. User Action: Check to see if the node is reachable and retry.
CONNECTED
session to 'service-name' on node 'node-name' established Facility: LAT, LAT Facility Explanation: The SET HOST/LAT session has been established to the specified service and node. No node name is specified in the message when the node is the same as the service. User Action: None.
CONSEQERR
a control sequence malfunction is detected Facility: DTK, DECtalk Facility Explanation: A DECtalk private control sequence malfunction occurred since the DECtalk device was turned on. User Action: Check the DECtalk hardware. Consistency check failed, please check your file Facility: EDT, EDT Editor Explanation: There is a discrepancy between the number of lines and characters present when the editing session ends. This message indicates an EDT problem. User Action: Check for possible errors in your output file. Submit a Software Performance Report (SPR).
CONSTRTOOLARGE
constant string too large Facility: VAXTPU, VAX Text Processing Utility Explanation: A constant declaration includes a constant expression that exceeds the internal tables of the compiler. User Action: Use an expression that generates a shorter string.
CONTIMEOUT
connection timed out, server not available, or incorrect server name Facility: LAT, LAT Facility Explanation: A LAT connection attempt on a LAT device (LTAxxx:) failed when the connection request timed out. Either the remote node was not available or the LTA device describing the destination to receive the connection was set up incorrectly. User Action: Check the mapping for the LTA device from which the connection was attempted or check to see whether the remote node described by the LTA device is available on the network.
CONTINUE
unable to continue processing 'filespec' Facility: BACKUP, Backup Utility Explanation: The specified file, which is being processed at a change of save set volumes, is no longer accessible. The accompanying message provides additional information and the Backup Utility terminates processing of the file. If other file activity is occurring on the volume, the error is probably caused because another user deleted the file during the backup process. User Action: Note that the file is incompletely processed.
CONTINUED
'save set spec' contains a continued file - cannot append Facility: BACKUP, Backup Utility Explanation: In a save operation with the /NOREWIND qualifier, the specified volume contained a multivolume file that is continued on another volume, and therefore a file cannot be appended to the volume. User Action: Retry the operation using the /REWIND qualifier to force BACKUP to initialize the output volume, or use another volume.
CONTRACT
contract virtual address space error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CONTRADEF
contradictory definition for variable or constant 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The variable or constant definition contradicts its previous definition. User Action: Rename the variable or constant to a unique name, or change the definition to match its previous definition.
CONTROLC
operation aborted by CTRL/C Facility: VAXTPU, VAX Text Processing Utility Explanation: The program stopped executing because you pressed Ctrl/C. User Action: None. However, if you have kept a journal file, you can exit from VAXTPU and restart the session.
CONTROLC
operation completed under CTRL/C Facility: LAT, LAT Facility Explanation: The LATCP command completed after you entered Ctrl/C. User Action: None.
CONTROLC
operation completed under CTRL/C Facility: RMS, VMS Record Management Services Explanation: An operation did not finish because Ctrl/C is pressed. The operating system does not normally display this message. User Action: None.
CONTROLC
operation completed under CTRL/C Facility: SYSTEM, VMS System Services Explanation: An operation did not finish because Ctrl/C is pressed. This message indicates success. User Action: None.
CONTROLO
operation completed under CTRL/O Facility: RMS, VMS Record Management Services Explanation: An operation did not finish because CTRL/O is pressed. The operating system does not normally display this message. User Action: None.
CONTROLO
output completed under CTRL/O Facility: SYSTEM, VMS System Services Explanation: An output operation to the terminal did not finish because Ctrl/O is pressed. The operating system does not normally display this message. User Action: None.
CONTROLY
operation completed under CTRL/Y Facility: SYSTEM, VMS System Services and RMS, VMS Record Management Services Explanation: An operation did not finish because Ctrl/Y is pressed. The operating system does not normally display this message. User Action: None.
CONVERT_STALL
destination log file too small - conversion aborted Facility: LMCP, Log Manager Control Program Explanation: An attempt was made to convert an existing log file to a destination log file that is too small. During the conversion the log manager stalled, indicating an inadequate destination log file size. User Action: To continue with the operation, specify a larger destination log file size in the command line.
COO
can't open output file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The output file specification is erroneous, or you do not have write access to the file. User Action: Check the file specification for errors, or check to see if you have write access to the file. If the problem continues, notify the system manager.
COPIED
copied 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility successfully completed a save operation. This message is displayed only if the /LOG qualifier is specified. User Action: None.
COPIEDB
input-filespec copied to output-filespec ('nnn' blocks)
Facility: Shared by several facilities
Explanation: This informational message displays the number of
blocks or the number of blocks copied, based on the size of the
input files.
User Action: None.
COPIEDC
'input-filespec' copied to 'output-filespec' ('nnn' records packed
into 'mmm' blocks)
Facility: Shared by several facilities
Explanation: This informational message displays the number of
records read in from the input file and the number of blocks
written to the output file.
User Action: None.
COPIEDR
input-filespec copied to output-filespec ('nnn' records)
Facility: Shared by several facilities
Explanation: This informational message displays the number of
records or the number of records copied, based on the size of the
input files.
User Action: None.
COPMSG
user record copied Facility: AUTHORIZE, Authorize Utility Explanation: This message is informational. User Action: None.
COPY_LOG
copy of log from 'log-filename' follows: Facility: UETP, User Environment Test Package Explanation: The current process has been created and is communicating with other processes in the UETP. To centralize the reporting of information about the progress of the UETP, this process is copying the log file from the execution of one of those processes. User Action: None.
COPY_LOG_ENDED
end of log file from 'filespec' Facility: UETP, User Environment Test Package Explanation: The current process has finished copying the log file introduced by the UETP$_COPY_LOG message. User Action: None.
COPY_LOG_LINE
'text' Facility: UETP, User Environment Test Package Explanation: The current process is copying a line of the file introduced by the UETP$_COPY_LOG message. Normally, only the text being copied appears; the facility, severity, and IDENT fields are not printed. User Action: None.
COR
can't open required file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The required file specification is erroneous, or the file is nonexistent, or you do not have read access to the file. User Action: Check the file specification for errors, or check to see if you have read access to the file. If the problem continues, notify the system manager.
CORRUPTEMB
EMB packet header has been corrupted Facility: BUGCHECK, System Bugcheck Explanation: The system has detected corruption of the system error log buffers. The system allocates space for error log entries from a set of common buffers. System software that makes use of the error logging routines typically writes into these entries. This message occurs when an attempt to write into an error log entry has overwritten other parts of the system error log buffers. The most common cause of this error is a coding error within a device driver. User Action: Submit a Software Performance Report (SPR) that includes a BACKUP save set of the system dump file generated by this error. (Use the /IGNORE=NOBACKUP qualifier on the BACKUP command that produces the save set included with your SPR.) Could not align tabs with cursor Facility: EDT, EDT Editor Explanation: The cursor is in a position where it cannot be evenly divisible by the tab size when the tab compute function is used. User Action: Change the tab size or cursor position. CPU ucode not at required rev level for port activity Facility: VAXport, VAXport Driver Explanation: The port driver will not attempt to start the port. User Action: On an 11/750, make sure that the console TU58 is present and up-to-date. Otherwise, call the Digital Services Group to check the port hardware.
CPUCEASED
CPU ceased execution Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
CPUEXIT
shutdown requested by another CPU Facility: SMP, Symmetric Multiprocessing Explanation: The current processor was requested to perform a bugcheck by another processor in the multiprocessor system. User Action: This bugcheck occurs as a direct result of a request by another processor only. Analyze the crash dump to determine which CPU is the 'crash CPU' and the reason why that CPU crashed.
CPUNOTACT
requested CPU not active Facility: SYSTEM, VMS System Services Explanation: The current process requires system functionality that is not available or no longer available among the active processors in the system. If this message is associated with a vector disabled (VECDIS) status code, a vector-present processor within the system has failed or has been removed from the system. User Action: Notify your system manager.
CPUNOTVLD
CPU not booted or CPU ID out of range Facility: SDA, System Dump Analyzer Explanation: You specified an invalid CPU ID for the SDA command SET CPU or SHOW CPU. The CPU ID is invalid either because there is no CPU in the system with the specified CPU ID, or because the CPU with the specified CPU ID was never booted and was not active at the time of the system failure. User Action: Reenter the command with a valid CPU ID.
CPUSANITY
CPU sanity timer expired Facility: SMP, Symmetric Multiprocessing Explanation: One of the processors in a multiprocessor configuration detected that another processor that is participating in the SMP environment is no longer responding to hardware clock interrupts. User Action: After the system reboots, determine which processor stopped responding to hardware clock interrupts by analyzing the crash dump generated by this bugcheck. Further analysis of the crash dump might show the reason why that CPU was not responding to clock interrupts, for example, it was looping in a driver at an IPL high enough to block its clock interrupts. Correct the code that stayed at high IPL for too long.
CPUSPINWAIT
CPU spinwait timer expired Facility: SMP, Symmetric Multiprocessing Explanation: One of the processors in a multiprocessor configuration held onto a spin lock longer than the permissible period of time. This is detected by another processor, which is trying to acquire that spin lock during that time. User Action: Analysis of the crash dump will show the spin lock that was held too long and should show the reason that the owning CPU did not release the spin lock when it should. For example, if the owning CPU had acquired the spin lock multiple times and subsequently released the spin lock using the conditional release option of the spin lock unlock macro when it should have executed a 'total' release of that spin lock, then the owning CPU will proceed with execution while it is unaware that it still owns the spin lock. Meanwhile, another CPU that attempts to acquire that spin lock will eventually time out and generate this bugcheck.
CPUSTARTD
CPU 'number' started Facility: SYSTEM, VMS System Services Explanation: The START/CPU command was used to start CPU 'number'. This informational message indicates that the boot sequence for the selected CPU has been started. The CPU may not actually start, if for example, CPU self test fails. User Action: None.
CPUSTARTIP
CPU 'number' startup in progress, cannot stop Facility: SYSTEM, VMS System Services Explanation: The STOP/CPU command was used to stop CPU 'number' but the selected CPU is currently starting and cannot be stopped until the startup is complete. User Action: Wait until the CPU has started and then re-issue the STOP/CPU command.
CPUSTOPPING
CPU 'number' stopping Facility: SYSTEM, VMS System Services Explanation: The STOP/CPU command was used to stop CPU 'number'. This informational message indicates that the selected CPU is in the process of stopping. In some situations, the CPU will not actually stop. Because some multiprocessor systems support primary CPU switching, a STOP/CPU command can stop the current primary, and cause a new primary CPU to be selected. However, if the selected CPU cannot become primary, (the console may have disabled it from becoming primary), the primary switch will not occur, and the primary CPU will not be stopped. User Action: None.
CRC
network DAP level CRC check failed Facility: RMS, VMS Record Management Services Explanation: CRC checksums computed by VMS RMS and the File Access Listener (FAL) at the remote node did not match when compared during a VMS RMS close operation. The file that is created or modified may be corrupted. User Action: Repeat the file access. If the CRC error on close persists, the communication hardware is malfunctioning.
CRCLS
the 'class-name' class cannot be removed from this report Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The class name entered does not apply to the currently selected report and therefore cannot be removed from the Report (SPR). The name is, however, valid in a different Report (SPR). User Action: Select a different report or enter the HELP CLASSES command to get a list of available classes.
CRE
ACP file create failed Facility: RMS, VMS Record Management Services Explanation: A file could not be created. This message is associated with a system status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a code that provides more information about the condition. Take corrective action based on this status code.
CREA_ERR
error creating work file 'filespec' Facility: CONVERT, Convert Utility Explanation: This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error described in the RMS error message and try again.
CREATDIR
creating temporary directory "dir-name". Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL creates a temporary directory if you specify the Get Save Set option. This is an informational message. User Action: None.
CREATE
error creating 'filename' Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility Explanation: This message will be accompanied by a VMS RMS error message that explains the error. User Action: Correct the error described in the VMS RMS error message and try again to create an output file.
CREATED
'filespec' created Facility: Shared by several facilities Explanation: This informational message is displayed when command activity results in a new file or directory. User Action: None.
CREATED
file is created, not opened Facility: Shared by several facilities Explanation: A system service, VMS RMS, or file system ACP request to create a file or directory (if it does not currently exist) completed successfully with a new file or directory. User Action: None. The applications program should detect and respond, if necessary, to this condition.
CREATED
file/section/resource did not exist - is created Facility: SYSTEM, VMS System Services Explanation: This file, section, or resource did not already exist and has just been created. If global sections are specified, this status is returned to processes that actually create a section through use of the $CRMPSC system service. (Omission of SEC$M_GBL results in the creation of local sections, rather than the creation of global sections and the return of this status.) This message indicates success. User Action: None.
CREATED
requested item is created Facility: PPL, Parallel Processing Facility Explanation: The requested item is created. An alternate success status indicates that the item is not found. User Action: Continue normally.
CREATED_SOME
created some of those requested - partial success Facility: PPL, Parallel Processing Facility Explanation: Some, but not all, of the requested items were created. User Action: If processing can continue with fewer items than those requested, then continue normally.
CREATEDSTM
'filename' has been created in stream format Facility: Shared by several facilities Explanation: RMS created the file in stream format with embedded carriage control because format and carriage control were specified in the RMS $CREATE call and are not supported by the remote node. This is an informational message. User Action: None.
CREATEFAIL
unable to activate subprocess Facility: VAXTPU, VAX Text Processing Utility Explanation: The use of the built-in procedure CREATE_PROCESS has failed to successfully start a subprocess. User Action: Re-create the subprocess, and if unsuccessful, check your ASTLM, PRCLM, or BYTLM quotas.
CREATELOST
error creating directory [SYSLOST] Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to create the directory [SYSLOST] to enter lost files. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
CREATEVIRT
error creating the virtual volume 'volume' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received an error from RMS while trying to create a Files-11 file to be used as a virtual volume. User Action: This message will be followed by one or two error messages reporting the actual condition discovered by RMS. Take corrective action suggested by the RMS error messages, then retry the command.
CREDIR
created directory 'directory-name' Facility: BACKUP, Backup Utility Explanation: BACKUP successfully created the directory 'directory'. This message is displayed only if the /LOG qualifier is specified. User Action: None.
CREDIRERR
error creating directory 'directory-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to create the specified directory. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
CREERR
unable to create SYSUAF.DAT Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
CREJOB
error creating job Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command Explanation: The system encountered an error creating a batch or print job. The accompanying message provides additional information. User Action: Correct the error and reenter the command.
CREJOB
error opening job 'job-name' for user 'user-name' in queue 'queue- name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to create a job. This job and the information about its files are not restored during the upgrade. User Action: The accompanying message gives information about why the operation failed. Attempt to correct the problem and retry the upgrade, or, after the upgrade, print or submit the job as originally desired using the DCL command PRINT or SUBMIT.
CRENEWFOLD
folder 'folder-name' does not exist. Do you want to create it (Y/N, default is N)? Facility: MAIL, Mail Utility Explanation: You have requested MAIL to place a message into a nonexistent folder. User Action: Confirm the request by entering Y, or abort with a carriage return.
CREPARFIL
unable to create parameter file Facility: SYSGEN, System Generation Utility Explanation: An error occurred during a WRITE operation. User Action: Reenter the command so that you can write to the file.
CREPRC
process creation failed Facility: RUN, Run Detached Utility Explanation: The creation of the subprocess or detached process failed. For an explanation of possible reasons for failure, see the error codes returned by the CREPRC system service. User Action: Correct the problem described by the CREPRC error message, and reenter command.
CREPRCFAL
error creating process for batch job Facility: JBC, Job Controller Explanation: The job controller was unable to create a process for the execution of a batch job. Usually, this indicates a lack of system resources, such as process slots, needed to complete the $CREPRC system service request. User Action: Resubmit the batch job. If the condition persists, contact your system manager.
CREPRCSTOP
failed to create a batch process; queue 'queue-name' will be stopped Facility: QMAN, Queue Manager Explanation: The queue manager could not create a process to execute a batch job. To avoid errors when trying to execute other batch jobs in the queue, the specified queue will be stopped upon completion of any jobs currently executing in that queue. An accompanying message provides additional information. User Action: Take action based on the accompanying message. Possibly there are too few process slots on the node. Correct the problem and try to restart the queue.
CREPRIJOB
error creating print job on queue 'queue-name' Facility: MAIL, Mail Utility Explanation: An error occurred when you attempted to create a print job to queue a message for printing. This message is usually accompanied by a system error message indicating the reason for the failure. User Action: Resolve the problem and reenter the command.
CREQUE
error creating queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to create a queue. This queue, its jobs, and information about its files are not restored during the upgrade. User Action: The accompanying message gives information about why the operation failed. Attempt to correct the problem and retry the upgrade, or after the upgrade has completed, enter the DCL command INITIALIZE/QUEUE as originally desired. If the queue contained jobs waiting for execution, the CREJOB message should also appear during the upgrade.
CRE_STM
file is created in stream format Facility: RMS, VMS Record Management Services Explanation: VMS RMS created the file in stream format with embedded carriage control instead of using the record format (RFM field) and carriage control (RAT field) type specified in the VMS RMS $CREATE call. This file format conversion is performed because the remote DECnet system only supports stream format files. This message indicates success. User Action: None.
CRF
can't read back saved footnotes Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR has successfully written footnote information to the work file but cannot read it back. One or more 001RNO.TMP files may already exist. User Action: Delete any 001RNO.TMP files, and reprocess the file. If the problem continues, notify the system manager.
CRFERR
error encountered in Cross Reference Facility: LINK, Linker Utility Explanation: An error is returned by the Cross-Reference Facility. User Action: The additional message from the Cross-Reference Facility should explain the problem.
CRMP
CRMPSC system service failed to map global buffers Facility: RMS, VMS Record Management Services Explanation: This message is associated with a system status code returned from the $CRMPSC (Create and Map Section) system service called from VMS RMS to map global buffers. User Action: The status value (STV) field of the RAB contains a code that provides more information about the condition. Take corrective action based on this status code.
CRMPSC
error code of 'xx' mapping section Facility: PATCH, Patch Utility Explanation: The system service $CRMPSC request failed due to the error represented as xx. User Action: Correct the error (represented as xx) and retry.
CRP
can't recognize page on /PAGES qualifier Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A page range specification is illegally formatted. User Action: Correct the page range specification. CTRL/C ignored Facility: EDT, EDT Editor Explanation: You attempted to use Ctrl/C to interrupt an EDT operation that EDT does not allow you to abort. User Action: None. You cannot abort the operation.
CTRLCEXIT
exit now to avoid journal file inconsistency Facility: VAXTPU, VAX Text Processing Utility Explanation: Use of Ctrl/C often causes a journal file inconsistency during recovery. User Action: Exit immediately after pressing Ctrl/C to save your edits. You can then reenter the editing session.
CTRLCHAR
the following line contains control characters - ignored Facility: DSR, DIGITAL Standard Runoff Explanation: DSR encountered control characters in a line of the input file. The control characters were ignored, however. User Action: None.
CTRLCJOU
CTRL/C may have invalidated the journal file Facility: VAXTPU, VAX Text Processing Utility Explanation: A Ctrl/C character has been detected in the journal file. This may mean that the rest of the session is invalid. User Action: If you used Ctrl/C during an editing session, exit immediately and restart VAXTPU.
CTRLERR
disk boot driver virtual circuit failure Facility: VAXCLUSTER, VAXcluster Facility Explanation: The satellite could not establish a virtual circuit to the MSCP server on the boot node or received a hardware error during communications. User Action: Check that the MSCP server is loaded on the boot node, verify the CLUSTER_AUTHORIZE.DAT file, and look for hardware errors on the boot node's system disk and PE/Ethernet port.
CTRLERR
fatal controller error
Facility: SYSTEM, VMS System Services
Explanation: The exact meaning depends on the device. This message
may indicate a hardware error. If this message is associated with
a status code returned by a request to a disk driver or magtape,
it indicates a controller-related error. For example, one or more
of the following conditions can cause this error:
o Late data
o Error confirmation
o Invalid map register
o Interface timeout
o Missed transfer
o Programming error
o Read timeout
o RX01 switch set incorrectly (RX02 only) (disk driver specific)
If this message is associated with a status code returned by a
request to a DR11-W interface, a fatal error that affects all
DR11-W activity is set in the DR11-W CSR on completion of the
QIO request. Look at the third and fourth words of the IOSB (CSR
and EIR) for the specific cause of the error. If the condition
indicated in the CSR can be cleared, that is, if the ATTN bit
can be cleared, SS$_DRVERR is returned. If the condition cannot
be cleared, SS$_CTRLERR is returned. In both cases, the driver
performs a device reset to the DR11-W.
If this message is associated with a status code returned by a
request to a DR32 interface, a fatal hardware malfunction occurred
that stops all DR32 activity. (Only for start data transfer
functions.) The second longword of the IOSB contains additional
information pertaining to this error; the following bit values are
associated with SS$_CTRLERR:
XF$V_IOS_INVPTE
XF$V_IOS_SBIERR
XF$V_IOS_RDSERR
If this message is associated with a status code returned by a
request to a DMC/DMR device, it can occur for one of the following
reasons:
o NAK threshold errors exceeded
o Time out on response from remote end
o Buffer not available
o Maintenance message received in RUN mode
o Message too long to fit in receiver buffer
o Modem has disconnected
o Start message is received in run mode
o Nonexistent memory error
o Halt to DMC/DMR is complete
If this message is displayed, restart the DMC/DMR device.
If this message is associated with a status code returned by
a LPA11-K driver, it is a fatal error that affects all LPA11-K
activity. The LPA11-K terminates all active requests. The third
and fourth words of the IOSB contain the LPA11-K Ready-Out Status
Register and Maintenance Register contents. In particular, the
high byte of the third word contains the specific LPA11-K error
code.
If this message is associated with DEUNA hardware, on a STARTUP
request the startup failed because of bad error return from the
DEUNA hardware. On a read request, the hardware returned a zero-
length message.
User Action: Action depends on the type of device to which the
I/O request is directed. If the failure is on STARTUP, the DEUNA
should be checked by running UETP or the Digital Services Group
should run the DEUNA diagnostics. If the failure is on a read
request and the protocol has enabled PADDING, then the remote
software module should be corrected to stop sending zero-length
messages.
If the failure persists, notify the system manager.
CTRLY
installation cancelled via CTRL/Y. Facility: VMSINSTAL, Install Procedures Explanation: You canceled the installation by entering Ctrl/Y. This message is informational. User Action: None.
CTXSTSERR
Error obtaining vector context test subprocess status Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error following vector context testing. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
CUR
no current record (operation not preceded by $GET/$FIND) Facility: RMS, VMS Record Management Services Explanation: A program attempted a VMS RMS $DELETE, $TRUNCATE, or $UPDATE operation without having performed a successful $GET or $FIND operation. User Action: Check for a programming error. Modify the source program, if necessary, to detect and respond to the condition.
CUREXEC
current executor node name 'node-name' Facility: NCP, Network Control Program Explanation: This informational message is output after an NCP SET EXECUTOR NODE command is entered, and the command failed, or if an established link to another executor failed. It indicates the name of the node that NML is treating as the executor. User Action: None.
CVTERR
could not convert entity 'time or number' using 'time or number' Facility: RUN, Run Detached Utility Explanation: Time specified with the /DELAY, /INTERVAL, or /SCHEDULE qualifiers is not in the proper format, or the value entered could not be converted to a numeric value. User Action: Reenter qualifier value (time or number) in the proper form.
CVTERR
error converting to decimal value, 'value' Facility: ERF, Error Log Utility Explanation: An attempt is made to convert a value to decimal resulting in an error. User Action: Submit a Software Performance Report (SPR).
CVTUNGRANT
cannot convert an ungranted lock Facility: SYSTEM, VMS System Services Explanation: An attempt is made to convert a lock that is not granted. (Only locks that are granted may be converted to another lock mode.) User Action: See the section on the lock management services in the VMS System Services Reference Manual and correct your program.
CWF
can't write footnote file (N) Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR can open the footnote work file but cannot write into it; N is a system error code. User Action: Reprocess the file. If the problem continues, notify the system manager.
DAC
ACP file deaccess failed during $CLOSE Facility: RMS, VMS Record Management Services Explanation: An error occurred when a file is closed. The file is deaccessed. This message is associated with a status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a code that provides more information about the condition. Take corrective action based on this status code.
DAN
invalid data area number for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The data area number specified in a key definition XAB is not a defined area for the file. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
DATACHECK
write check error Facility: SYSTEM, VMS System Services Explanation: The data in memory did not match the data on disk during a data check operation. If this message is associated with a status code returned by a LPA11-K driver, a mismatch between the microcode in memory and the microcode loaded into the LPA11-K is detected. The second word of the IOSB contains the number of bytes successfully loaded. Another possible explanation is that the Ethernet hardware detected a late collision on a write request. User Action: Note the condition. If necessary, modify the source program to detect and respond to the condition. This message may indicate a hardware error. Check the Ethernet cable and all Ethernet controllers for proper operation. If the error persists, notify the system manager.
DATADEVERR
data error on 'device-name' byte 'location' good data = 'xx' bad data = 'xx' Facility: UETP, User Environment Test Package Explanation: One of the UETP tests detected a difference between the data that is written from memory and the same data after it is read back into memory. The 'location' is the offset from the start of the buffer where the first difference is detected. User Action: Investigate the device or mechanism that caused the error.
DATAER
data error on 'device-type' unit 'number' byte 'location' good data = 'xx' bad data = 'xx' Facility: UETP, User Environment Test Package Explanation: One of the UETP tests detected a difference between the data that is written from memory and the same data after it is read back into memory. The 'location' is the offset from the start of the buffer where the first difference is seen. User Action: Investigate the device or mechanism that caused the error. Datagram Free Queue Insert Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Call the Digital Services Group. Datagram Free Queue Remove Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Call the Digital Services Group.
DATALOST
data lost Facility: SYSTEM, VMS System Services Explanation: Data was lost on a PTD$WRITE operation because the terminal driver's type-ahead buffer is full. User Action: Wait until the driver is ready for input and try entering the data again. For information on how to program the pseudoterminal, refer to the VMS I/O User's Reference Manual: Part I.
DATALSTSYN
data list syntax error Facility: MACRO, VAX MACRO Assembler Explanation: The data list in the directive contained a syntax error. For example, the directive .LONG 3,,5 contains a data list syntax error because there is no data item between the two commas. User Action: Correct the syntax of the data list.
DATAOVERUN
data overun
Facility: SYSTEM, VMS System Services
Explanation: This message can occur under the following
conditions:
o More data has been read into the user buffer than the user
buffer can hold.
o More data has been written into the user buffer than the user
buffer can hold.
o Card reader data has been written into the controller data
buffer before the driver has been able to receive previously
sent data.
o Continued attempts to use PTD$WRITE have resulted in data loss
because the terminal driver's type-ahead buffer is full.
If this message is associated with a status code returned by a
request to a magnetic tape driver, the data block read is longer
than the assigned buffer. On a read reverse operation, the first
data read and stored in the buffer is the data that was nearest
the end-of-tape marker when the operation began.
User Action: There are several possible user actions:
o If there is too much data for the existing buffer, specify a
larger buffer.
o If the problem occurred on a card reader operation, resubmit
the cards to the reader.
o Turn on the alternate type-ahead buffer by using the DCL
command SET TERMINAL/ALTYPEAHD. Then increase the type-ahead
buffer size or the alternate type-ahead buffer size, or both,
by modifying the TTY SYSGEN parameters.
o Wait until the driver is ready to receive input before you
resume writing data. For information on how to handle flow
control and the pseudoterminal, refer to the VMS I/O User's
Reference Manual: Part I.
DATAOVFL
data area overflow in section - please submit SPR Facility: MESSAGE, Message Utility Explanation: An internal error in the compiler has been detected. User Action: Submit a Software Performance Report (SPR).
DATATRUNC
data truncation error Facility: MACRO, VAX MACRO Assembler Explanation: The specified value did not fit in the given data type. The assembler truncated the value to make it fit. User Action: Reduce the value or the number of characters in an ASCII string or change the data type.
DATFILCRE
component database created Facility: SYSMAN, Cluster System Management Utility Explanation: The specified STARTUP component database is created. User Action: None.
DATMISMCH
creation date of 'date' in shareable image 'image-name' differs from date of 'date' in shareable image library 'library-name' Facility: LINK, Linker Utility Explanation: A shareable image extracted from a shareable image library has a different creation date from the date recorded for that shareable image in the library. User Action: Insert the new shareable image into the shareable image library using the DCL command LIBRARY.
DATTOOLNG
length of new data may not exceed length of old data Facility: PATCH, Patch Utility Explanation: This error is returned when patching in absolute mode (PATCH/ABSOLUTE), and the length of the data being inserted is longer than that of the data to be replaced in the file. User Action: Make sure that the data to be inserted is equal to or shorter in length than the data in the file.
DBCORRUPT
component database is corrupt Facility: SMI, System Management Integrator/Server Explanation: The startup component database is corrupt. User Action: Verify that the file being used is a component database and that the file has not been edited or otherwise modified. If the problem still exists, submit a Software Performance Report and include the component database.
DBGTFR
image 'image-name' has no Debugger transfer address Facility: LINK, Linker Utility Explanation: A debugger is requested with the /DEBUG qualifier, but the linker could not locate a transfer address within the debugger module. User Action: If you specified the optional filename parameter with the /DEBUG[=filename] qualifier, ensure that the specified debugger module contains a transfer address. If you specified /DEBUG, without the filename parameter, submit a Software Performance Report (SPR).
DBLERR
double error halt restart Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable hardware error. Because of the severity of the error, further operation is impossible; or if it is possible, it may corrupt user data. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Thoroughly test all system hardware components. If no hardware errors are located and if the problem persists, submit a Software Performance Report (SPR). The SPR should describe the conditions at the time of the error, and should include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command to produce the save set.)
DCVNOTFND
domain converter not found Facility: CDA, Compound Document Architecture Explanation: The required domain converter could not be found. User Action: Only tabular to document domain conversions (for example, DTIF to DDIF) are currently supported. Check the formats specified for input and output files to ensure that a document to tabular conversion is not being attempted.
DDIFIN
'count' line(s), 'count' frame(s) read from file 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU opened the named DDIF file and read the indicated number of lines and frames from that file into a buffer. User Action: None.
DDIFOUT
'count' line(s), 'count' frame(s) written to file 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU wrote the indicated number of lines and frames from a buffer into the named DDIF file. User Action: None.
DEADLOCK
deadlock detected Facility: SYSTEM, VMS System Services, RMS, VMS Record Management Services Explanation: The system detected a set of processes waiting for locks in a circular fashion (deadlock). This lock request is denied in order to break the deadlock. User Action: Recovery from a deadlock is application-specific. One common action is for the program to release all of its locks (performing any necessary cleanup) and then to retry the operation. See the section on the lock management services in the VMS System Services Reference Manual and rerun the program.
DEBUG
breakpoint at line 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: A BREAK statement has been executed. User Action: None.
DEBUG
command interpreter debugger signal at PC 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: The DCL command DEBUG is issued after CTRL/Y interrupted an image that is not linked with the debugger. User Action: Link the image with the /DEBUG qualifier to enable use of the debugger.
DECNET
your DECnet network is up and running. Facility: VMSINSTAL, Install Procedures Explanation: When VMSINSTAL begins an installation, it makes sure that your DECnet network has been shut down. This check failed. VMSINSTAL asks if you want to continue the installation. User Action: Digital recommends that you correct this situation before continuing.
DECOVF
arithmetic trap, decimal overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: A decimal overflow caused an arithmetic overflow condition. User Action: Examine the PC location displayed in the message and check the program listing to verify that operands or variables are specified correctly.
DECOVF
decimal overflow Facility: LIB, Library Facility Explanation: During an arithmetic operation, a decimal value exceeds the largest representable decimal number. The result of the operation is set to the correctly signed least significant digit. User Action: None.
DECPTREF
decrement page table reference count error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DECTSTFAI
a local self-test has failed Facility: DTK, DECtalk Facility Explanation: A local self-test malfunction occurred since the DECtalk device was turned on. User Action: Check the DECtalk hardware.
DEFAULTED
entity defaulted present in command string Facility: CLI, Command Language Interpreter (DCL) Explanation: This status is returned by the CLI$PRESENT CLI interface routine to indicate that the specified entity is not explicitly present in the command line, but is present by default. User Action: None.
DEFAULTLEN
a default is limited to 'max-length' characters in length, including commas Facility: CDU, Command Definition Utility Explanation: CDU encountered a DEFAULT assignment in the CLD file that exceeded the maximum allowable length for a DEFAULT assignment. Currently, the maximum length for a DEFAULT assignment is 94 characters. User Action: Edit the CLD file so that no DEFAULT assignments are greater than 94 characters in length.
DEFCHARSTIC
error defining characteristic: name 'characteristic-name', number 'characteristic-number' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to define characteristics. The definition for this characteristic is not restored during the upgrade. User Action: The accompanying message gives information about why the operation failed. Attempt to correct the problem and retry the upgrade, or after the upgrade, enter the DCL command DEFINE /CHARACTERISTIC as originally desired.
DEFER_Q_FULL
no space is currently available to process an AST request Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A call to a DECthreads service from an AST routine cannot be served immediately because there are too many outstanding requests. User Action: AST routines using DECthreads are occurring too quickly. Reduce the number of requests or slow the rate of their arrival. If you continue to have problems, submit a Software Performance Report (SPR) including a small test program that reproduces the problem.
DEFERR
unable to obtain DEFAULT record Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
DEFFORM
error defining form: name 'form-name', number 'form-number' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to define a form. The definition for this form was not restored during the upgrade. User Action: The accompanying message gives information about why the operation failed. Attempt to correct the problem and retry the upgrade, or after the upgrade, enter the DCL command DEFINE/FORM as originally desired.
DEFFORUSE
default format used, could not determine user's preference Facility: LIB, Library Facility Explanation: Translation of LIB$DT_FORMAT failed and the VMS standard representation is used. User Action: Examine and make corrections to the logical LIB$DT_ FORMAT.
DEFINEKEY
defined key 'key-name' Facility: LAT, LAT Facility Explanation: The specified key has been defined by LATCP. User Action: None.
DEFKEY
'state' key 'key-name' has been defined Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified key is defined. User Action: None.
DEFOVF
too many command procedure parameters - limit to eight Facility: CLI, Command Language Interpreter (DCL) Explanation: A command procedure is invoked with more than eight parameters. User Action: Reenter the command; do not specify more than eight parameters.
DEFPWD
Warning: copied or renamed records must receive new password Facility: AUTHORIZE, Authorize Utility Explanation: You did not explicitly specify a password for the new record. User Action: You must specify a password for the new record.
DEL
RFA-accessed record is deleted Facility: RMS, VMS Record Management Services Explanation: A record accessed by the record's file address (RFA) is deleted previously. User Action: Modify the program, if necessary, to detect and respond to the condition.
DELACCESS
file protection does not allow delete access Facility: JBC, Job Controller Explanation: The file protection of the specified file, which is entered with the delete option, does not allow delete access to the requestor. User Action: None.
DELCONPFN
fatal error in delete contents of PFN Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DELDATERR
error deleting data from 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. An error occurred during an attempt to delete the text; or a VMS RMS error occurred; or there is not enough virtual memory available. User Action: Compress the old library before deleting the specified text.
DELETE
error deleting 'filename' file ID ('numeric-string')
Facility: BACKUP, Backup Utility
Explanation: An error is encountered during an attempt to delete
the file with the specified file identification in response to the
/DELETE qualifier. The accompanying message provides additional
information.
User Action: None.
DELETE
file ('file-id') 'filename' error deleting file
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to delete
the specified file. An accompanying message provides additional
information.
User Action: Correct the condition that caused the error and
reenter the command.
DELETED
'filename' deleted Facility: Shared by several facilities Explanation: This informational message displays the file specification of a file that is deleted successfully. User Action: None.
DELETED
module 'module name' deleted from 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: This success message is generated by the DCL command LIBRARY. User Action: None.
DELETED
previous Known File Entry has been deleted Facility: INSTALL, Install Utility Explanation: This message is displayed as the result of issuing a REPLACE command in INSTALL. If the REPLACE command failed to create a new Known File Entry for any reason, this message is displayed to explicitly declare that the previous Known File Entry has been successfully removed. This message is a warning explaining why even the old entry no longer exists in case REPLACE failed to create a new entry. User Action: None.
DELETEFAIL
unable to terminate subprocess Facility: VAXTPU, VAX Text Processing Utility Explanation: The use of the built-in procedure DELETE to delete a subprocess failed to terminate the subprocess. User Action: None.
DELETESWL
'device-name' is write protected - file deletion pass not executed Facility: BACKUP, Backup Utility Explanation: The input device is software write locked. The BACKUP Utility cannot perform the file deletion pass. User Action: Dismount the input device, remount it writeable, and either delete the files by hand or reenter the BACKUP command.
DELEXIGBL
termtable section already exists Facility: SMG, Screen Management Facility Explanation: The system program which maps termtable as a global section is unsuccessful. Before a new global section can be created, the previous global section must be deleted. User Action: The system must be rebooted in order to map a new TERMTABLE.EXE as the new global section.
DELGBLSEC
delete global section error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DELGBLWCB
delete global section window error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DELHEADER
file ('file-id') 'filename' marked for delete
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file is marked for deletion, but has
not been deleted.
User Action: None. The utility deletes the file.
DELHEADER_BUSY
deleted file header marked "busy" in index file bitmap Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message is issued along with the BADHEADER message and gives a more detailed reason why the specified file header is corrupt. In this case, the file header and the index file bitmap are inconsistent; the file header indicates that the file is deleted, but the index file bitmap indicates that the file header is busy, for example, the file is not deleted. User Action: None. See the BADHEADER message.
DELKEY
'state' key 'key name' has been deleted Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified key is deleted. User Action: None.
DELKEYERR
error deleting 'module-name' from 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The module you want to delete does not appear in the module name table (MNT); a VMS RMS error occurred; or there is not enough virtual memory available. User Action: List the library to find out whether the module is present. If so, correct the problem before reentering the command line.
DELLINK
deleted link 'link-name' Facility: LAT, LAT Facility Explanation: The specified link has been deleted by LATCP. User Action: None.
DELPORT
deleted port 'port-name' Facility: LAT, LAT Facility Explanation: The specified port has been deleted by LATCP. User Action: None.
DELSERVICE
deleted service 'service-name' Facility: LAT, LAT Facility Explanation: The specified service has been deleted by LATCP. User Action: None.
DELSYM
'symbol table' symbol 'symbol name' has been deleted Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message verifies that the symbol deletion requested from the DELETE/SYMBOL command has occurred. User Action: None.
DELTIMREQ
delta time required, absolute time supplied Facility: LIB, Library Facility Explanation: An absolute time is passed to the routine when a delta time is required. User Action: Examine each argument and change the delta time to absolute time.
DELTVA
error code of 'xx' deleting 'xxx' to 'xxx' Facility: PATCH, Patch Utility Explanation: The system service request $DELTVA failed due to the error code represented as xx. User Action: Correct the error (represented as xx) and retry.
DELVER
explicit version number or wild card required Facility: Shared by several facilities Explanation: The DCL command DELETE requires a version number in each file specified. User Action: Reenter the command. Specify either the explicit version number for the file you want to delete or use a wildcard in the version field.
DELWSLEX
delete working set list entry index error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DENOSU
'testname' device 'device-type' is not supported Facility: UETP, User Environment Test Package Explanation: The device name in this message is unknown to the UETP and cannot be tested by UETP, for example, a user-written driver might not be known to the UETP. User Action: The UETP either supports or knows to ignore all devices supported by VMS. If another device, which is not a supported layered product, produces this message, submit a Software Performance Report (SPR).
DENSITY
'saveset-spec' does not support specified density - default used Facility: BACKUP, Backup Utility Explanation: The specified tape hardware does not support the density selected by the /DENSITY qualifier. The Backup Utility uses the default density. User Action: Use a different tape device, or specify a different density.
DEQSUBLCKS
tried to dequeue lock with sublocks Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DESSTROVF
destination string overflow Facility: LIB, Library Facility Explanation: The destination string is overflowed, and the operation did not justify return of a warning, but a fatal error. User Action: Increase the length of the destination string, or use dynamic string for destination. Destination for MOVE or COPY not found Facility: EDT, EDT Editor Explanation: The range specification in the command does not exist. User Action: Reenter the command specifying an existing range.
DESTP
'testname' stopped testing 'controller' unit 'number' at 'time' Facility: UETP, User Environment Test Package Explanation: A device that passed the simple read/write test in the initial phase of the UETP could not complete its test in the device test phase. User Action: If you think that the device should be tested by UETP, investigate and correct the problem; otherwise, ignore the message.
DEUNUS
'testname' device 'device-name' is unusable, error code = 'xxxxxxxx' Facility: UETP, User Environment Test Package Explanation: The specified device failed to pass the simple read /write test in the initial phase of UETP. Subsequent tests with UETP will not attempt to test the device. Another message usually follows to explain why the device failed the test. Possible causes are that the device is down, offline, not mounted, not initialized, or not write-enabled. User Action: Either make the device usable or ignore the message. Consult the Software Installation Support manual.
DEV
error in device name or inappropriate device type for operation Facility: RMS, VMS Record Management Services Explanation: A device name is not specified correctly; the device specified is not supported by this system, or the type of device specified cannot perform the requested operation (for example, an attempt is made to create a random access file on a sequential device). User Action: If the error occurred while a command is being entered, verify the syntax and spelling of the device specification or the logical name, if a logical name is specified. If the error occurred while an image is being executed, check that the file specification is coded correctly and that the logical name, if any, is assigned before the image is executed. If the device name is correctly specified and if the device is valid for the requested type of operation, verify that the device is available on your system. Otherwise, modify the program.
DEVACTIVE
device is active Facility: SYSTEM, VMS System Services Explanation: If this message is associated with a status code returned by a request to a DR32 interface, the microcode cannot be loaded because there is an active data transfer request (only for the load microcode function). If this message is associated with a status code returned by a request to an LPA11-K driver, the microcode cannot be loaded or the microprocessor cannot be started because there is an active data transfer request. If this message is associated with a status code returned by a request to a DR11-W interface, the DR11-W controller is occupied with a request from another process. The operating system does not normally display this message. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
DEVALLOC
device already allocated to another user Facility: SYSTEM, VMS System Services Explanation: An attempt to allocate a device failed because the device is allocated by another user or channels are assigned to it. Only one user at a time can access an allocated device. Or, on a startup request, the user attempted to start the protocol as a shared default user, when a shared default user already exists for that protocol type. User Action: Wait until the current owner has deallocated the device, or reenter the request specifying a different device of the same type, or specify a generic device name in the allocate request. The user must not attempt to bring up two SHARED DEFAULT users until the first user is stopped.
DEVALLOC
device 'device-name' already allocated to another user. Facility: VMSINSTAL, Install Procedures Explanation: In response to the prompt Where will the distribution volumes be mounted? you specified a device that is allocated to another user. You will be asked to specify another device. User Action: Specify a device name that is not allocated to another user.
DEVALRALLOC
device already allocated to this job Facility: SYSTEM, VMS System Services Explanation: This is a success status message from the Allocate Device system service. The process has already allocated the device. User Action: Depending on the program logic, this may not be an error; no action is necessary.
DEVALSPL
device already spooled Facility: CLI, Command Language Interpreter (DCL) Explanation: A request to set a device spooled is made for a device that is already set spooled. User Action: None.
DEVASSIGN
device has channels assigned Facility: SYSTEM, VMS System Services Explanation: A request to deallocate a device failed because the device has I/O channels assigned to it; that is, it is currently being read or written. User Action: Verify the device name (or logical name, if a logical name is specified) and reenter the command with the correct device name. If any executing subprocesses are using the device, wait until they have terminated before attempting to deallocate the device.
DEVCLASS
device class of SYS$INPUT must be terminal
Facility: FDL, Edit/FDL Utility
Explanation: EDIT/FDL cannot interact with a file, only with a
terminal.
User Action: Do not invoke EDIT/FDL from a batch job. Also, if
invoking EDIT/FDL from an interactive command file, first include
the following line immediately before the $EDIT/FDL command in the
command file:
$ ASSIGN/USER 'F$LOGICAL("SYS$OUTPUT")' SYS$INPUT
DEVCMDERR
device command error Facility: SYSTEM, VMS System Services Explanation: The exact meaning depends on the device. If this message is associated with a status code returned by a request to an LPA11-K driver (only for the initialize LPA11-K, set clock, and start data transfer request functions), it is associated with the issuance of a new LPA11-K command. The third and fourth words of the IOSB contain the LPA11-K Ready-Out Status Register and Maintenance Register contents. In particular, the high byte of the third word contains the specific LPA11-K error code. User Action: Action depends on the type of device to which the I/O request is directed.
DEVCOUNT
number of devices must match number of volumes Facility: MOUNT, Mount Utility Explanation: The number of devices specified in the DCL command MOUNT to mount a disk volume set did not match the number of volume labels specified in the command. User Action: Check the command line. Verify the names of the devices and volume labels for the command and then reenter the command with a matching number of devices and volume labels.
DEVFOREIGN
device is mounted foreign Facility: SYSTEM, VMS System Services Explanation: A Files-11 operation is attempted on a device which is mounted foreign. User Action: Remount the device as Files-11. If the medium is DOS or RT11 format, use FLX; otherwise, write a program.
DEVICE
devices Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "DEVICE" class operations. User Action: None.
DEVICEFULL
device full - allocation failure Facility: SYSTEM, VMS System Services Explanation: It indicates that space cannot be allocated for a file because the device is full; or a request for contiguous space cannot be satisfied because the specified number of contiguous blocks is not available. User Action: Verify the status of the device. If it is a private device, purge unwanted files with the DCL command PURGE. Otherwise, obtain another volume to create files. If the device is a system device, notify the system operator or manager that the volume is full.
DEVICES
only one device allowed Facility: MOUNT, Mount Utility Explanation: More than one device is specified in the DCL command MOUNT. Only one volume can be mounted at a time for this specified type of MOUNT. User Action: Reenter the DCL command MOUNT specifying only one device.
DEVINACT
device inactive Facility: SYSTEM, VMS System Services Explanation: The device unit involved in the current operation is inactive. This message indicates that you tried to perform an activity that cannot be properly performed until the device unit is active. For example, the XE device has not been started. User Action: Start the controller before doing any tributary requests. The user should make sure that the QIO STARTUP has finished successfully or that the XE device has not shut down the unit due to a hardware failure.
DEVMNT
device 'device-name' will be 'mount-status' Facility: VMSINSTAL, Install Procedures Explanation: The device that you specified for the output of the Get Save Set option is initialized (if it is a disk) and mounted. This informational message appears only if the output device you specified is not mounted when VMSINSTAL is started. User Action: None.
DEVMOUNT
device is already mounted Facility: SYSTEM, VMS System Services Explanation: The device specified has a volume mounted and cannot be allocated, or a volume is already mounted on a device for which a mount request is previously issued. User Action: Verify the device name (or logical name, if a logical name is specified) and reenter the command with the correct device name. If the device name is correct and if the volume that is mounted can be dismounted, dismount the volume and reenter the request.
DEVNOTALLOC
device not allocated Facility: SYSTEM, VMS System Services Explanation: The device specified in a deallocate request is not currently allocated. User Action: Verify the device name (or logical name, if a logical name is specified) and reenter the command with the correct device name.
DEVNOTBLK
'device' is not a block structured device Facility: BAD, Bad Block Locator Utility Explanation: This message indicates a fatal error. You attempted to perform an analysis of media that is not block structured. User Action: Do not use the ANALYZE/BAD command with this device.
DEVNOTERM
illegal source operator device Facility: OPCOM, Operator Communication Process Explanation: The DCL command REPLY requested a device that is not a terminal be enabled as an operator terminal; for example, the DCL command REPLY/ENABLE is issued in a batch job. User Action: Reenter the command from a terminal.
DEVNOTEXIST
device 'device-name' does not exist. Facility: VMSINSTAL, Install Procedures Explanation: The device you specified for the output of the Get save set option does not exist. User Action: Specify a valid device name.
DEVNOTFOR
'device-name' is not mounted foreign Facility: BAD, Bad Block Locator Utility Explanation: The device is not mounted foreign. User Action: Mount the device using the /FOREIGN qualifier and reinvoke the utility.
DEVNOTFOR
device not mounted foreign Facility: CLI, Command Language Interpreter (DCL) Explanation: An operation is requested for a device that must be mounted foreign to perform the operation. User Action: If the device is not mounted, then mount it foreign; if the device is mounted, dismount it and remount it foreign.
DEVNOTKNWN
device not known: 'input' Facility: SYSGEN, System Generation Utility Explanation: The specific device is unknown when you entered the SYSGEN command CONFIGURE. User Action: See VMS Device Support Manual for the correct UNIBUS controller name.
DEVNOTKNWN
unable to locate datalink driver Facility: VAXCLUSTER, VAXcluster Facility Explanation: You are attempting to boot a satellite using an unsupported Ethernet adapter. User Action: Check for an unsupported Ethernet adapter on the satellite.
DEVNOTKNWN
unable to locate disk boot driver Facility: VAXCLUSTER, VAXcluster Facility Explanation: This message indicates an internal error in the NISCS bootstrap. User Action: Submit a Software Performance Report or contact the Digital Services Group.
DEVNOTMBX
device is not a mailbox Facility: SYSTEM, VMS System Services Explanation: An I/O channel specified in a system service request is not currently assigned to a mailbox. The service requires that the device be a mailbox. User Action: Check for a programming error. Verify that the channel number specified for the service is valid.
DEVNOTMOUNT
device is not mounted Facility: SYSTEM, VMS System Services Explanation: This message is displayed when you issue the DCL command DISMOUNT for a device that is not mounted or when you attempt an operation that requires a mounted device. User Action: Reenter the command with the mounted device or mount the device in question.
DEVNOTSPL
device not spooled Facility: CLI, Command Language Interpreter (DCL) Explanation: A request to set a device not spooled is made for a device that is already set not spooled. User Action: None.
DEVNOTSUIT
the device 'device-name' is not suitable for operations Facility: EXCHANGE, Exchange Utility Explanation: An EXCHANGE command is directed at a device for which the requested operation could not be performed. User Action: Reenter the command, specifying a suitable device.
DEVOFFLINE
device is not in configuration or not available Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: For some device-specific reason, the associated driver is not available. If this message is associated with a status code returned by a request to a DMC11 interface, the device protocol is not started (read or write). The function is inconsistent with the current state of the unit (Set Mode). The device is not currently on line or the Ethernet protocol has not been specified. User Action: Reenable or repair the device and retry the operation. The XE device should be checked to make sure that it has been configured as ONLINE. The user should make sure that all parameters in the QIO STARTUP request are supplied, including NMASC_PCLI_PTY.
DEVOFFLINE
device is off line Facility: OPCOM, Operator Communication Process Explanation: This message is displayed on the operator's console when a device goes off line in the VMS system configuration. User Action: Take appropriate measures to bring the device on line.
DEVOFFLINX
'date and time', Device 'device-name' is off line Mount verification in progress Facility: OPCOM, Operator Communication Process Explanation: The device is off line and mount verification is in progress. All I/O requests are stalled. User Action: Cancel the mount verification or bring the volume back on line.
DEVONLINE
device on line Facility: OPCOM, Operator Communication Process Explanation: This informational message is displayed on the operator's console when a device becomes on line. User Action: None.
DEVONLY
using device name only, ignoring parts of 'filespec' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has ignored all parts of the file specification except the device name. This command completed successfully. In the future, use the device name only in this context. User Action: None.
DEVQUALS
invalid qualifier for device type Facility: DUMP, File Dump Utility Explanation: A qualifier is specified that is invalid if the input medium is not a disk or tape device or is mounted with the /FOREIGN qualifier. User Action: Reenter the command.
DEVRCT
unable to analyze 'device-name', due to revector caching Facility: BAD, Bad Block Locator Utility Explanation: The device controller is capable of revectoring bad blocks dynamically; hence, the device will always appear to be flawless. User Action: Do not analyze the media.
DEVREQERR
device request error
Facility: SYSTEM, VMS System Services
Explanation: The exact meaning depends on the device. If this
message is associated with a status code returned by a request to
a DR32 interface, a programming error or an error associated with
the far end DR-device is indicated. The second longword of the
I/O status block contains additional information pertaining to the
error; the following bit values are associated with SS$_DEVREQERR:
XF$V_IOS_DDIDIS
XF$V_IOS_RNGERR
XF$V_IOS_UNQERR
XF$V_IOS_INVPKT
XF$V_IOS_FREQMT
XF$V_IOS_INVDDI
XF$V_IOS_LENERR
XF$V_IOS_DDIERR
If this message is associated with a status code returned by a
request to an LPA11-K driver, it indicates an LPA11-K user request
error for a start data transfer request. The third and fourth
words of the IOSB contain the LPA11-K Ready-Out Status Register
and Maintenance Register contents. In particular, the high byte of
the third word contains the specific LPA11-K error code.
On a write request, the DEUNA failed to transmit the message after
16 attempts.
User Action: Action depends on the type of device to which the I/O
request is directed.
The Ethernet cable may have short-circuited, or it may have been
temporarily overloaded. In either case, the Ethernet cable should
be checked and if it is operational, the user may wish to send
packets again. However, it must be noted that if these kinds of
errors persist, the Ethernet is overloaded.
DEVSELREQ
device selection required Facility: ERF, Error Log Utility Explanation: A device type or class must be selected. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary to determine the appropriate qualifier for selecting a device type or class. Then reenter the command.
DEVSPEC
input specification for non-file-structured dump must contain only device Facility: DUMP, File Dump Utility Explanation: The input file specification can contain only the device component if the input medium is not a disk or tape device or if it is mounted with the /FOREIGN qualifier. User Action: Correct and reenter the command.
DEVWRTLCK
'date and time', Device 'device-name' has been write locked. Mount verification in progress Facility: OPCOM, Operator Communication Process Explanation: A write request to a Files-11 disk has failed because the device is not mounted write-locked. User Action: Cancel the mount verification, or remove the write lock on the volume.
DFL
data bucket fill size larger than bucket size for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The data bucket fill size specified in a key definition XAB exceeds the bucket size for the data area. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
DGQINCOMP
datagram queue operation incomplete Facility: SYSTEM, VMS System Services Explanation: A request to remove a certain number of datagrams from a queue succeeded only partially because there were fewer entries available than requested. This warning message should not appear. User Action: None.
DIAGNOSTIC
job controller read record limit exceeded Facility: JBC, Job Controller Explanation: The job controller keeps count of the number of read operations required to process a request. If the number exceeds a maximum value, the job controller considers this to be a looping condition and proceeds to abort and restart itself. This message is displayed on the operators terminal. The event is usually caused by a corrupted queue file, though it may indicate an internal job controller error. User Action: Enter a STOP/QUEUE/MANAGER command to close the queue file. If you have a cluster, do this on all nodes. Next, enter a START/QUEUE/ MANAGER command on one node. This will open the queue file and cause the job controller to perform a "cold start validation" of the file. If the queue file fails the test, create a new queue file before enabling Batch/Print facilities on the system.
DIAGPACK
disk is a diagnostic pack Facility: INIT, INITIALIZE Command, BACKUP, Backup Utility Explanation: Either the DCL command INITIALIZE is entered to initialize a volume that is identified as a diagnostic volume, or a Backup Utility operation is attempted using a volume identified as a diagnostic volume. In either case, the volume cannot be used. User Action: Retry the operation using another volume.
DIALFAI
autodial failed Facility: REM, Set Host Facility Explanation: The autodialer failed to dial the specified number. User Action: Verify the specified number and re-enter the command.
DIALINNOT
diagonal line not allowed Facility: SMG, Screen Management Facility Explanation: The vertices specified will result in a diagonal, rather than vertical or horizontal, line. User Action: Specify the vertices so that the line drawn will be vertical or horizontal.
DIFACCTS
values are 'account-name' and 'account-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message follows the COMPFAIL message and specifies the values (for the 'account-name' field of the job) in each of the two queue files being compared. User Action: If the specified difference is undesirable, make appropriate changes.
DIFCHARS
values are 'number', 'number', 'number', 'number' and 'number', 'number', 'number', 'number' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message follows the COMPFAIL message and specifies octaword values for the 'characteristics' field of the queue or job in each of the two queue files being compared. User Action: If the specified difference is undesirable, make appropriate changes.
DIFLWDS
values are 'longword' and 'longword' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message specifies the longword values for the field identified by the 'type-of-field' in the COMPFAIL message that precedes this message. User Action: If the specified difference is undesirable, make appropriate changes.
DIFSTRINGS
values are 'character-string' and 'character-string' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message specifies the different character string values for the field identified by 'type-of-field' in the COMPFAIL message that precedes this text. User Action: If the specified difference is undesirable, make appropriate changes.
DIFTIMES
times are 'date-and-time' and 'date-and-time' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message follows the COMPFAIL message and specifies the different values for the 'after-time' field of the job in each of the two queue files being compared. User Action: If the specified difference is undesirable, make appropriate changes.
DIFTYP
expected 'library-type' 'library-spec.' to be 'library-type' Facility: LIBRAR, LIBRARY Command Explanation: This warning message is generated by the DCL command LIBRARY. The referenced library is actually of a different type from that indicated in the command string. Processing continues based on the actual library type. User Action: None.
DIFVAL
memory contains different value than specified Facility: PATCH, Patch Utility Explanation: The value specified is not contained within the given memory location. User Action: Correct the value and retry the operation. DIGITAL Standard Runoff Version V3.0: 'number' diagnostic messages reported Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This is a standard error message line that specifies the actual number of error messages output. User Action: For more information refer to the specific error messages accompanying this message. DIGITAL Standard Runoff Version V3.0: No errors detected Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This message indicates the successful processing of a file by DSR. User Action: None.
DIR
error in directory name Facility: RMS, VMS Record Management Services Explanation: A directory name is specified incorrectly. For example, a directory or subdirectory name string contained more than 39 characters. Or, use of a logical name resulted in more than one directory name in the file specification. User Action: Verify the syntax of either the directory name in the file specification or the logical name, if a logical name is specified.
DIRALLOC
directory allocation failure Facility: SYSTEM, VMS System Services Explanation: The file system failed to allocate space to increase the size of a directory file. Because directory files must be contiguous, this error might be caused by the disk being full. More likely, there is not enough contiguous space on the disk for the directory, so the free disk space is being fragmented. User Action: Reorganize the free disk space by copying it with the Backup Utility, or restructure your application to use a larger number of smaller directories.
DIRECT
invalid directory syntax - check brackets and other delimiters Facility: CLI, Command Language Interpreter (DCL) Explanation: The directory name in a file specification entered for a command contains an illegal character; or a command that expects a directory name string did not find square brackets ([ ]) or angle brackets (<>) in the specified parameter. Note that this error can occur if a physical device name is specified without a colon following it. This error can also occur with VMS Version 4.4 or higher if you use Version 3.7 syntax to specify a concealed device (for example, using DUA0: instead of /TRANSLATION_CONCEALED). User Action: Examine the directory name (or logical name, if a logical name is specified). Correct the directory syntax and reenter the command.
DIRE_ERROR
above error occurred writing directory, volume might be corrupted Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error writing the directory of the volume. A more specific error message is printed immediately before this message. User Action: Since EXCHANGE might have already modified the volume in some way, it is possible that the directory stored on the volume does not match the current contents of the volume. It is possible to save all the files by creating a virtual volume and copying all files from the possibly corrupted volume. Note that this copy must be made before exiting EXCHANGE.
DIRENTRY
ACP failed to find same directory entry Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DIRFULL
directory is full Facility: SYSTEM, VMS System Services Explanation: An error occurred while a disk file is being created because the directory specified is full and cannot catalog any more entries. The maximum size of a directory file is 1024 blocks. If associated with a DECnet-VAX operation, this message indicates that the directory of declared network names is full. User Action: Delete or purge unwanted files from the directory and repeat the request; specify a different directory for the output file; or organize the directory into subdirectory levels to obtain more cataloging space. You can also use the BACKUP and RESTORE commands on the directory tree.
DIRNAME
directory file 'filespec' is not named '.DIR;1' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The specified file is marked with the DIRECTORY file characteristic, but it does not have a file type of DIR and a version number of 1. VMS RMS cannot recognize the file as a directory. User Action: Use the DCL command RENAME to rename the file.
DIRNOTCRE
'output file' directory file not created Facility: Shared by several facilities Explanation: A request to create a directory file over the network has failed. The creation of directory files over the network is currently unsupported. User Action: None.
DIRNOTEMPTY
directory file is not empty Facility: SYSTEM, VMS System Services Explanation: The directory you attempted to delete cannot be deleted because it contains files. User Action: Be certain that you want to delete the directory. Then, delete all the files in the directory first. If the directory is corrupted, use the DCL command SET FILE/NODIRECTORY to remove its status as a directory.
DIRSYNX
directive syntax error Facility: MACRO, VAX MACRO Assembler Explanation: The directive contained a syntax error. User Action: Correct the syntax of the directive.
DISCON
error disconnecting link to listener Facility: NCP, Network Control Program Explanation: An error occurred while disconnecting the link to NML. Information accompanying this message explains any secondary reasons for this error. User Action: Take corrective action based on the accompanying information.
DISCONNECT
process is disconnected from requested interrupt vector Facility: SYSTEM, VMS System Services Explanation: A connection is already outstanding for the device, or the driver cannot reallocate AST control blocks quickly enough. The latter condition can occur because insufficient AST control blocks (P6 argument) were specified, not enough pool space is available for the requested AST control blocks, or the process ASTCNT quota is exhausted. On a write request, a loss of carrier signal is detected on the Ethernet cable. User Action: Check the Ethernet cable for proper operation. Check the DEUNA hardware for proper operation. Check the H400 or other Ethernet transceiver for proper operation.
DISCONNECTED
session disconnected from 'service-name' Facility: LAT, LAT Facility Explanation: The SET HOST/LAT session has been disconnected. User Action: None.
DISKCLASS
fatal error detected by Disk Class driver (DUDRIVER) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DISKFRAG
free space on 'device-name' is too fragmented Facility: BACKUP, Backup Utility Explanation: The number of free extents on the specified volume is unreasonably large. The volume cannot be used as a save set disk. User Action: Reinitialize the volume or select another volume and retry the operation.
DISKS
disks Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operators terminal is enabled for "DISKS" class operations. User Action: None.
DISMAL
all of the volumes have been dismounted Facility: MOUNT, Mount Utility Explanation: All of the volumes mounted by this invocation of $MOUNT or the MOUNT command have been dismounted because of errors that were detected after the volumes had been mounted. Messages explaining the nature of the error that forced the dismount usually precede this message. User Action: Take the corrective measures mandated by the error messages preceding DISMAL, and reenter the MOUNT request.
DISMOUNTD
volume 'volume-name' of volume-set 'volume-set-name' dismounted Facility: MOUNT, Mount Utility Explanation: The specified volume of the specified volume set has been dismounted because of errors encountered in processing the volume after it is mounted. An error with part of a volume set causes the entire volume set to be dismounted. This message appears for each member of the volume set that is dismounted due to the error condition. Only those volumes that were mounted by this invocation of the MOUNT command are listed. If the volume set name is not available, the string "name n/a" appears as the name of the volume set. A message describing the error that caused the volume to be dismounted usually precedes this message. User Action: Correct the error condition specified in the accompanying message and reenter the MOUNT command.
DISMPART
some of the volumes have been dismounted Facility: MOUNT, Mount Utility Explanation: Some, but not all, of the volumes that were mounted by this invocation of the Mount Utility or the MOUNT command have been dismounted due to errors detected after the volumes had been mounted. Preceding messages explain the nature of the error that forced the dismount. Also preceding this message is a list of the volumes that were dismounted. User Action: Take the corrective measures mandated by the error messages preceding DISMPART, and reenter the MOUNT request.
DISPCHARSTIC
error obtaining information about definition for characteristic: name 'characteristic-name', number 'characteristic-number' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This message was encountered during a wildcard $GETQUI system service call attempt to display characteristics information. The information for this characteristic is not stored during the upgrade, hence it is lost after the upgrade. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade.
DISPERR
error during display or summary output Facility: MONITOR, Monitor Utility Explanation: An error occurred while displaying the requested MONITOR data to the SYS$OUTPUT device, or while performing output operations to the summary file. To obtain more information, examine the accompanying linked message. User Action: Correct the error indicated by the linked message and rerun the MONITOR command. Usually, this message represents a status value returned to MONITOR from one of the Run-Time Library terminal-independent screen procedures.
DISPFILE
error obtaining information about file 'filespec' in job 'job-name' for user 'user-name' in queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error was encountered during a wildcard $GETQUI system service call attempting to display file information. The information for this file is not stored during the upgrade, hence it is lost after the upgrade. User Action: The accompanying message gives information as to why the operation failed. Correct the problem and retry the upgrade.
DISPFORM
error obtaining information about definition for form: name 'form- name', number 'form-number' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error was encountered during a wildcard $GETQUI system service call attempt to display form information. The information for this form is not stored during the upgrade, hence it is lost after the upgrade. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade.
DISPJOB
error obtaining information about job 'job-name' for user 'user- name' in queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error was encountered during a wildcard $GETQUI system service call attempt to display job information. The information for this job and its files are not stored during the upgrade, hence it is lost after the upgrade. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade.
DISPLAY_SHORT
formatted message exceeds screen length in record 'nnn' Facility: AUDSRV, Audit Server Explanation: The entire text of the security alarm message could not be displayed because the terminal page length is not long enough. User Action: Increase the terminal page length, if possible, and try again.
DISPQUE
error obtaining information about definition for queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error was encountered during a wildcard $GETQUI system service call attempt to display queue information. The information for this queue, its jobs and their files are not stored during the upgrade and are lost after the upgrade. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade.
DISREQ
DISPLAY_ID parameter must be specified Facility: SMG, Screen Management Facility Explanation: A call to SMG$READ_VERIFY is made specifying right- justification, no DISPLAY_ID is specified, and the SCROLL_REVERSE sequence is not found for this terminal in TERMTABLE.EXE. Since right-justification requires a cursor positioning sequence to work properly, either the DISPLAY_ID parameter must be specified or the SCROLL_REVERSE sequence must be added to TERMTABLE.EXE. User Action: Add the DISPLAY_ID parameter to the SMG$READ_VERIFY call or add the SCROLL_REVERSE sequence to TERMTABLE.EXE.
DIVBY_ZER
division by zero Facility: STR, String Manipulation Facility Explanation: The string arithmetic routines attempted to take the reciprocal of a string whose numeric value is 0. User Action: The user should ensure that any string used as a divisor is not a null string or any other string whose numeric value is 0.
DIVBYZERO
divide by zero Facility: VAXTPU, VAX Text Processing Utility Explanation: Division by zero is not permitted. User Action: None is required. However, you may want to check the program for attempts to divide by zero and correct any occurrences you find.
DIVBYZERO
division by zero error Facility: MACRO, VAX MACRO Assembler Explanation: An expression contained a division by zero. User Action: Change the values in the expression.
DIVZERO
attempt to divide by zero Facility: PATCH, Patch Utility Explanation: An expression contained a division by zero. User Action: Correct the value and retry the operation.
DNA
invalid default file name string address Facility: RMS, VMS Record Management Services Explanation: The default file specification string address field in the FAB is not valid, or is in an area of memory that cannot be read by the caller. User Action: Check for a programming error. Verify that the call to the VMS RMS service is coded correctly.
DNF
directory not found Facility: RMS, VMS Record Management Services Explanation: The specified directory name does not exist on the specified device. User Action: The status value (STV) field of the FAB contains a system status code that provides additional information. Verify that both the device and directory are specified correctly. Create a directory on the device, if necessary, or specify an existing directory.
DNR
device not ready, not mounted, or unavailable Facility: RMS, VMS Record Management Services Explanation: An input/output operation cannot be performed because the physical device is not ready, the required volume has not been mounted, the device has been allocated to another user, or a file header on the volume has been corrupted. User Action: Make sure that the volume is physically loaded, the device is ready, and the DCL command MOUNT has completed successfully. Check that the correct controller is set on the drive. Then retry the command or program. If the error reoccurs, and the volume is a structured disk, use the DCL command ANALYZE /DISK_STRUCTURE to check the volume for file header corruption.
DNS
.NO SPACE illegal in this context
Facility: RUNOFF, DIGITAL Standard Runoff
Explanation: A .NO SPACE command has been inserted following a
command that issues a .BREAK.
User Action: Remove the .NO SPACE command, or put it in the
correct place.
Do you want to create a new file?
Facility: AUTHORIZE, Authorize Utility
Explanation: The Authorize Utility is prompting you for an answer.
User Action: Respond YES (Y) or NO (N).
'virtual-unit:' does not contain the member named to VMB. System may not reboot.
Facility: OPCOM, Operator Communication Process
Explanation: Either of the following conditions can cause this
message:
o The boot device is dismounted or failed out of the system disk
shadow set.
o Shadowing finds the boot device missing from the system disk
shadow set membership during any dismount operations on the
system disk.
User Action: Mount the boot device back into the shadow set as
soon as possible. If you cannot mount the boot device back into
the shadow set, change the device name in VMB so the system can
reboot.
DOESNTFIT
'string' will not fit at current indentation level Facility: DSR, DIGITAL Standard Runoff Explanation: The indicated string will not fit on a line with the proper indentation of the index entry or subentry. User Action: Hyphenate the word using the .HYPHENATE and .BREAK flags.
DONEMSG
system authorization file modified Facility: AUTHORIZE, Authorize Utility Explanation: This is an informational message. User Action: None.
DOS11_BADLABEL
volume on 'tapedrive' has label with invalid format Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received an error trying to read a DOS-11 magtape label, or the label did not have a valid format. User Action: In the case of an input error, a second message will follow the BADLABEL message. Take corrective action based on the following message. In the case of invalid format, the tape mounted on the drive is not a valid DOS-11 volume. Find and mount the correct DOS-11 tape and retry the operation.
DOS11_BLOCKSIZE
volume on 'tape' has block larger than 512 bytes Facility: EXCHANGE, Exchange Utility Explanation: While reading a DOS-11 magtape, the Exchange Utility has read a block which is longer than 512 bytes. User Action: The file containing the long block cannot be processed by EXCHANGE.
DOS11_IOERROR
error during I/O on volume 'volume' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error during input or output on a DOS-11 magtape volume. User Action: A second message describing the actual error condition will follow this message. Take corrective action based on the contents of the second message.
DOS11_POSITION
rewinding tape to recover correct positioning Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has lost its position on a DOS-11 magtape, usually due to an input or output error. User Action: EXCHANGE will rewind the tape and move to the correct position. Please wait for this to complete.
DOUBLDALOC
double deallocation of swap file space Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DOUBLDEALO
double deallocation of memory block Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
DPE
device positioning error Facility: RMS, VMS Record Management Services Explanation: A magnetic tape file is not positioned properly. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a system status code that provides additional information about the condition. Take corrective action based on this status code. Retry the operation. If the error persists, it may indicate a system software or hardware failure. Notify your system operator or manager.
DQCLUS
device is mounted clusterwide, CLUSTER environment ignored Facility: SMI, System Management Integrator/Server Explanation: Disk quota functions are already operating in a cluster environment. To avoid duplicate efforts, the command is only executed on the first node in the cluster. User Action: Do not specify the /CLUSTER qualifier with the SET ENVIRONMENT command.
DRIVENAM
driver name is 'driver-name' Facility: SYSGEN, System Generation Utility Explanation: This message is issued with the message SYSVERDIF to identify the driver. User Action: See the SYSGEN message SYSVERDIF for user action information.
DRIVERNOTSHUT
LATACP not initialized because driver not completely shut down Facility: LAT, LAT Facility Explanation: An attempt was made to run the LATACP process before the previous driver shutdown request had completed. User Action: Wait until driver shutdown tasks have completed before attempting to start LATACP or determine whether some condition is preventing LAT driver shutdown from completing.
DRVERR
fatal drive error Facility: SYSTEM, VMS System Services Explanation: An input or output operation failed because of an error in a disk or magnetic tape drive. If this message is associated with a status code returned by a request to a DR11-W interface, a fatal error that affects all DR11-W activity is set in the DR11-W CSR on completion of the QIO request. Look at the third and fourth words of the IOSB (CSR and EIR) for the specific cause of the error. If the condition indicated in the CSR can be cleared, that is, if the ATTN bit can be cleared, SS$_DRVERR is returned. If the condition cannot be cleared, SS$_CTRLERR is returned. In both cases, the driver performs a device reset to the DR11-W. If this message is returned by a request to a magtape or a disk driver, it is a drive-related error. One or more of the following conditions can cause this error: o Drive or driver timing error o Illegal function o Illegal register o Operation incomplete o Register modify refused o Write clock failure (disk driver-specific) o Nonexecutable function (magnetic tape-specific) o Unrecovered reproducible error (magnetic tape-specific) User Action: Check the status of the device and reenter the command. Verify that the drive is on, loaded, and mounted correctly. If the failure persists, notify the system manager.
DRVRSTRT
error while issuing startup command to driver Facility: CNF, NI Configurator Explanation: An error occurred while attempting to issue the startup commands to the NI driver in preparation to reading the broadcast system ID messages. User Action: See the accompanying message to determine the appropriate action.
DSAQUOTA
error disabling quota processing Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to disable quota processing. An accompanying message provides additional information. User Action: Correct the condition that caused the error and use the SYSMAN command DISKQUOTA DISABLE to disable quota processing.
DTP
invalid key data type for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The key data type specified in a key definition XAB is not a valid data type code. The valid key data codes are: STG (default), BN2, BN4, BN8, IN2, IN4, IN8, PAC, COL, DSTG, DBN2, DBN4, DBN8, DIN2, DIN4, DIN8, DPAC, and DCOL. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
DTRBADMAIL
unexpected mail received, type is 'mail-type' Facility: DTR, DECnet Test Program Protocol Explanation: The logical link is broken. User Action: Retry the operation.
DTSBADMAIL
unexpected mail received, type is 'mail-type' Facility: DTS, DECnet Test Program Protocol Explanation: The logical link is broken. User Action: Retry the operation.
DUALLOC
dual allocation on volume 'n' Facility: MOUNT, Mount Utility Explanation: A logical block on the relative volume identified in the message is allocated to more than one file. User Action: Use the DCL command ANALYZE/DISK_STRUCTURE/NOREPAIR for the volume. This command invokes the Analyze/Disk_Structure Utility, which issues a message for each occurrence of dual file allocation. These messages identify the file name, the range of logical block numbers that have been dually allocated, and the virtual block numbers that the logical blocks map to. You can examine the messages to determine the files involved in each case of dual allocation. Then, without allowing other file activity, copy all but one file involved in each case of dual allocation to a new version. After you create new versions of the applicable files, delete the versions containing dual allocation. In this way, blocks that are not actually free are marked as free blocks in the storage bit map. Next, rerun the utility on the volume, using the ANALZYZE/DISK_STRUCTURE/REPAIR command. Finally, examine each file and reconstruct from backup media those files that have been corrupted. Dump aborted, page tables may be corrupted Facility: BUGCHECK, System Bugcheck Explanation: When writing a selective dump (SYSGEN parameter DUMPSTYLE set to 1), the VMS operating system relies heavily on the integrity of the various system and process page tables. This message indicates that the system might have detected corruption in these page tables, and it will abort further dumping. You might not be able to analyze the dump. User Action: Submit a Software Performance Report (SPR).
DUMPEMPTY
dump file contains no valid dump Facility: SDA, System Dump Analyzer Explanation: The SDA cannot read the contents of the system dump file. The system dump file may be unreadable because the data is bad or because the file is empty. If the SDA cannot read the dump file, it will not run. User Action: None.
DUMPERRORS
'number' errors occurred while writing the dump file Facility: SDA, System Dump Analyzer Explanation: The first block of the dump file contains information indicating that there were 'number' errors while writing out the information to the dump file. User Action: None. The dump file might not be useful for analysis.
DUMPINCOMPL
the dump file write was not completed Facility: SDA, System Dump Analyzer Explanation: The process of writing out the dump file was aborted. The dump file is not complete, and it is not useful for dump analysis. User Action: None. The dump file is not useful for analysis.
DUP
duplicate key detected (DUP not set) Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $PUT or $UPDATE operation specified a record that contained one or more key values that duplicated key values in other records stored in the file, and the key does not have the DUPLICATES ALLOWED attribute. User Action: Either reorganize the file and specify that duplicate keys are allowed, or modify the source program to detect and respond to the condition.
DUP
duplicate key encountered Facility: CONVERT, Convert Utility Explanation: More than one record in the input file has the same value in a key field, but duplicate keys are not allowed. User Action: Either allow duplicate keys or change the key values.
DUPBLKNUM
duplicate block number 'nnnnnnnn', already exists in 'xDBSF' Facility: BAD, Bad Block Locator Utility Explanation: The block number specified in the /BAD_BLOCKS list is already recorded in either the MDBSF or the SDBSF. The block is ignored, and processing continues. User Action: None.
DUPBUFNAME
buffer 'name' already exists Facility: VAXTPU, VAX Text Processing Utility Explanation: The first argument for the built-in procedure CREATE_ BUFFER must be a unique string. You have specified a name that already exists. User Action: Reenter the command with a different string as the first argument.
DUPCHARNAME
duplicate characteristic name Facility: JBC, Job Controller Explanation: A DEFINE/CHARACTERISTIC command specified a characteristic name that is already defined. Each characteristic must have a unique name. User Action: Choose a name that is not yet defined or delete the old definition and redefine it.
DUPCHARNUM
duplicate characteristic number Facility: JBC, Job Controller Explanation: A DEFINE/CHARACTERISTIC command specified a characteristic number that is already defined. Each characteristic must have a unique number. User Action: Choose a number that is not yet defined or delete the old definition and redefine it.
DUPCOMFIL
command file 'filespec' already being written Facility: PATCH, Patch Utility Explanation: You have already requested that a command procedure be written for this PATCH session. User Action: None.
DUPDEF
duplicate definition of 'name' encountered Facility: CDU, Command Definition Utility Explanation: CDU encountered a DEFINE statement in which there is already a definition with the same name. User Action: Edit the CLD file so that all definitions use unique names.
DUPDEVSPC
duplicate device specified Facility: MOUNT, Mount Utility Explanation: The same tape device is specified more than once in a list of tape devices for the DCL command MOUNT. User Action: Reenter the MOUNT command specifying each device only once.
DUPDSKQUOTA
duplicate disk quota file entry Facility: SYSTEM, VMS System Services Explanation: Another quota entry for the specified UIC already exists. User Action: Check the UIC listed. Correct the UIC or select and reenter another UIC.
DUPFILENAME
duplicate file name Facility: SYSTEM, VMS System Services Explanation: The directory specified already contains an entry for the specified file name, file type, and version number. User Action: Delete the existing file, or correct the command or program to change the file name, file type, or version number specified for the output file.
DUPFORM
duplicate form number Facility: JBC, Job Controller Explanation: A DEFINE/FORM command specified a form number that is already defined. Each form must have a unique number. User Action: Specify the command so that each form is defined uniquely.
DUPFORMNAME
duplicate form name Facility: JBC, Job Controller Explanation: A DEFINE/FORM command specified a form name that is already defined. Each form must have a unique name. User Action: Choose a name that is not yet defined or delete the old definition and redefine it.
DUPGLOBAL
global symbol 'symbol-name' from file 'library-filespec' already in library 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. An attempt is made to insert an object module containing a global symbol that is already in the global symbol table (GST). User Action: Replace the module instead of inserting it; or remove the global symbol from the library before inserting the module.
DUPIDENT
only one IDENT statement is allowed Facility: CDU, Command Definition Utility Explanation: More than one IDENT statement is encountered in a single CLD file. Only one IDENT statement is allowed. User Action: Edit the CLD file so that there is only one IDENT statement.
DUPINVALID
component file already in STARTUP table Facility: SMI, System Management Integrator/Server Explanation: An attempt is made to add a startup component file to the component database which already contains that entry. User Action: Either use the STARTUP MODIFY FILE command at the SYSMAN> prompt to change the existing entry, or reenter the command with a new component file name.
DUPKEY
duplicate key in index Facility: LBR, Librarian Subroutine Package Explanation: This message is generated by the Librarian routines. On a call to LBR$INSERT_KEY, the specified key is found to exist already. User Action: Call LBR$REPLACE_KEY to replace the existing key.
DUPKEY
keyword 'keyword-name' has already been defined Facility: CDU, Command Definition Utility Explanation: CDU encountered a KEYWORD definition that conflicts with an existing KEYWORD definition with the same name. KEYWORD definitions in the same TYPE definition must be unique. User Action: Edit the CLD file so that each KEYWORD definition in the same TYPE definition is unique.
DUPKEYMAP
attempt to define a duplicate key map 'key-map-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You are trying to create a key map with the same name as a key map or key-map list that already exists. User Action: Select another name for the new key map.
DUPKEYMAPLIST
attempt to define a duplicate key-map list 'key-map-list-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You are trying to create a key-map list with the same name as a key map or key-map list that already exists. User Action: Select another name for the new key-map list.
DUPLABEL
only one LABEL clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one LABEL clause in a single qualifier/parameter definition. Only one LABEL clause is allowed per qualifier/parameter definition. User Action: Edit the CLD file so that each qualifier/parameter definition does not contain more than one LABEL clause.
DUPLNAM
duplicate name Facility: SYSTEM, VMS System Services Explanation: A process name specified in a request to create a process duplicates the name of an existing process executing with the same group number. Process names must be unique within a group. User Action: Specify an alternative process name. Check whether the existing process with that name should be deleted and, if so, use the DCL command STOP to delete it.
DUPMOD
module 'module-name' from file 'library-filespec' already in 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The module you are inserting into the library already exists in the module name table (MNT). User Action: Change the name of the module or replace the existing module with a new one.
DUPMODULE
module 'module-name' from file 'filename' already in 'name' Facility: LIBRAR, LIBRARY Command Explanation: One of the modules being inserted into the library already exists in the library module name table. User Action: Change the name of the module being inserted, delete the module of the same name from the library, or use the LIBRARY /REPLACE option to replace the module.
DUPMODULE
only one MODULE statement allowed Facility: CDU, Command Definition Utility Explanation: More than one MODULE statement is encountered in a single CLD file. Only one MODULE statement is allowed. User Action: Edit the CLD file so that there is only one MODULE statement.
DUPMSG
message code nn already assigned as ss Facility: MESSAGE, Message Utility Explanation: You have assigned the same message code (nn) to more than one message symbol. The first message symbol (ss) assigned to the message code is shown. User Action: Check that you have not assigned twice the same message number or symbol for the same facility. Reenter the message definitions so a different message symbol is assigned to one message code.
DUP_OUTPUT
output file has already been specified Facility: SORT, Sort/Merge Utility Explanation: You passed the output file argument in the routine package more than once. User Action: Check your file arguments and verify that you specified the output file only once.
DUPPLACE
only one PLACEMENT clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one PLACEMENT clause in a single qualifier definition. Only one PLACEMENT clause is allowed per qualifier definition. User Action: Edit the CLD file so that each qualifier definition does not contain more than one PLACEMENT clause.
DUPPREFIX
only one PREFIX clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU has encountered more than one PREFIX clause in a single verb/syntax definition. Only one PREFIX clause is allowed per verb/syntax definition. User Action: Edit the CLD file so that each verb/syntax definition does not contain more than one PREFIX clause.
DUPPROMPT
only one PROMPT clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one PROMPT clause in a single parameter definition. Only one PROMPT clause is allowed per parameter definition. User Action: Edit the CLD file so that each parameter definition does not contain more than one PROMPT clause.
DUPQUAL
qualifier 'qualifier-name' has already been defined Facility: CDU, Command Definition Utility Explanation: CDU has encountered a previously defined qualifier in a single verb/syntax definition. All qualifiers defined in a single verb/syntax definition must be unique. User Action: Edit the CLD file so that all qualifiers defined in a single verb/syntax definition are unique.
DUPRVN
duplicate volume number already mounted Facility: MOUNT, Mount Utility Explanation: A volume of the same relative volume number and the same volume set name is already mounted. You are trying to mount a volume that belongs to a volume set with the same name as a volume set that is already mounted. User Action: Make sure that you have mounted the correct volume. Verify that you are defining the volume status (/SHARE, /NOSHARE, /GROUP, or /SYSTEM) consistently with volumes already mounted.
DUPSYM
'name' is a duplicate symbol definition Facility: CDU, Command Definition Utility Explanation: The same name is used twice. For example, this error could occur because the same syntax list or qualifier name appears twice in the CLD file. User Action: Modify the CLD file to correct the duplication.
DUPSYM
duplicate symbol definition Facility: MESSAGE, Message Utility Explanation: You have assigned the same symbol to represent two values. This message may refer to symbols defined in a message definition, a facility definition, or the .LITERAL directive. User Action: Reenter your source statements with each symbol defined only once.
DUPSYNTAX
only one SYNTAX clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one SYNTAX clause in a single qualifier/parameter definition. Only one SYNTAX clause is allowed per qualifier/parameter definition. User Action: Edit the CLD file so that each qualifier/parameter definition does not contain more than one SYNTAX clause.
DUPTYPE
only one TYPE clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one TYPE clause in a single value definition. Only one TYPE clause is allowed per value definition. User Action: Edit the CLD file so that each value definition does not contain more than one TYPE clause.
DUPUNIT
MSCP Controller - duplicate unit number Facility: SYSTEM, VMS System Services Explanation: On a STARTUP request, the user cannot assign two channels to an XE unit before the unit is started in SHARED mode. The driver may have to relink the user's Channel Control Block (CCB) to a different UCB and this cannot be done if there are two CCBs that must be reset. User Action: The user must STARTUP the XE unit in SHARED mode before assigning any extra channels to the XE unit.
DUPVALUE
only one VALUE clause is allowed Facility: CDU, Command Definition Utility Explanation: CDU encountered more than one VALUE clause in a single qualifier/parameter definition. Only one VALUE clause is allowed per qualifier/parameter definition. User Action: Edit the CLD file so that each qualifier/parameter definition does not contain more than one SYNTAX clause.
DUPVOLNAM
volume label already present in set Facility: MOUNT, Mount Utility Explanation: During an attempt to add a volume to an existing volume set, the specified volume set is found to contain a volume with the label specified. User Action: Verify the labels on the existing volumes in the set. Choose a new label for the volume you are adding to the set, reinitialize the volume, and reenter the DCL command MOUNT/BIND.
DVI
invalid device ID value in NAM block Facility: RMS, VMS Record Management Services Explanation: The device identification field of the VMS RMS NAM block is not valid. User Action: Verify that the call to the VMS RMS service is coded correctly.
DVN
duplicate variable name: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: An attempt has been made to use a name specification with a .VARIABLE command that has already been used with a previous .VARIABLE, .IF, .IFNOT, or .ELSE command. User Action: Change the name specification.
DX1
in-core indexing (.DO INDEX/.PRINT INDEX) is no longer supported Facility: RUNOFF, DIGITAL Standard Runoff Explanation: In-core indexing is no longer supported. User Action: See accompanying message.
DX2
instead, specify RUNOFF/INTERMEDIATE and .REQUIRE 'file.RNX' here. Facility: RUNOFF, DIGITAL Standard Runoff Explanation: In-core indexing is no longer supported. See accompanying message. User Action: Specify RUNOFF/INTERMEDIATE and .REQUIRE 'file.RNX'.
ECONOTSET
eco level 'nn' not set in 'filespec' Facility: PATCH, Patch Utility Explanation: You specified an ECO level that is not set in that particular image file. This typically occurs when you enter the PATCH command CHECK ECO before entering the PATCH command UPDATE. User Action: Enter a SET ECO command to reenable the Patch Utility command processing. Specify the correct ECO level and retry the operation.
ECOSET
eco level 'nn' already set in 'filespec' Facility: PATCH, Patch Utility Explanation: You specified an ECO level that has already been set in that particular image file. User Action: Enter a SET ECO command to reenable the Patch Utility command processing. Specify the correct ECO level and retry. Editor aborted Facility: EDT, EDT Editor Explanation: EDT experienced some difficulties and had to abort the session. User Action: Use the journal file to recover your editing work.
EDITPROC
error creating or executing editor subprocess Facility: MAIL, Mail Utility Explanation: You entered the SEND/EDIT command and MAIL's attempt to create a subprocess failed. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
EDITSCLSH
edits clash 'editing-commands' 'filespecs' Facility: SUMSLP, SUMSLP Batch Editing Utility Explanation: Two or more conflicting editing commands have been entered, that is, more than one edit operation has been specified for one line of source code. The relevant editing commands and the file specifications of the SUMSLP command files are listed following this informational message. User Action: None.
EDOUTSEQ
edits out of sequence Facility: SUM, Source Update Merge Utility and SUMSLP, SUMSLP Batch Editing Utility Explanation: The indicated edit command is not in ascending sequence within the update file. The editing operation has been performed correctly. User Action: Edit the update file to place the edit in the correct position.
EF_ALRFRE
event flag already free Facility: LIB, Library Facility Explanation: A call is made to LIB$FREE_EF to free an event flag number that is not allocated. User Action: Ensure that you use the correct event flag number in the call to LIB$FREE_EF.
EF_ALRRES
event flag already reserved Facility: LIB, Library Facility Explanation: A call is made to LIB$RESERVE_EF to receive an event flag number that is already allocated. User Action: Ensure that you use the correct event flag number in the call to LIB$RESERVE_EF.
EFD
.END FOOTNOTE doesn't terminate .FOOTNOTE Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The .ENDFOOTNOTE command is improperly positioned in the file; it does not follow associated footnote data. User Action: Put the .ENDFOOTNOTE command in the correct place, or remove it.
EF_RESSYS
event flag reserved to system Facility: LIB, Library Facility Explanation: A call is made to LIB$RESERVE_EF to reserve an invalid event flag number. Ranges for valid event flag numbers are 1 through 23 and 32 through 63. User Action: Retry specifying a valid event flag number.
ELD
.END LITERAL doesn't follow .LITERAL Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The .END LITERAL command is improperly positioned in the file; it does not follow the .LITERAL command. User Action: Put the .END LITERAL command in the correct place, or remove it.
ELEALREXI
an element of the same name already exists Facility: PPL, Parallel Processing Facility Explanation: An element by this name already exists, and its ID is returned. User Action: Continue normally if you expect the name to exist.
ELETOOLON
element too long, maximum 255 characters Facility: LIB, Library Facility Explanation: The initialization string element passed to LIB$INIT_ DATE_TIME_CONTEXT is too long; the maximum length allowed is 255 characters. User Action: Begin debugging procedures to verify and correct the problem.
EMPTY_CHECK
checkpoint contains no active transactions Facility: LMCP, Log Manager Control Program Explanation: There are no active transactions in the displayed checkpoint record. User Action: None
EMPTYDEF
no attributes supplied - DEFINE ignored Facility: CDU, Command Definition Utility Explanation: The CLD file does not contain any attributes. User Action: Add attributes to the CLD file.
EMPTYFILE
no modules found in file 'filename' Facility: LINK, Linker Utility Explanation: An object file contained no object modules. User Action: Ensure that the source file compiled properly and that the output object file is not empty.
EMPTYFILE
zero-length page or swap file cannot be installed Facility: SYSGEN, System Generation Utility Explanation: You attempted to install a zero-length page or swapping file. User Action: None. You cannot install a zero-length page or swapping file.
EMPTYHIST
library update history is empty Facility: LBR, Librarian Subroutine Package Explanation: The library has an update history, but no update history records are present. User Action: None.
EMPTYIN
empty input file 'filename' Facility: DSR, DIGITAL Standard Runoff Explanation: The input file contained no data for processing. User Action: Edit the input file.
EMPTYJOB
no files specified in job request Facility: JBC, Job Controller Explanation: A batch or print job is requested that did not specify any files to process. This error condition occurs if the requesting process opened and closed a job using the SJC$_ CREATE_JOB and SJC$_CLOSE_JOB function codes, but did not specify any files with the SJC$_ADD_FILE function of the $SNDJBC system service. This condition causes the open job to be removed from the system job queue file. User Action: None.
EMPTYKMLIST
key-map list 'key-map-list-name' does not contain any key maps Facility: VAXTPU, VAX Text Processing Utility Explanation: You are referring to a key-map list that has no key maps. User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the command line to obtain the names of the key-map lists and their key maps.
EMPTYLIBRARY
no modules in library: 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: The library being compressed contains no modules. User Action: None.
EMPTYLST
known file entry list is empty Facility: INSTALL, Install Utility Explanation: There are no entries in the known file entry list. Therefore, LIST, DELETE, REMOVE, and PURGE will have no effect. User Action: None.
EMSKNOTABS
entry mask not absolute Facility: MACRO, VAX MACRO Assembler Explanation: The entry mask expression is not absolute or it contained undefined symbols. User Action: Change the values in the expression.
ENAQUOTA
error enabling quota processing Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to enable quota processing. An accompanying message provides additional information. User Action: The utility does not reconstruct disk quota information. Try to correct the condition that caused the error and then reenter the command.
END
control returned to node 'node-name' Facility: LAT, LAT Facility Explanation: The SET HOST/LAT session has ended. User Action: None.
END
control returned to node 'node-name' Facility: REM, Set Host Facility Explanation: This informational message reports that a remote terminal session has ended. If DECNET has not been started on your system, _0:: is displayed in place of your node name. User Action: None.
ENDABORT
'name' compilation aborted Facility: Shared by several facilities Explanation: Serious errors prevented the compilation of 'name' from being completed. User Action: Correct the errors and recompile the program.
ENDDIAGS
'name' completed with 'nnn' diagnostics Facility: Shared by several facilities Explanation: The compilation or assembly of 'name' is completed with diagnostics. Use of the object module produced may give invalid results. User Action: Correct the conditions which resulted in the diagnostics and recompile or reassemble the program.
ENDED
'name' ended Facility: Shared by several facilities Explanation: A program phase has been ended. User Action: None.
ENDEDD
'name' ended at 'system date and time' Facility: Shared by several facilities Explanation: A program phase has been ended. User Action: None.
ENDEDT
'name' ended at 'system time' Facility: Shared by several facilities Explanation: A program phase has been ended. User Action: None.
ENDNOOBJ
'name' completed with 'nnn' diagnostics-object deleted Facility: Shared by several facilities Explanation: The compilation or assembly of 'name' is completed with errors. No object file is produced. User Action: Correct the source language errors and recompile or reassemble.
ENDOFBUF
attempt to move past the end of buffer 'buffer-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You attempted to move past the end of the current buffer. VAXTPU makes offset 0 of the end-of-buffer mark the current editing position. User Action: Stop trying to move forward. You are already positioned at the end of the buffer.
ENDOFFILE
end of file
Facility: SYSTEM, VMS System Services
Explanation: You received this message because of one or more of
the following conditions:
o A tape mark indicating end-of-file is encountered during an
attempt to read a tape. For data transfer functions, the byte
count is zero; for skip record functions, the count is the
number of blocks skipped.
o An end-of-file card is encountered during an attempt to read
from the card reader.
o A mailbox is empty or had an end-of-file (IO$_ENDOFFILE)
written to it.
o No data is available for transfer on the DMC-11, and IO$M_NOW
is specified.
o The file system ACP encountered the end of the allocated space
for a virtual I/O operation or an attempted truncation.
User Action: Note the condition. If necessary, modify the source
program to detect and respond to the condition.
ENDOFFILE
end of file on read to terminal or file Facility: VAXTPU, VAX Text Processing Utility Explanation: Premature end-of-file encountered on read from input device or file. User Action: Submit a Software Performance Report (SPR).
ENDOFTAPE
end of tape Facility: SYSTEM, VMS System Services Explanation: The end of tape marker, indicating the physical end of the tape, is encountered. User Action: Note the condition. If the tape marker is encountered during an operation in the forward direction, it may be necessary to modify the source program to detect and respond to the condition.
ENDOFVOLUME
end of volume Facility: SYSTEM, VMS System Services Explanation: Two consecutive tape marks were detected during a skip file operation to a tape mounted non-file-structured or during a skip record operation. This return is also used as a logical end-of-tape indicator for non-ANSI tapes. If an ANSI standard tape is mounted foreign, this may only indicate an empty file within the volume and not the end of the volume. The high word of the first longword in the I/O status block contains the number of tape marks passed. User Action: Use a read function to read data located past the double tape mark. (The first read function returns end-of-file status; a second read function reads the data.)
ENDPRS
error code of 'xx' on command line parse end Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry.
ENDTOPIC
request LBR$OUTPUT_HELP terminate printing Facility: LBR, Librarian Subroutine Package Explanation: When a user-supplied output routine is called by LBR$OUTPUT_HELP, the output routine returns this status to terminate the printing of help text. User Action: None.
ENDWRNGMAC
.ENDM does not end macro 'macro-name' in 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This warning message is generated by the DCL command LIBRARY. The macro name following the .ENDM statement does not match the name of the macro it should end. User Action: Reformat the macro source file.
ENDWRNGMAC
statement ends wrong MACRO Facility: MACRO, VAX MACRO Assembler Explanation: The .ENDM directive specified a different name from its corresponding .MACRO directive. User Action: Correct the name in the .ENDM directive to ensure that the .ENDM directive and .MACRO directive correspond as required.
ENGLUSED
English used, could not determine user's language Facility: LIB, Library Facility Explanation: Translation of the logical SYS$LANGUAGE (or any logicals depending on the specified language) failed, or the tables supporting the selected language were not chosen by your system manager. English is being used. User Action: Examine SYS$LANGUAGE. Verify that the logical name table for the language is built and that all logicals depending on SYS$LANGUAGE (for example, logicals to supply spellings of months and days of the week) are correct.
ENQ
ENQ system service request failed Facility: RMS, VMS Record Management Services Explanation: A $ENQ or $DEQ system service invoked by RMS failed. The status value (STV) field of the FAB contains a code that provides more information about the condition. User Action: Correct the condition described in the STV field. Take corrective action based on this system status code.
ENT
ACP enter function failed Facility: RMS, VMS Record Management Services Explanation: An attempt to enter a file specification in a directory failed. This message is associated with a status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
ENTERED
'filespec' entered as 'filespec' Facility: SET, SET Facility Explanation: The file has been entered successfully. This message is displayed when you specify the /LOG qualifier with the SET FILE /ENTER command. User Action: None.
ENTERLOST
file ('file-id') 'filename' error entering file in directory
[SYSLOST]
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to enter
the specified file in directory [SYSLOST]. An accompanying message
provides additional information.
User Action: Correct the condition that caused the error and
reenter the command.
ENTERR
error entering 'filespec' as 'filespec' Facility: SET, SET Facility Explanation: An error occurred while attempting to enter a synonym for a file. This message is accompanied by another message explaining why the synonym could not be entered. User Action: Respond to the accompanying message.
ENTFIL
error entering file on queue Facility: INPSMB, Input Symbiont Explanation: The system encountered an error creating a batch job from card reader input. The accompanying message provides additional information. User Action: Correct the error and reenter the job.
ENTIDMTCH
'string' ident of 'string' for entity 'string' in module 'module- name' file 'file-name' does not match ident of 'string' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The specified modules were not compiled with the same external files (for example, a library). User Action: Recompile the modules in error.
ENTIDMTCHB
'string' ident of number 'number' for entity 'string' in module 'module-name' file 'file-name' does not match ident of number 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The specified modules were not compiled with the same external files (for example, a library). User Action: Recompile the modules in error.
ENTIDMTCHO
object type of 'string' for entity 'string' in module 'module-name' file 'filename' does not match object type of 'string' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: You specified different object types. User Action: Recompile using the same object types.
ENTIDMTCHT
ident type for entity 'string' in module 'module-name' file 'file- name' differs from ident type in module 'module-name' file 'file- name' Facility: LINK, Linker Utility Explanation: You specified both a binary and string ident for a single entity. User Action: Recompile, specifying either a binary or string ident, but not both the same entity. Entity must be WORD, SENTENCE, PAGE, or PARAGRAPH Facility: EDT, EDT Editor Explanation: The EDT command SET ENTITY is entered without one of the following four entity options: WORD, SENTENCE, PAGE, PARAGRAPH. User Action: Reenter the command specifying one of the four entity options displayed in the message text.
ENTNF
specified entity not found in command tables Facility: CLI, Command Language Interpreter (DCL) Explanation: The parameter, qualifier, or keyword specified as input to one of the CLI$xxxx routines does not exist in the command tables. User Action: Check the spelling of the entity and its existence in the command tables.
ENTNOTFOU
node/service entity not found Facility: LAT, LAT Facility Explanation: An attempt to locate information about a specified node or service ended with the local node finding no such information. User Action: Check the network to ascertain that the specified node or nodes offering the specified service are available. Also, check that the group codes offered by the specified node or service coincide with the local node's user groups.
ENV
current Command Environment Facility: SYSMAN, Cluster System Management Utility Explanation: The current environment is changed with the SET ENVIRONMENT command. User Action: Verify that the listed environment is correct.
ENV
support for RMS service call or feature not present Facility: RMS, VMS Record Management Services Explanation: An image attempted a VMS RMS function that is not supported in this version of VMS RMS. User Action: Consult the system manager to find out which functions are supported or to include your desired function.
ENVNOTSET
environment not changed Facility: SYSMAN, Cluster System Management Utility Explanation: An error occurred in processing a SET ENVIRONMENT command. The previous environment is still in effect. User Action: Take action according to the specific error message accompanying this message.
EOF
end of file detected Facility: RMS, VMS Record Management Services Explanation: An end-of-file condition occurred on a VMS RMS service. User Action: If necessary, modify the source program to detect and respond to the condition.
EOF
end of input Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont input routine indicating the end of input. User Action: None.
EOF
end-of-file Facility: SMG, Screen Management Facility Explanation: End of file condition is detected on input. User Action: If necessary, modify your program to recognize this condition and respond to it.
EOFMISMATCH
end of file position mismatch for 'filespec' Facility: BACKUP, Backup Utility Explanation: During a compare or verify operation, the end-of-file pointer for the specified file did not agree with the input file. If other file activity is occurring on the volume, the error may be caused because another user modified the file during the backup operation. User Action: Note that the copies are inconsistent.
EOMERROR
compilation errors in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an internal error in the operating system, submit a Software Performance Report (SPR).
EOMFATAL
fatal compilation errors in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
EOMFTL
link abort specified in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module specified link abort. User Action: Correct the source for the module, recompile, and relink.
EOMSTK
'number' items left on Linker internal stack in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module did not leave the linker stack empty. User Action: Submit a Software Performance Report on the appropriate language compiler.
EOMWARN
compilation warnings in module 'module' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errrors indicate an operating system internal error, submit a Software Performance Report (SPR).
EOTIN
EOT response to text Facility: SYSTEM, VMS System Services Explanation: The IBM system has sent an EOT instead of an expected acknowledgment to XKDRIVER after receiving a block of data from XKDRIVER. User Action: Either a normal condition exists where the IBM host has acknowledged the receipt of a block of text with an EOT instead of an ACK (in this case, you do not need to provide corrective action), or an error has occurred. When an error occurs, you may need to correct and retransmit the last block of data to the IBM host.
EQV_NOTICE
equivalent name - device 'controller name' will be output as 'controller-name' Facility: SYSGEN, System Generation Utility Explanation: An equivalent name for a controller is entered with the SYSGEN command CONFIGURE. User Action: None. This message is informational.
ERACTED
error activating editor 'editor-name' Facility: MAIL, Mail Utility Explanation: MAIL could not activate the editor specified by your last SET EDITOR command. User Action: Check the validity of your editor specification by using the SHOW EDITOR command. Check with your system manager to make sure the specified editor is available on your system.
ERASEBLKS
blocks reclaimed on relative volume N not completely erased Facility: MOUNT, Mount Utility Explanation: While rebuilding a volume set, some of the blocks being reclaimed could not be erased. User Action: The accompanying message provides additional information.
ERASEFAIL
volume not completely erased Facility: INIT, INITIALIZE Command Explanation: INIT encountered at least one error when it attempted to erase the volume. User Action: The accompanying message provides additional information.
ERBOXPROC
'process-name' Error count = 'nnn' Facility: UETP, User Environment Test Package Explanation: This message assigns a sequence number, 'nnn', to an error found by a particular process. The error is described in a subsequent message. In order to set off the error from other text being printed, a box of asterisks surrounds this message. *********************** * 'program name' * * Error count = 'nn' * *********************** User Action: Take action indicated by the messages that follow.
ERRAT_LIN
error in line 'line-number' at or near 'line-number' Facility: SMG, Screen Management Facility Explanation: This is a general information message included with many termtable compiler messages. This message attempts to identify specifically where an error occurred. User Action: Check the specified line in your definition.
ERRCACHFUL
error cache is full Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) describing the conditions leading to the error. In the SPR, include a listing of the BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ERRCREKBD
unable to create virtual input device Facility: LAT, LAT Facility Explanation: LATCP cannot create a virtual input device for keyboard commands. An accompanying message explains why the virtual input device cannot be created. User Action: Correct the situation based on the information in the accompanying message.
ERRCVTFIL
error returning input filename from DCL Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR CONVERT command. The input file specification could not be obtained. Examine the accompanying message for more information. User Action: Correct the input file specification and reenter your command.
ERRCVTOPN
error opening input file for conversion Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR CONVERT command. The specified input file could not be opened. User Action: This error may occur if the specified input file is incorrect or inaccessible. Correct the input file specification and reenter your command.
ERREXECOM
EXECUTE subcommand is not allowed in execute command file Facility: MONITOR, Monitor Utility Explanation: A MONITOR EXECUTE command is encountered in a MONITOR command file. Any Monitor Utility command may appear in a MONITOR command file except the EXECUTE command. User Action: Remove the EXECUTE command from the command file, and reenter the original request.
ERREXEFIL
error returning execute command filename from DCL Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR EXECUTE command. The MONITOR command file specification could not be obtained. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and rerun the MONITOR EXECUTE command.
ERREXEOPN
error opening execute command file Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR EXECUTE command. The MONITOR command file could not be opened. User Action: This error can occur if the command file specification is incorrect, or if the file is inaccessible. Correct the file specification and then reenter the MONITOR EXECUTE command.
ERREXEREA
error reading execute command file Facility: MONITOR, Monitor Utility Explanation: An error occurred while reading a MONITOR command file. User Action: Reenter the MONITOR EXECUTE command. If the error reoccurs, check the command file.
ERREXEREP
error replacing "@" with "EXECUTE" Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR command file. An attempt to translate the string "@" to "EXECUTE" failed. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and reexecute the command file. Most such messages represent status values returned to MONITOR from the Run-Time Library string manipulation procedures.
ERRFREDYN
error freeing dynamic string when returned to LIB$FREE_VM Facility: STR, String Manipulation Facility Explanation: Unable to free space allocated to the string; this usually occurs when a dynamic string descriptor points to static storage. User Action: Begin debugging procedures to verify and correct the problem.
ERRHALT
halt with error interrupt pending Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ERRINPFIL
error processing /INPUT file Facility: MONITOR, Monitor Utility Explanation: An error occurred while referencing the input recording file. To obtain more information, examine the accompanying linked messages. User Action: Correct the error indicated by the linked messages and rerun the MONITOR command.
ERRLIN
error in line 'line-number' Facility: SMG, Screen Management Facility Explanation: This is a general informational message included with many termtable compiler messages. This message attempts to identify specifically which line contained an error. User Action: Check the specified line in your definition.
ERROR
error reading parameter file Facility: SYSGEN, System Generation Utility Explanation: An irrecoverable I/O error occurred while SYSGEN was reading a parameter file. User Action: Reenter the command. Error in command Facility: EDT, EDT Editor Explanation: The command entered is invalid User Action: Enter a valid command. Error in command option Facility: EDT, EDT Editor Explanation: The command entered included a /NAME qualifier where name is not a valid option. User Action: Reenter the command without specifying /NAME as a qualifier. Error in range specification Facility: EDT, EDT Editor Explanation: The command requires a complete range specification. User Action: Reenter the command including a complete range specification. Error opening terminal for input Facility: EDT, EDT Editor Explanation: EDT could not access the specified terminal for input. This message appears when you are using EDT from a running program. User Action: After determining why EDT cannot access the specified terminal, correct the problem. Error opening terminal for output Facility: EDT, EDT Editor Explanation: EDT could not access the specified terminal for output. This message appears when you are using EDT from a running program. User Action: After determining why EDT cannot access the specified terminal, correct the problem. Error reading from input file Facility: EDT, EDT Editor Explanation: EDT cannot read an input file when it started the editing session. The problem file could be the main input file, the journal file if you are using the /RECOVER specifier, or the startup command file if you are using one. User Action: Determine why the input file cannot be read. Error reading from terminal Facility: EDT, EDT Editor Explanation: EDT cannot process the input it is receiving from the terminal. The message appears when you are using EDT from a running program. User Action: After determining why EDT cannot process input from the specified terminal, correct the problem. Error reporting suppressed, memory dump continuing Facility: BUGCHECK, System Bugcheck Explanation: This message indicates that too many errors occurred while writing a dump to the disk; it is no longer appropriate to continue to send messages for each error, and error reporting is suppressed. The system continues to attempt to write the dump. User Action: When the system reboots, copy the dump to another file. You can determine the text associated with the hexadecimal statuses of previous messages by using the F$MESSAGE lexical function or its equivalent. If the status indicates a possible disk problem, see the user action for the accompanying message.
ERROR
unable to initialize disk boot driver Facility: VAXCLUSTER, VAXcluster Facility Explanation: This is a catchall error in the bootstrap. User Action: Check for communication and hardware failures. Error writing 'nn' block(s), starting at vbn 'vv' - status = 'ss' Facility: BUGCHECK, System Bugcheck Explanation: An error occurred while writing a dump to the disk. The status is the error returned by the QIO$ system service that attempted the write operation. The system continues to attempt to write the dump. User Action: When the VMS operating system reboots, copy the dump to another file. You can determine the text associated with the hexadecimal status by using the F$MESSAGE lexical function or its equivalent. If the status indicates a possible disk problem, see the user action for the accompanying message. Error writing to output file Facility: EDT, EDT Editor Explanation: EDT cannot produce an output file. The problem file could be the MAIN buffer copy, the journal file, or a file requested with the WRITE command. User Action: After determining why EDT cannot produce an output file, correct the problem.
ERROR_HALT
failed to load MSCP server Facility: STACONFIG, Standalone Configure Process Explanation: The call to load the MSCP server from STACONFIG_MSCP failed. Most likely there is not enough nonpaged memory available to allocate the server data structures and local buffer area. User Action: Check the values in the sysgen parameter NPAGDYN to ensure the amount of nonpaged memory allocated to the system is reasonable. Also check MSCP_BUFFER to make sure that value is not too large compared to the value in NPAGDYN.
ERRORISUE
completed with errors Facility: LINK, Linker Utility Explanation: The link completed, but errors were detected. User Action: Correct the errors and relink.
ERRORS
compilation errors in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module contains compilation errors. User Action: Correct the source code, then recompile or reassemble.
ERROUTOPN
error opening conversion file for output Facility: MONITOR, Monitor Utility Explanation: An error occurred during processing of a MONITOR CONVERT command. The specified output file could not be opened. User Action: This error may occur if the output file specification is incorrect. Correct the output file specification and reenter your command.
ERRPARSE
error parsing command Facility: MONITOR, Monitor Utility Explanation: An error is detected while parsing a Monitor Utility command. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and reenter the command. To obtain the correct syntax for utility commands, enter the HELP command in response to the MONITOR> prompt.
ERRPHOTRA
phonemic transcription error is detected Facility: DTK, DECtalk Facility Explanation: A phonemic transcription malfunction occurred after DECtalk device was turned on. User Action: Check the DECtalk hardware.
ERRPROMPT
error prompting for input Facility: MONITOR, Monitor Utility Explanation: An error is detected while prompting the terminal for input. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and reenter the command.
ERRRECFIL
error processing /RECORD file Facility: MONITOR, Monitor Utility Explanation: An error occurred while referencing the output recording file. To obtain more information, examine the accompanying linked messages. User Action: Correct the error indicated by the linked messages and rerun the MONITOR command.
ERRROUCAL
error in the routine call Facility: LIB, Library Facility Explanation: One or more errors were detected during a call to LIB$DELETE_FILE or LIB$RENAME_FILE, but a user-specified error routine is called to handle the conditions. This is an alternate success status. User Action: None.
ERRSYMACTIVE
special error symbol already active Facility: VAXTPU, VAX Text Processing Utility Explanation: The special error symbol can only be set once, and it has already been set. User Action: Be sure you are the first to set the special error symbol.
ERRSYSINFO
failed to collect system information on node 'node-name' Facility: MONITOR, Monitor Utility Explanation: The Monitor Utility encountered a problem when it attempted to collect system-specific information from the remote node. This is generally a network problem. User Action: Check to make sure that DECnet is up and running on the remote node. Reenter the MONITOR request.
ERRTSTMOD
error obtaining test mode name Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. User Action: Submit a Software Performance Report.
ERRVIRDPY
unable to create virtual output device Facility: LAT, LAT Facility Explanation: LATCP cannot create a virtual output device to display data. An accompanying mesage explains why the virtual output device cannot be created. User Action: Correct the situation based on the information in the accompanying message.
ESA
invalid expanded string address Facility: RMS, VMS Record Management Services Explanation: The expanded string area address in the VMS RMS NAM block is invalid; or the address is in an area of memory that cannot be read or written by the caller, as required; or the expanded string buffer contains an invalid file specification. User Action: Verify that the call to the VMS RMS service is coded correctly. Check the logical name translation.
ESCAPE
escape sequence detected Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont format routine indicating an escape sequence has been detected. User Action: None.
ESL
invalid expanded string length Facility: RMS, VMS Record Management Services Explanation: The expanded string length field in the VMS RMS NAM block contains a value of zero; the attempted operation requires the expanded string. User Action: Verify that the call to the VMS RMS service is coded correctly.
ESS
expanded string area too small Facility: RMS, VMS Record Management Services Explanation: The user buffer provided to receive an expanded file specification string is too short; the string does not fit. User Action: Verify that the call to the VMS RMS service is coded correctly.
ESTABCON
establishing connection to remote nodes . . . Facility: MONITOR, Monitor Utility Explanation: Connections to one or more remote nodes are being made. Connections to remote nodes are made when the /NODE qualifier is used or when the CLUSTER class is requested. All connections to remote nodes are made before data collection is initiated. User Action: None.
EVENT_OCCURRED
event XL occurred with param Facility: PPL, Parallel Processing Facility Explanation: This code indicates the occurrence of an event for which notification has been requested by the user. User Action: Since the application requested this notification, response is application-dependent.
EVL
too many variables: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The maximum of 20 variables has been exceeded with the inclusion of the specified .VARIABLE or conditional command (.IF, .IFNOT, .ENDIF, or .ELSE); the command in error has been ignored. User Action: Reduce the number of variables.
EVTSIZ
an event is too large to translate to DNA form Facility: EVL, Event Logger Explanation: A raw event is too large to format properly into DECnet standard form. Therefore, it is discarded. This is probably caused by a network software problem. User Action: Submit a Software Performance Report (SPR).
EXARANGE
invalid range of addresses Facility: PATCH, Patch Utility Explanation: The range of addresses specified is in the wrong order. The higher address preceded the lower address. User Action: Retry using the following format: lower-boundary-address:upper-boundary-address
EXASTLM
exceeded AST quota Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: An image could not continue executing or a command could not execute because the process exceeded its AST quota. User Action: If your program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXBIOLM
exceeded buffered I/O quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue to create a subprocess because the process exceeded its buffered I/O quota. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXBYTLM
exceeded byte count quota Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: The requested operation failed because the process's byte count quota is not large enough. This can occur if excessive concurrent buffered I/O is outstanding, if a large number of mailboxes is created, or if a large number of windows needs to be created to completely map a file. Failure on window creation can occur on a $CRMPSC system service call, the DCL command RUN, or an Access or Create of a file. In this case, this message indicates that the specified file is very fragmented or the process's byte limit quota should be increased. Failure can also occur on a disk read or write operation indicating that a prior extend operation on the file has caused it to become very fragmented. User Action: Compress the file by copying the volume with BACKUP, or ask the system manager to increase the BYTELIM quota.
EXCCOP
exception raised; VMS condition code follows Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: An exception has been raised by the EXC_HANDLING.H package, which provides portable exceptions for the C language. The accompanying VMS condition code identifies the error. User Action: See the documentation for the software that your program is calling to determine the reason for this exception. Correct the problem or use the EXC_HANDLING.H package to provide an exception handler.
EXCEPTION
exception raised; address of exception object: 'object-address' Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: An exception has been raised by the EXC_HANDLING.H package, which provides portable exceptions for the C language. User Action: See the documentation for the software that your program is calling to determine the reason for this exception. Correct the problem or use the EXC_HANDLING.H package to provide an exception handler.
EXCPSC
more than 65535 psects defined in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module defines more than 65535 psects. User Action: Reduce the number of psects in the module and relink.
EXCPTSTER
error testing VAX Vector Exceptions Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
EXCPUTIM
CPU time limit expired Facility: SYSTEM, VMS System Services Explanation: The user's CPU time limit has expired. User Action: Request that a larger CPU time quota be assigned from the system manager and retry the operation.
EXDEPTH
exceeded allowed depth Facility: SYSTEM, VMS System Services Explanation: Either a programming error has occurred or the resource name tree does not have enough depth. The lock management services allow a certain depth to the resource name tree that is a function of the interrupt stack size. If the resource name tree requires more levels, the size of the interrupt stack must be increased. User Action: Either correct the programming error or increase the size of the interrupt stack by increasing the SYSGEN parameter INTSTKPAGES.
EXDIOLM
exceeded direct I/O quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue executing or a command could not execute because the process exceeded its direct I/O quota. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXDISKQUOTA
disk quota exceeded Facility: SYSTEM, VMS System Services Explanation: The disk quota has been exceeded while attempting to create or extend a file. User Action: Reduce disk usage by deleting files or have the system manager increase the quota.
EXEABO
executor characteristics not defined Facility: NCP, Network Control Program Explanation: There is no executor node defined on the local node from which the NCP command COPY is entered. User Action: None. This error will not affect the operation of the COPY command.
EXECUTEFAIL
execution aborted Facility: VAXTPU, VAX Text Processing Utility Explanation: Your program is terminated prematurely because of an error. User Action: Correct the error in your program and reexecute it.
EXECUTING
job executing on queue prevents requested operation Facility: JBC, Job Controller Explanation: The parameters of the specified job cannot be modified because the job is currently executing. Or, the specified queue cannot be deleted because there is a job executing from the queue. User Action: Reenter the request after the job has completed execution.
EXENQLM
exceeded enqueue quota Facility: SYSTEM, VMS System Services and RMS, VMS Record Management Services Explanation: You exceeded your ENQLM quota. Since the ENQUEUE quota is shared by a process and all its subprocesses, any of these processes could have used the entire quota. Also, the higher the SYSGEN parameter RMS_DFMBFSUR, the higher the UAF parameter ENQLM must be. User Action: Either increase the ENQLM quota for your account, log out and then log in again, and retry the operation; or modify the program to release locks (RMS record locks or other uses of the $ENQ system service), which may no longer be required.
EXFILLM
exceeded open file quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue executing or a command could not execute because the process exceeded its open file quota. Since the FILLM quota is shared by a process and all its subprocesses, any one of these processes could have used the entire quota. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXGBLPAGFIL
exceeded global page file limit Facility: SYSTEM, VMS System Services Explanation: The attempt to allocate a global section with page file backing store failed because the systemwide limit on these pages is exceeded. No part of the section is allocated. User Action: Delete some similar sections or ask the system manager to increase the SYSGEN parameter GBLPAGFIL. Then, try the operation again.
EXHFUL
file extension header has no room Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
EXHNEVCAL
process exit handler was not called Facility: PPL, Parallel Processing Facility Explanation: An application stopped without executing its PPL$ exit handler. User Action: The application may require an application-specific recovery procedure.
EXISTENCE
object referenced does not currently exist Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A DECthreads routine has been requested to operate on an object that does not exist. User Action: Consult the documentation for the DECthreads routine that issued this message to determine the conditions that caused it. Also check the program where the call is issued to determine which object or objects being passed as parameters do not currently exist.
EXISTS
'filespec' already exists Facility: Shared by several facilities Explanation: The directory specified in the DCL command CREATE/DIR already exists. This message is informational. User Action: None.
EXISTS
known file entry for a version of this file already exists Facility: INSTALL, Install Utility Explanation: A known file entry already exists for this file name on the specified device and directory. User Action: Contact your system manager.
EXITFAIL
attempt to EXIT is unsuccessful Facility: VAXTPU, VAX Text Processing Utility Explanation: An error occurred during execution of the built-in procedure EXIT; the procedure did not complete successfully. This usually occurs because the EXIT procedure could not write the modified buffers. This message should be accompanied by a message specifying the reason why the EXIT procedure failed. User Action: Take corrective action according to the reason for the EXIT failure; for example, if there is insufficient disk space to create the modified version of the output file, purge some files to free space on the disk.
EXITING
editor exiting Facility: VAXTPU, VAX Text Processing Utility Explanation: Your program exited from the VAXTPU image. User Action: None.
EXITSTATUS
is 'AS' Facility: PPL, Parallel Processing Facility Explanation: An application participant exited with this status code. User Action: Determine the cause of the termination by examining the status code.
EXIT_THREAD
current thread has been requested to exit Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The cma_exit_thread routine has been called to force the thread to shut down in an orderly fashion. This message notifies all active exception handlers to perform any necessary cleanup activities. User Action: None.
EXLNMQUOTA
exceeded the job logical name table Facility: LOGIN, Login Processor Explanation: The job logical name table is full. You cannot make further job logical name assignments. User Action: Deassign logical names you no longer need to free space in the table. If you have sufficient privilege to modify the user authorization file, you can increase the size of the logical name table with the AUTHORIZE command MODIFY. The format of the command is: AUTHORIZE MODIFY username/JTQUOTA=n The variable n is the size of the job logical name table in bytes. The default for the job logical name table size is 1024 bytes. The new value takes effect the next time you log in. For a detached process, increase the SYSGEN parameter PQL_ DJTQUOTA.
EXP
file expiration date not yet reached Facility: RMS, VMS Record Management Services Explanation: A call to a VMS RMS service attempted to overwrite a magnetic tape file that is not expired. User Action: If the file can be overwritten, remount the volume with the /OVERRIDE=EXPIRATION qualifier. (You must be the owner of the volume or have the VOLPRO privilege to override the expiration date.) Otherwise, use another volume.
EXPAGQUO
exceeded pagefile quota Facility: LINK, Linker Utility Explanation: The linker could not expand its virtual address space sufficiently due to inadequate pagefile quota. Since the PGFLQUOTA is shared by a process and all its subprocesses, any one of these processes could have used all the quota. User Action: If the link fails consistently because of insufficient quotas, contact your system manager and request that your quota be increased.
EXPANDPHD
expand process header error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
EXPCOMPLEX
expression too complex Facility: VAXTPU, VAX Text Processing Utility Explanation: The expression is too complex. User Action: Break up the expression into simpler expressions.
EXPECTED
one of the following symbols is expected: Facility: VAXTPU, VAX Text Processing Utility Explanation: You have a syntax error in your program. One of the symbols listed is expected but not found. User Action: Correct the syntax error and recompile your program.
EXPGFLQUOTA
exceeded pagefile quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue executing or a command could not execute because the process exceeded its pagefile quota. Since the PGFLQUOTA is shared by a process and all its subprocesses, any one of these processes could have used the entire quota. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXPIRED
this product has expired after VMS Version nnn. Please contact your local Digital sales representative. Facility: VMSINSTAL, Install Procedures Explanation: The product cannot be installed on the current version of the VMS operating system. The product has been restricted to versions lower than the version specified in the message. User Action: Contact your local Digital sales representative.
EXPORTQUOTA
port's quota exceeded Facility: SYSTEM, VMS System Services Explanation: The quota permitted by processes on this port of a multiport (shared) memory has been exceeded. User Action: Wait until other processes release the required resource, or reboot VMS and reconnect shared memory specifying a larger quota.
EXPOVR32
expression overflowed 32 bits Facility: MACRO, VAX MACRO Assembler Explanation: The value of the expression could not be stored in a longword (32 bits). The assembler truncated the value to 32 bits. User Action: Change the values in the expression.
EXPRCLM
exceeded subprocess quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue executing or a command could not execute because the process exceeded its subprocess limit. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXPREG
error code of 'xx' expanding program region Facility: PATCH, Patch Utility Explanation: The system service $EXPREG request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry.
EXPSHRPAT
attempt to expand patch area for shareable image Facility: PATCH, Patch Utility Explanation: The patch area cannot be created for shareable images. User Action: Relink the shareable image instead of patching it.
EXPSTKOVR
expression too nested, stack overflow Facility: PATCH, Patch Utility Explanation: You attempted to evaluate an expression that contained more than 16 levels of nested arguments. User Action: Remove levels of nested arguments until you have 16 levels or less and retry the operation.
EXPSYN
invalid expression syntax - check operators and operands
Facility: CLI, Command Language Interpreter (DCL)
Explanation: An arithmetic expression in a DCL command is not
syntactically correct; the command interpreter cannot analyze the
expression. An invalid expression can occur as a result of:
o Missing operators between values or symbol names
o Unmatched parentheses
o Undefined symbol names that are being interpreted as character
string data
User Action: Examine the expression for any of the errors listed
previously. Correct the expression and reenter the command.
EXPTOOCOM
expression is too complex Facility: SMG, Screen Management Facility Explanation: The expression is too complex for the termtable compiler to parse. User Action: Modify the expression so that it is less complex.
EXPVIR
error allocating virtual memory Facility: FDL, Create/FDL Utility Explanation: This message will be accompanied by a system error message that explains the error. User Action: Correct the error described in the system error message and try again.
EXQUOTA
exceeded quota Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: An image could not continue executing or a command could not execute because the process exceeded one of its resource quotas or limits. If this message is associated with a status code returned by a request to a DR32 interface, a DR11-W interface, or an LPA11-K driver, the AST quota for the requesting process is exceeded. In the latter case, an AST cannot be queued for a buffer full/empty AST. Normally, a start data transfer request can require no more than three AST blocks at a time. If this message is associated with a vector disabled (VECDIS) status code, the process's paging file quota prohibits the allocation of sufficient process memory for storing its mainline vector state. If this message is associated with a status code returned by a request to a DUP11 interface, a request cannot be queued because the buffered I/O quota is exceeded. This message can indicate failure to create a subprocess because deductible quotas, when subtracted from the current quotas of the creator, would not leave the minimum required quotas for the creator. This message may also occur if the size of a buffered I/O request exceeds the value of the SYSGEN parameter MAXBUF. User Action: Use the DCL command SHOW PROCESS/QUOTAS to determine the current quotas and to determine which quota is exceeded. Determine whether any subprocesses are hibernating and are no longer performing useful functions; delete any such subprocesses. If a program fails consistently because of insufficient quotas, contact the system manager and request that the quotas be increased.
EXT
ACP file extend failed Facility: RMS, VMS Record Management Services Explanation: The requested extension of a file cannot be performed. This message is associated with a status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
EXTBIT
illegal extract bit number - greater than 31 Facility: PATCH, Patch Utility Explanation: You specified an illegal bit number; legal bit numbers range from 0 to 31 inclusive. User Action: Retry the operation specifying a legal bit number.
EXTCACHIV
contents of extent cache is garbage Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
EXTEND
unable to extend work file for needed space Facility: SORT, Sort/Merge Utility Explanation: SORT failed to extend your temporary work file. Either the device is full or you have reached your disk quota limit. User Action: Reassign work files to a different device with more space or have the system manager extend your quota.
EXTENDED
'filespec' extended Facility: SYSGEN, System Generation Utility Explanation: This informational message is the result of the SYSGEN command CREATE and indicates that the specified file has been extended. User Action: No action is required.
EXT_ERR
error in RMS Extension; reason code %Xnnnnnnnn Facility: RMS, VMS Record Management Services Explanation: An RMS extension discovered an error in processing a file. This most likely indicates inconsistent data in the file, but may indicate that the file has an incorrect STORED_SEMANTICS attribute. The reason code is a VMS status code provided by the RMS extension. User Action: Use the DIRECTORY/FULL command to check the semantics of the file being accessed. It may be necessary to manually alter the file's semantics attribute using the SET FILE command. Verify that the internal structure of the data file is valid.
EXTN_ERR
unable to extend output file Facility: CONVERT, Convert Utility Explanation: The size of the input file exceeded the initial allocation of the output file, and when CONVERT tried to extend the file, an error occurred. This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error described in the RMS error message and try again.
EXTNOTFOU
RMS Extension not found Facility: RMS, VMS Record Management Services Explanation: The semantics of the file being accessed did not match the semantics of the attempted access, and no RMS extension could be located which could perform the conversion. User Action: Use the DIRECTORY/FULL command to check the semantics of the file being accessed.
EXTNOTFOUND
extension 'extension-name' not found Facility: VAXTPU, VAX Text Processing Utility Explanation: The named extension to VAXTPU cannot be located. User Action: Install the named extension before trying to use it.
EXTQELM
exceeded timer queue entry quota Facility: SYSTEM, VMS System Services Explanation: An image could not continue executing or a command could not execute because the process exceeded its timer queue entry quota. Since the TQELM quota is shared by a process and all its subprocesses, any one of the processes could have used all the quota. User Action: If a program fails consistently because of insufficient quotas, contact your system manager and request that your quotas be increased.
EXTRACTED
module 'module-name' extracted from 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This success message is generated by the DCL command LIBRARY. User Action: None.
EXTRAENDM
extraneous .ENDM in 'library-filespec' Facility: LIBRAR, LIBRARY Command Explanation: This warning message is generated by the DCL command LIBRARY. The specified library contains a .ENDM line that does not terminate any macro. User Action: Reformat the macro source file.
EXTRANEOUSARGS
one or more extraneous arguments specified Facility: VAXTPU, VAX Text Processing Utility Explanation: You have specified one or more extraneous arguments for this DECwindows call. User Action: Specify only acceptable arguments.
EXTRAPARM
superfluous parameter detected Facility: AUTHORIZE, Authorize Utility Explanation: You have specified too many parameters in the command line. The extra parameter is identified in the message. User Action: Reenter your command without the excess parameter.
FAB
file aborted Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR has aborted the file for internal reasons. This is a DSR internal error. User Action: Submit a Software Performance Report (SPR).
FAB
invalid FAB or FAB not accessible Facility: RMS, VMS Record Management Services Explanation: Either the specified VMS RMS block identifier field does not indicate that the field is a FAB, or the FAB is not in a portion of memory that can be written to by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly. An attempt may have been made to perform file operations with a RAB. Verify that the FAB is properly initialized and that the block identifier field is not overwritten during execution of the program image.
FAC
record operation not permitted by specified file access (FAC) Facility: RMS, VMS Record Management Services Explanation: A record operation is attempted that is not indicated in the file access field of the FAB for the file. For example, to delete a record, the DEL option must have been specified in the FAC field when the file is opened or created. If the error results from the DCL command READ or WRITE, this message indicates either the DCL command WRITE is entered for a file opened for reading, or the DCL command READ is entered for a file opened for writing. User Action: If the error occurred during execution of an image, verify that the FAC parameter in the FAB indicates the requested type of access. If the error occurred during use of the DCL commands, verify that the correct qualifier is specified when the DCL command OPEN is entered to open the file.
FACOVFL
facility table overflow in section - please submit SPR Facility: MESSAGE, Message Utility Explanation: An internal error in the compiler is detected. User Action: Submit a Software Performance Report (SPR).
FACTBAD
cannot read factory bad block data Facility: INIT, INITIALIZE Command and BACKUP, Backup Utility Explanation: Either the DCL command INITIALIZE or the Backup Utility encountered an error during an attempt to read the bad block data recorded on the specified volume. An accompanying message provides additional information. User Action: Either correct the condition that caused the error and reenter the command or notify the system manager. If the volume is under warranty, it should be returned to the factory. Contact the Digital Services Group if necessary.
FACTOOLONG
facility name, 'name', exceeds maximum length 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: The facility name you want to use is longer than the maximum allowed length. User Action: Use a shorter facility name.
FAIL
failed to 'execute-verb' entry for 'filespec' Facility: INSTALL, Install Utility Explanation: A failure to ADD, CREATE, DELETE, REMOVE, or REPLACE a known file entry occurred. An accompanying error message explains the failure. User Action: Correct the situation indicated by the accompanying error message and reenter the command.
FAILED
failed to perform 'execute-verb' operation Facility: INSTALL, Install Utility Explanation: A PURGE or listing operation failed to execute completely. An accompanying message explains the failure. User Action: Correct the situation indicated by the accompanying error message and reenter the command. Failed to Locate Port Micro-code Image Facility: VAXport, VAXport Driver Explanation: The port driver will not start the port. User Action: Make sure that the console load media is present in the console drive, and reboot the system.
FAILFREVM
failed to deallocate 'number' bytes of virtual memory Facility: CNF, NI Configurator Explanation: An error occurred when NICONFIG attempted to deallocate virtual memory. User Action: Check the accompanying error message to determine whether the virtual address space is exceeded, or whether a program error is uncovered. An invalid address or size for deallocation indicates a programming error.
FAILGETVM
failed to allocate 'nn' bytes of virtual memory Facility: INSTALL, Install Utility Explanation: INSTALL failed to allocate sufficient work space for itself. User Action: Either your PGFLQUO value is too low for your account, or the system's VIRTUALPAGECNT SYSGEN parameter is too low. Contact your system manager.
FAILGETVM
failed to allocate 'number' bytes of virtual memory Facility: CNF, NI Configurator Explanation: An error occurred when NICONFIG attempted to allocate virtual memory. User Action: Check the accompanying error message to determine whether the virtual address space is exceeded, or whether a program error is uncovered. An invalid address or size for allocation indicates a programming error.
FAILOVER
attempting failover Facility: LAT, LAT Facility Explanation: A SET HOST/LAT connection to a service has been abnormally lost. SET/HOST LAT is attempting to connect to another node offering the same service. User Action: None.
FAILURE
internal VAXTPU failure detected at PC 'address' Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
FAILURE_STATUS
facility 'name' returned failure status of 'xxxxxxxx' Facility: VAXTPU, VAX Text Processing Utility Explanation: A facility that VAXTPU called returned a failure status. User Action: There is an error in the VAXTPU built-in procedure call which generated the error. Correct the parameters and try again.
FAIOPEFIL
failed to open file 'filename' Facility: SMG, Screen Management Facility Explanation: The termtable compiler could not open the file specified in a REQUIRE statement. User Action: Make sure that the specified file exists and that you have read access to it.
FAO
error formatting report information Facility: BAD, Bad Block Locator Utility Explanation: An error is encountered during an FAO formatting operation. User Action: Copy all pertinent diagnostic message information and submit a Software Performance Report (SPR).
FAOBUG
FAO system service failure Facility: LINK, Linker Utility, CREF, Cross-Reference Utility, LIBRAR, LIBRARY Command Explanation: An error is returned by the $FAO system service. User Action: Submit a Software Performance Report (SPR).
FAOFAIL
FAO failure Facility: CREF, Cross-Reference Utility, and LINK, Linker Utility Explanation: An error is returned by the $FAO system service. User Action: Ensure that the field descriptor FAO control strings are correct.
FAOFAIL
FAO system service failure Facility: LIBRAR, LIBRARY Command Explanation: An unexpected internal consistency check occurred. User Action: Contact your system manager and submit a Software Performance Report (SPR).
FATALERR
fatal error on 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an irrecoverable error during an attempt to read or write the specified save set. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
FATALERR
fatal error reading startup database Facility: STDRV, System Startup Driver Explanation: The startup driver encountered a fatal error while trying to read the startup database files. The startup operation is aborted. If this message occurs during a system reboot, VMS may not have been properly started. User Action: Verify that the startup databases, defined by the logical names STARTUP$STARTUP_VMS, STARTUP$STARTUP_LAYERED, and STARTUP$PHASES, are all available and can be accessed.
FATALERROR
fatal error message issued Facility: LINK, Linker Utility Explanation: The linker issued a fatal error message in the link. User Action: Correct the problem and relink.
FATALEXC
fatal exception encountered Facility: CONVERT, Convert Utility Explanation: This message appears if an exception record is encountered and if you have specified the /EXIT qualifier. User Action: Specify either /TRUNCATE or /PAD, or else specify /NOEXIT.
FATALEXCPT
fatal executive or kernel mode exception Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an unrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
FATERRLIB
fatal error in library Facility: DTK, DECtalk Facility Explanation: An internal error occurred in the DECtalk device. User Action: Submit a Software Performance Report describing the problem.
FATERRLIB
fatal error in library Facility: LIB, Library Facility Explanation: An internal consistency check failed in the VMS Run- Time Library. This usually indicates a programming error in the Run-Time Library. User Action: Submit a Software Performance Report (SPR).
FATERRLIB
fatal error in library Facility: SMG, Screen Management Facility Explanation: An internal error has occurred within the Screen Management Facility. User Action: Submit a Software Performance Report describing the problem.
FATINTERR
fatal internal error in Run-Time Library Facility: OTS, General Purpose Facility, and STR, String Manipulation Facility Explanation: An explicit or implicit call to the VMS Run-Time Library resulted in the failure of an internal consistency check. User Action: Rerun your program. Collect as much information as possible, including the system traceback listing, and submit a Software Performance Report (SPR).
FAU
flag character 'character' already in use Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to define a character as a flag character; however, the character has already been defined. User Action: Use another character as a flag character.
FCPREADERR
file processor read error Facility: SYSTEM, VMS System Services Explanation: An I/O error occurred when file structure data, for example, a directory, is being read. User Action: Examine the error log and correct the hardware problem if necessary.
FCPREPSTN
file processor reposition error Facility: SYSTEM, VMS System Services Explanation: An I/O error occurred during an attempt to reposition a tape volume after it had gone off line. User Action: Examine the error log and correct the hardware problem if necessary.
FCPREWNDERR
file processor rewind error Facility: SYSTEM, VMS System Services Explanation: An I/O error occurred when a volume is being rewound. User Action: Examine the error log and correct the hardware problem if necessary.
FCPSPACERR
file processor space error Facility: SYSTEM, VMS System Services Explanation: An I/O error occurred while spaces were being skipped within a file or files. The operating system does not normally display this message. User Action: Examine the error log and correct the hardware problem if necessary.
FCPWRITERR
file processor write error Facility: SYSTEM, VMS System Services Explanation: An I/O error occurred when file structure data, for example, a directory, is being written. User Action: Examine the error log and correct the hardware problem if necessary.
FDEXNORCV
expected floating divide by zero exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate arithmetic exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FDLERROR
error parsing FDL file Facility: FDL, Edit/FDL Utility Explanation: This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
FDLPAR
error parsing FDL file Facility: FDL, Edit/FDL Utility Explanation: An error occurred during the parsing of the FDL file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message and try again.
FDLPARSE
fatal error encountered parsing FDL file Facility: EXCHNET, EXCHANGE/NETWORK Command Explanation: An error occurred during the parsing of the FDL file supplied by the user. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message and reenter the command.
FEL
'flag-name' flag at end of line ignored Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This flag cannot occur at the end of a line. User Action: Remove the flag from the end of the line.
FEX
file already exists, not superseded Facility: RMS, VMS Record Management Services Explanation: An attempt is made to create or rename a file with the same file specification as an existing file in the volume set. User Action: Choose a different file specification; delete the existing file (if a new one is to be created); or use the SUP option in the FOP parameter in the FAB to request that an existing file be superseded.
FFVSDIVER
error encountered testing f_floating vector-scalar division Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVSMLTER
error encountered testing f_floating vector-scalar multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVSSBTER
error encountered testing f_floating vector-scalar subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVVADDER
error encountered testing f_floating vector-vector addition Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVVDIVER
error encountered testing f_floating vector-vector division Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVVMLTER
error encountered testing f_floating vector-vector multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FFVVSBTER
error encountered testing f_floating vector-vector subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during f_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FIDERROR
unexpected file change in 'filespec' Facility: BACKUP, Backup Utility Explanation: A file boundary marker is missing from the input save set. Data in the save set may be corrupted. It is likely that parts of the specified file and one or more complete files are missing. User Action: Examine the file for corruption and reconstruct as necessary. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility; in this case, submit a Software Performance Report (SPR).
FIDNOTFND
internal error. File to be processed not found on process list Facility: BACKUP, Backup Utility Explanation: The file context has been lost. This is an internal error. User Action: If this error can be reliably reproduced, the BACKUP command used and a description of the circumstances should be submitted along with a Software Performance Report (SPR).
FIDNUM_ZERO
file number zero but not a valid deleted header Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message is issued along with the BADHEADER message and gives a more detailed reason why the specified file header is corrupt. In this case, the file number field in the file header (FH1$W_FID_NUM or FH2$W_FID_NUM) is zero, indicating that this is a deleted header, but the other fields of the file header do not have the values that a deleted file header should have. User Action: None. See the BADHEADER message.
FIELDLIM
number of fields in range exceeds limit Facility: NCP, Network Control Program Explanation: The channel list supplied in the command is invalid. Channel lists may have eight fields, separated by commas. The last field cannot be a hyphenated range. User Action: Correct the channel list.
FIL11_NOREC
ignoring /RECORD_FORMAT for Files-11 output Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility does not support the /RECORD_ FORMAT option on Files-11 output files. User Action: Leave the qualifier off. If the output file is not in the desired format, use the VMS CONVERT utility to change the format of the file.
FILACCERR
magnetic tape file access is nonblank Facility: SYSTEM, VMS System Services Explanation: The accessibility characteristic in the HDR1 label is not blank and the file cannot be accessed without overriding the field. User Action: Mount the magnetic tape with the /OVERRIDE=ACCESSIBILITY qualifier. (The VOLPRO privilege is required or you must be the owner of the tape.) Otherwise, use another volume.
FILADDED
added component file to phase Facility: SYSMAN, Cluster System Management Utility Explanation: The named startup component file is added to the named phase. User Action: Verify that the listed file name and phase are correct.
FILALRACC
file already accessed on channel Facility: SYSTEM, VMS System Services Explanation: The request failed because the channel over which the $QIO IO$_ACCESS request is issued already had either a file or logical link accessed on it. User Action: Check for a programming error.
FILAREDIF
files are different Facility: DIFF, DIFFERENCES Command Explanation: The two files being compared are different. This is an informational message. User Action: None.
FILCNTNONZ
open file count nonzero after process rundown Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an unrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
FILDISABL
component file updated Facility: SYSMAN, Cluster System Management Utility Explanation: The named startup component file is disabled on the specified node. User Action: Verify that the listed file name is correct.
FILE_ABSENT
log file not found - /NEW_VERSION not required Facility: LMCP, Log Manager Control Program Explanation: An attempt was made using the /NEW_VERSION qualifier to create a new log file that does not currently exist. User Action: To continue with the operation, do not specify the /NEW_VERSION qualifier in the command line. File attributes error Facility: EDT, EDT Editor Explanation: The file cannot be edited by EDT because of its attributes. User Action: None. The file cannot be edited.
FILE_EMPTY
log file contains no valid record data Facility: LMCP, Log Manager Control Program Explanation: An attempt was made to dump or show file usage of a log file that contained no valid records. User Action: None.
FILE_EXISTS
log file already exists - current file not superseded Facility: LMCP, Log Manager Control Program Explanation: The log file name specified already exists. This log may contain information about currently active transactions that will be lost on reboot or failover if a new log file is created. User Action: To continue with the operation, specify the /NEW_ VERSION qualifier in the command line. If you specify /NEW_ VERSION, a new log file will be created. File specification required Facility: EDT, EDT Editor Explanation: You did not specify a file name (or file specification) with an INCLUDE, PRINT, or WRITE command. User Action: Reenter the command including the correct file specification.
FILEACC
error accessing system authorization file Facility: LOGIN, Login Processor Explanation: An error occurred while attempting to access the authorization file. An accompanying message will provide more information. User Action: Correct the problem described by the accompanying message, and try again.
FILECONVERTED
file format is being converted to a supported type Facility: VAXTPU, VAX Text Processing Utility Explanation: The buffer being written is created from a file that had nonstandard attributes. The output file being created does not have the attributes of the input file; it is created with standard attributes (VARIABLE with CR record attributes). User Action: None.
FILEGONE
startup component database is missing Facility: SMI, System Management Integrator/Server Explanation: The current startup component database does not exist, or you do not have read or write access to this database. User Action: To create a new database, use the STARTUP CREATE command at the SYSMAN> prompt. To select a different component database, use the STARTUP SET DATABASE command at the SYSMAN> prompt. If the database exists, but you cannot access it, verify the protection applied to the file (using the DIRECTORY/FULL command), and change the protection if necessary (using the SET PROTECTION command). If you cannot change the protection, ask the system manager or the owner of the file to change the protection.
FILEIN
'count' lines read from file 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU opened the named file and read the indicated number of lines from that file into a buffer. User Action: None.
FILEIO
file I/O error 'filename' Facility: NCP, Network Control Program Explanation: An error occurred during file input or output; for example, a system image file could not be read. An accompanying VMS RMS message should identify the reason for the error (such as a protection violation if the file is protected against read access). User Action: Take corrective action based on the VMS RMS message.
FILELOCKED
file is deaccess locked Facility: SYSTEM, VMS System Services Explanation: The program attempted to access a locked file. A file becomes locked when it is accessed with FIB$M_DLOCK (bit) set and then deaccessed without writing attributes. User Action: Unlock the file with the DCL command UNLOCK and examine it for inconsistency.
FILEMPTY
file 'filename' has no folders Facility: MAIL, Mail Utility Explanation: A DIR/FOLDER command is entered, but the current mail file has no folders and, therefore, no messages. User Action: None.
FILENABL
component 'filename' updated Facility: SYSMAN, Cluster System Management Utility Explanation: The named startup component file is enabled on the specified node. User Action: Verify that the listed file name is correct.
FILENOTFOUND
unable to locate file 'filename' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not find the listed input file. User Action: Check the command for a misspelling error, or reenter the command specifying the correct location for the input files.
FILENUMCHK
file identification number check Facility: SYSTEM, VMS System Services Explanation: The volume index file may be corrupted. The file number in the file header that is read is invalid. The disk's file structure is damaged. User Action: Repair the volume using the Analyze/Disk_Structure Utility.
FILEOUT
'count' lines written to file 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU wrote the indicated number of lines from a buffer into the named file. User Action: None.
FILEPURGED
oldest file version purged Facility: SYSTEM, VMS System Services Explanation: The newly created file version exceeded the maximum number of versions of that file; the oldest file version is deleted. This message is informational. User Action: None.
FILESEQCHK
file identification sequence number check Facility: SYSTEM, VMS System Services Explanation: The file sequence number in the file header is not the one expected. A directory entry points to a file that is deleted. User Action: Remove the directory entry with the following command line: DELETE filespec
FILESTRUCT
unsupported file structure level Facility: SYSTEM, VMS System Services Explanation: The file structure on the accessed volume is not compatible with the ACP, or the file structure may be corrupt. User Action: Verify that the correct physical volume is mounted. Or repair the volume using the Analyze/Disk_Structure Utility. If the volume is new and does not contain data, use the DCL command INITIALIZE to initialize the volume in the correct format.
FILETOOLONG
file only partially installed Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN command INSTALL failed. The /SIZE qualifier specified with the SYSGEN command CREATE is larger than the maximum allowed. User Action: Specify a smaller /SIZE qualifier with the CREATE command.
FILLIM
exceeded open file limit Facility: CONVERT, Convert Utility Explanation: SORT exceeded the process open file limit. User Action: Increase the FILLM parameter in the user authorization record.
FILMODIFD
component 'filename' modified Facility: SYSMAN, Cluster System Management Utility Explanation: The named startup component file is modified as directed by user. User Action: Verify that the listed file name is correct.
FILNOPOST
file will not be subject to date-recording or deletion Facility: BACKUP, Backup Utility Explanation: This is a warning message indicating that BACKUP will not post-process the file because its contents were not successfully verified. User Action: Determine why the file could not be successfully verified and retry the BACKUP operation.
FILNOTACC
file not accessed on channel Facility: SYSTEM, VMS System Services Explanation: The process is trying to read or write to a channel that does not have a file accessed on it. User Action: Modify the source program to correct the problem.
FILNOTCNTG
file is not contiguous as required Facility: SYSTEM, VMS System Services Explanation: A system file that must be in contiguous disk format is not contiguous. User Action: Use the DCL command COPY/CONTIGUOUS to make a new contiguous version of the file.
FILNOTDEL
error deleting 'filespec' Facility: Shared by several facilities Explanation: A file could not be deleted. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take appropriate action based on the associated VMS RMS message.
FILNOTEXP
file is not expired Facility: MOUNT, Mount Utility and SYSTEM, VMS System Services Explanation: A tape file cannot be overwritten because it has not reached its expiration date. User Action: To overwrite or delete the file, mount the volume with the /OVERRIDE=EXPIRATION qualifier. You must be the owner of the volume or have volume protection (VOLPRO) privilege.
FILNOTFND
component file not found Facility: SMI, System Management Integrator/Server Explanation: A search for startup component files matching a given search string found no matching entries. User Action: Reenter the command with a different file parameter.
FILNOTPUR
error deleting 'filespec' Facility: Shared by several facilities Explanation: An error is detected during an attempt to delete the specified file. A subsequent message explains the reason for the error. User Action: Take corrective action based on the accompanying message.
FILOPE
file open error, 'name of file' Facility: NCP, Network Control Program Explanation: Your command could not open the specified file. An accompanying VMS RMS message should specify why the file could not be opened; for example, the file could not be found. The 'name of file' identifies the file that could not be opened, for example, the permanent database file. User Action: Take corrective action based on the RMS message. For instance, if a file cannot be found, determine whether it exists and whether it is located in the proper directory.
FILPURGED
'filespec' deleted Facility: Shared by several facilities Explanation: The DCL command PURGE displays the file specification of a file it is deleting. This message is informational. User Action: None.
FILREMOVED
component file removed from phase Facility: SYSMAN, Cluster System Management Utility Explanation: The named startup component file is removed from the specified phase. User Action: Verify that the listed file name is correct.
FILREQD
the /FILENAME qualifier is required with the RMS class Facility: MONITOR, Monitor Utility Explanation: The RMS class requires a file specification for live monitoring. User Action: Reenter the MONITOR command with a file specified with the /FILENAME qualifier.
FILTOOLON
file specification is too long (over 255 characters) Facility: DTK, DECtalk Facility Explanation: The file specification is too long. User Action: Correct your program so that it requests a file name of 255 characters or fewer.
FILTRNERR
input RMS file name is not unique across the CLUSTER Facility: MONITOR, Monitor Utility Explanation: A single file name specified with the /FILENAME qualifier for the RMS class translated to a different file on one or more requested nodes. A single file specification must locate the same file on all nodes requested. User Action: Reenter the MONITOR command with a file specification which is unique across the cluster.
FINDHOME
no valid home block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The utility could not locate a valid home block on the specified relative volume. User Action: If the volume can no longer be mounted by the operating system, it is corrupted and must be reconstructed from backup media. If the volume can be mounted, this message indicates a software error in the Analyze/Disk_Structure Utility. In this case, submit a Software Performance Report (SPR).
FINDIHD
no valid index file header, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: Both the primary and alternate index file headers are corrupted. User Action: If the volume can no longer be mounted by the operating system, it is corrupted and must be reconstructed from backup media. If the volume can be mounted, this message indicates a software error in the Analyze/Disk_Structure Utility. In this case, submit a Software Performance Report (SPR).
FINISHED
task completed Facility: UETP, User Environment Test Package Explanation: A module in the UETP completed, but errors may have occurred during its execution. User Action: None.
FIRSTMOD
first input file being a library requires module extraction Facility: LINK, Linker Utility Explanation: No input files were specified, and the first file is a library file with no explicit module extraction. User Action: Reenter the command, specifying an input file, or use the /INCLUDE qualifier on the library file.
FLAGTRUNC
value of message flags exceeds maximum value 15, truncated Facility: VAXTPU, VAX Text Processing Utility Explanation: The message flags value should be less than or equal to 15. The procedure for writing the messages uses only the low four bits of the value. User Action: Refer to the material on SET (MESSAGE_FLAGS, . . . ) in the VAX Text Processing Utility Manual for the proper values to specify.
FLG
invalid key definition flags for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: Either XAB$V_CHG or XAB$V_NUL is incorrectly specified for the primary key definition XAB, or a reserved key definition flag is specified. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
FLK
file currently locked by another user Facility: RMS, VMS Record Management Services Explanation: An attempt to open or create a file failed. Another user has the file open in a mode incompatible with the attempted access. User Action: Wait until the other user has unlocked the file. If the file is to be shared, verify that the SHR option is selected in the FAB for all users that need to access the file. If the file cannot be shared, modify the program to detect and respond to the condition by waiting.
FLOOVEMAT
floating overflow in math library - user PC location Facility: MTH, Mathematics Facility Explanation: An overflow condition occurred during execution of a math library procedure. This message results from an incorrect call to the math library, and usually indicates that an argument is too small or too large. User Action: Use the traceback information and PC displayed in the message to locate where your program called the math library.
FLOUNDMAT
floating underflow in math library - user PC location Facility: MTH, Mathematics Facility Explanation: An underflow condition occurred during execution of a math library procedure and the caller is enabled for floating underflow traps. This message results from an incorrect call to the math library. Refer to the discussion of the LIB$FLT_UNDER procedure in the VMS Run-Time Library Routines Volume. User Action: Locate the statement in your program where you called the math library causing the underflow condition to occur.
FLOVNORCV
expected floating point overflow exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate arithmetic exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FLTDIV
arithmetic trap, floating/decimal divide by zero at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An arithmetic exception condition occurred as a result of an attempt to divide a floating point/decimal number by zero. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLTDIV_F
arithmetic fault, floating divide by zero at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: During a floating-point operation, an attempt is made to divide by zero. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLTOVF
arithmetic trap, floating overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An arithmetic exception condition occurred as a result of a floating-point overflow. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLTOVF_F
arithmetic fault, floating overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: During an arithmetic operation, a floating-point value exceeded the largest representable value for that data type. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLTPNTSYNX
floating point syntax error Facility: MACRO, VAX MACRO Assembler Explanation: A floating-point constant contained a syntax error. User Action: Correct the syntax of the constant.
FLTUND
arithmetic trap, floating underflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services, LIB, Library Facility Explanation: An arithmetic exception condition occurred as a result of floating-point underflow. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLTUND_F
arithmetic fault, floating underflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: During an arithmetic operation, a floating-point value became less than the smallest representable value for that data type. User Action: Examine the PC location displayed in the message; check the program listing to verify that operands or variables are specified correctly.
FLUNNORCV
expected floating point underfow exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate arithmetic exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
FLUSH
output stream flush requested Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont output routine requesting the output stream be flushed. User Action: None.
FNA
flag not allowed in this context: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: (1) A flag is used that requires that text directly precede or follow it; or (2) a flag character is replaced by another character (by means of a .FLAGS command) and the previous function of the replacement has not been disabled (by means of a .NO FLAGS command). User Action: Check your usage of the flag, and make the appropriate correction.
FNA
invalid file name string address Facility: RMS, VMS Record Management Services Explanation: Either the file specification string address field in the FAB is incorrect, or is in a portion of memory that cannot be read by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly. Specifically, check that the address specified points to the correct string.
FND
ACP file or directory lookup failed Facility: RMS, VMS Record Management Services Explanation: An error occurred during a directory search. This message is associated with a system status code returned from a file system ACP QIO request made by VMS RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
FNF
error opening 'filename' Facility: FDL, Edit/FDL Utility Explanation: The Edit/FDL utility could not open the specified file. User Action: Verify that the device, directory, file name, and file type are correctly specified. (If a logical name is specified, check its current equivalence value. If the equivalence value is correct, verify that the correct volume is mounted on the specified device and that the file is on the volume. If the file specification is incorrect, use the appropriate specification.)
FNF
file not found Facility: RMS, VMS Record Management Services Explanation: The specified file does not exist. User Action: Check the file specification and verify that the device, directory, file name, and file type were all specified correctly. If a logical name is specified, verify the current equivalence assigned to the logical name. If the equivalence is correct, verify that the correct volume is mounted on the specified device and that the file is not inadvertently deleted. Specify the existing file.
FNF
file not found Facility: SYSGEN, System Generation Utility Explanation: SYSGEN is unable to locate the driver image file. The default directory and disk device for driver images is SYS$SYSTEM. This message is also produced during an AUTOCONFIGURE operation if a UNIBUS device does not have a corresponding driver in SYS$SYSTEM. User Action: Restore the image file to the system disk from a backup disk.
FNM
error in file name Facility: RMS, VMS Record Management Services Explanation: The file name portion of a file specification is specified incorrectly. For example, the file name contains more than 39 characters. Or the use of a logical name resulted in more than one file name in the file specification. User Action: Verify the syntax of the file name in the file specification or in the logical name, if a logical name is specified.
FOP
invalid file options Facility: RMS, VMS Record Management Services Explanation: The file options parameter in the FAB contains conflicting options. In particular, the UFO or NFS options were specified on an indirect open of a process permanent file. User Action: Verify that the call to the VMS RMS service is coded correctly.
FORCEDERROR
forced error flagged in last sector read Facility: SYSTEM, VMS System Services Explanation: This message applies only to devices governed by the Mass Storage Control Protocol (MSCP). The data in this sector is copied from another sector that had unrecoverable read errors. This data is written with the Forced Error Indicator set to show to subsequent readers that the data is questionable. User Action: Be aware that the contents of the sector are only a close approximation of the data. Use the Backup Utility to make a copy of the original file and recover its contents.
FORCEDEXIT
forced exit of image or process by Job Controller Facility: SYSTEM, VMS System Services Explanation: When the job controller detects a violation of the login hour restrictions specified in the authorization record for a user, the job controller forces the process to terminate. User Action: See your system manager.
FORGET
participant has no further need for this transaction state Facility: SYSTEM, VMS System Services Explanation: The resource manager issued a call declaring that none of the effects of the transaction should be applied. User Action: None.
FORM_ABORT
record contents invalid - format aborted Facility: LMCP, Log Manager Control Program Explanation: An attempt was made to dump formatted records that contained invalid data. The dump of these records continues in hexadecimal format only. User Action: Submit a Software Performance Report (SPR) describing the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP and the DCL DUMP commands for the given log file.
FORMAT
file has illegal format Facility: LINK, Linker Utility Explanation: This is a secondary message indicating the object file in question has an illegal format. User Action: Correct the source, recompile, and relink.
FORMAT
invalid media format Facility: SYSTEM, VMS System Services Explanation: An I/O operation failed because the data medium is not in a format that the device driver expected. If this message is associated with a status code returned by a request to a magtape, the format specified by the last set tape characteristics function is not implemented in the slave controller. User Action: Verify the physical data pack, reel, or cartridge to ensure that the correct data medium is mounted. Contact the Digital Services Group if necessary. If the error occurred while initalizing a diskette, reissue the INITIALIZE command using the /DENSITY qualifier.
FORWLOOP
infinite forwarding detected sending to user 'username' Facility: MAIL, Mail Utility Explanation: A forwarding loop is created. This message is generated after the Mail Utility has gone through the loop ten times. User Action: Determine what caused the loop.
FPART_SECTN
unable to repair log with partially written section(s) Facility: LMCP, Log Manager Control Program Explanation: While scanning for active transactions, the REPAIR command found sections that have been partially written. The REPAIR command has been aborted because it cannot reconstruct sections that may be required for repair. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of both the LMCP DUMP command and the DCL DUMP command for the given log file.
FREEBADBUF
attempted to free busy (or free) buffer Facility: BACKUP, Backup Utility Explanation: A software error occurred in BACKUP. User Action: Submit a Software Performance Report (SPR).
FREEDISK
free up 'number' blocks on disk 'disk-name' Facility: QMAN, Queue Manager Explanation: The specified amount of disk space is needed on the named disk. User Action: Purge and delete files to make more space on the disk.
FREEMEM
error freeing virtual memory Facility: BACKUP, Backup Utility and ANALDISK, Analyze/Disk_ Structure Utility Explanation: An error was encountered during an attempt to free dynamic virtual memory. An accompanying message provides additional information. This message indicates a software error in the utility that produced it. User Action: Submit a Software Performance Report (SPR).
FREEMEM
memory deallocation failure Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
FREEPAGREF
free page reference count is nonzero Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an unrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
FREEVM
deallocated 'number' bytes of virtual memory leaving 'number' Facility: CNF, NI Configurator Explanation: The VM bit is set in NICONFIG$LOG. Virtual memory has been deallocated and the amount is tallied. User Action: None.
FRERANGE
storage package range error Facility: PATCH, Patch Utility Explanation: An internal error has occurred. User Action: Submit a Software Performance Report (SPR).
FRESIZE
storage package size error Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report (SPR).
FREWSLX
free working set list index, resource wait Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an unrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
FROMBUILTIN
called from built-in 'built-in-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message shows the name of the built-in calling the code that generated the error. User Action: None.
FROMLINE
called from line 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message shows the line number where the error occurred. User Action: None.
FROMPROCLINE
called from line 'integer' of procedure 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message shows the line number within procedure of the caller where the error occurred. User Action: None.
FRZNCTX
context is frozen - either cancel this context or use alternate Facility: CLI, Command Language Interpreter (DCL) Explanation: You are attempting to use the F$CONTEXT lexical to add context information to a symbol. A context symbol cannot be changed after it has been referenced by an appropriate lexical function other than F$CONTEXT, which requires a context symbol. User Action: You must either use another symbol or use the cancel function of F$CONTEXT to erase the context from this symbol.
FSZ
invalid fixed control header size Facility: RMS, VMS Record Management Services Explanation: The fixed control area size of the FAB for the file does not contain the correct value. Files that have the print file record format must have an FSZ value of 2. User Action: Verify that the call to the VMS RMS service is coded correctly.
FTM
network file transfer mode precludes operation (SQO set) Facility: RMS, VMS Record Management Services Explanation: For network file access, the FAB file option SQO selects DAP (Data Access Protocol) file transfer mode. In this mode of operation, data records are blocked together for transmission over the network to increase data throughput and reduce CPU overhead. Selection of DAP file transfer mode limits data transfers to one direction (either transmit using $PUT /$WRITE or receive using $GET/$READ). Other VMS RMS services are disallowed except for $DISCONNECT and $CLOSE, which terminate file transfer mode. User Action: Verify that the call to the VMS RMS service is coded correctly. Modify the source program to either not request the prohibited services or not specify the SQO FOP option in the FAB.
FUL
device full (insufficient space for allocation) Facility: RMS, VMS Record Management Services Explanation: A $CREATE, $EXTEND, or $PUT operation for a file failed because there is not enough space on the volume. User Action: Delete or purge as many files as possible to provide usable space on the volume, or request the system operator to do so. If the volume is private and files cannot be deleted, obtain a new volume.
FUNNOTSUP
function not supported Facility: PSM, Print Symbiont Explanation: This status is returned indicating the current function is not supported by the user service. For future compatibility, user services should return this status for any unrecognized function code. User Action: None.
FUTBAKDAT
file ('file-id') 'filename' backup date is in the future
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The date of the last backup recorded for the file is
later than the current date. The utility sets the backup date to
the current date.
User Action: None.
FUTCREDAT
file ('file-id') 'filename' creation date is in the future
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The creation date recorded for the file is later
than the current date. The utility sets the creation date to the
current date.
User Action: None.
FUTREVDAT
file ('file-id') 'filename' revision date is in the future
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The date of the last modification recorded for the
file is later than the current date. The utility sets the revision
date to the current date.
User Action: None.
FWF
footnotes won't fit on page Facility: RUNOFF, DIGITAL Standard Runoff Explanation: There are too many footnotes in the input file, or there are too many lines in a footnote. User Action: Reduce the number or size of the footnotes.
GBC
invalid global buffer count Facility: RMS, VMS Record Management Services Explanation: An incorrect global buffer count value is specified. The global buffer count value must be in the range of 0 to 32,767. User Action: Verify that the call to the VMS RMS service is coded correctly.
GBLNDF
cannot define symbol - global symbol scoping is enabled Facility: CLI, Command Language Interpreter (DCL) Explanation: You are trying to define a global symbol after using the SET SYMBOL /SCOPE=NOGLOBAL command. Global symbols cannot be accessed or defined while symbol scoping is set to be NOGLOBAL. This can be reset with the SET SYMBOL /SCOPE=GLOBAL command. User Action: Check your command procedure. Either change the symbol scoping to GLOBAL, or use local symbols.
GBLNOTCRE
global section not created Facility: SMG, Screen Management Facility Explanation: The system program that maps TERMTABLE.EXE as a global section is unsuccessful. User Action: This message should be handled only by system managers. If there is already an existing global section for termtable, the system must be rebooted in order to create a new global section.
GBLONLY
cannot obtain global copy of image section 'image-section' Facility: PATCH, Patch Utility Explanation: The image being patched references a global copy of an image section. There is no local copy of this section within the image file. User Action: To patch such a section, you must patch the shareable image file in which it is contained.
GBLPAGSZRO
Global page share count is zero Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
GBLSECMAP
system terminal table used Facility: SMG, Screen Management Facility Explanation: The requested terminal definition is found in the system termtable. The requested terminal definition did not exist in the caller's private termtable. User Action: None.
GBLSELOWNER
you are the global selection owner Facility: VAXTPU, VAX Text Processing Utility Explanation: This VAXTPU session is the global selection owner. User Action: Because you own the global section, you must process it yourself.
GBLWARN
patching local copy of global image section 'image-section' Facility: PATCH, Patch Utility Explanation: The image being patched: (1) references a global image section, (2) contained a local copy of the global image section (only the local copy is being patched), (3) is no longer allowed to use the shared global section. User Action: Patch the shareable image instead of the executable image, if you want to continue sharing the global section. You must reinstall the shareable image after it is patched.
GBLWSLXERR
Global working set list entry not found Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
GENERR
generated ERROR: 'xxxxx' message Facility: MACRO, VAX MACRO Assembler Explanation: A .ERROR directive is assembled; 'xxxxx' is the value of the expression specified in the directive; and message is the text specified in the directive. User Action: Follow the instructions in the message.
GEN_MAX
generic queue limit reached Facility: JBC, Job Controller Explanation: A maximum of eight generic queues can feed a specific execution queue. This message indicates that you attempted to make an execution queue the target of too many generic queues. User Action: None. This is a restriction.
GENMINUS1
shadow set virtual unit generation number invalid on 'device' Facility: BACKUP, Backup Utility Explanation: An attempt has been made to use BACKUP on a member of a shadow set which has not yet been fully formed. User Action: Wait for the shadow set to be fully formed and retry the BACKUP operation.
GENWRN
generated WARNING: 'xxxxx' message Facility: MACRO, VAX MACRO Assembler Explanation: A .WARN directive is assembled; 'xxxxx' is the value of the expression specified in the directive; and message is the text specified in the directive. User Action: Follow the instructions in the message.
GETCHN
error getting device characteristics Facility: DUMP, File Dump Utility Explanation: The File Dump Utility encountered an error during an attempt to obtain the device characteristics of the input device. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
GETCHN
error getting device characteristics for 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to obtain the device characteristics of the input device. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
GETDVI
error getting device characteristics, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered in an attempt to get the device characteristics of the specified relative volume. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
GETDVI
error obtaining device information for 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: An error is encountered while attempting to obtain information regarding the device. User Action: Examine the associated diagnostic messages, making corrections where appropriate.
GETERR
get error Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
GETERR
read error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: A VMS RMS $GET read request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry.
GETJPI
failed to obtain default job and process information Facility: RUN, Run Detached Utility Explanation: The system service $GETJPI failed to get process and job information used to create new subprocess or detached process. User Action: See error codes returned by the $GETJPI system service to determine action.
GETJPIERR
error from SYS$GETJPI Facility: ERF, Error Log Utility Explanation: This message indicates an internal consistency error. User Action: Submit a Software Performance Report (SPR).
GETMEM
Memory allocation failure Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU is attempting to allocate memory for its data structures, but there is not sufficient free memory for it to do so. This error may occur if you are using an extremely complex editing environment. User Action: First, delete unneeded strings, ranges, markers, windows, and buffers, then reenter your command. If the error reoccurs, increase the value of the SYSGEN parameter VIRTUALPAGECNT. If the available memory is still insufficient for your editing environment, try to increase your account's page file quota. Finally, if the error persists, ask your system manager to increase available memory.
GETMSG
error obtaining message text Facility: BAD, Bad Block Locator Utility Explanation: An error is encountered while attempting to obtain message text. User Action: Copy all pertinent diagnostic message information and submit a Software Performance Report (SPR).
GETPTIERR
error from $GETPTI, buffer 'number', image VPN 'decimal-number' for 'decimal-number' pages Facility: LINK, Linker Utility Explanation: An error is returned from the $GETPTI system service. User Action: Submit a Software Performance Report with all relevant programs, listings, object files, and library files.
GETTIM
error code of 'xx' on $GETTIM Facility: PATCH, Patch Utility Explanation: The $GETTIM system service request failed due to the error represented as 'xx'. User Action: Correct the error and retry.
GETVM
allocated 'number' bytes of virtual memory, total of 'number' Facility: CNF, NI Configurator Explanation: The VM bit is set in NICONFIG$LOG. Virtual memory has been allocated and the amount is tallied. User Action: None.
GFC
given footnote count incorrect, correct value is n Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The actual number of lines generated for the footnote is greater or less than the count specified with the .FOOTNOTE n command. User Action: None. This is an informational message. If you do not want the message to appear, remove the number from the .FOOTNOTE command.
GFVSADDER
error encountered testing g_floating vector-scalar addition Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVSDIVER
error encountered testing g_floating vector-scalar division Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVSMLTER
error encountered testing g_floating vector-scalar multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVSSBTER
error encountered testing g_floating vector-scalar subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVVADDER
error encountered testing g_floating vector-vector addition Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVVDIVER
error encountered testing g_floating vector-vector division Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVVMLTER
error encountered testing g_floating vector-vector multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GFVVSBTER
error encountered testing g_floating vector-vector subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during g_floating vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
GOSUBMAX
GOSUB procedures too deeply nested - limit to 16 levels Facility: CLI, Command Language Interpreter (DCL) Explanation: You are nested at the maximum level of subroutines and tried to transfer control to another lower level. User Action: Modify your command procedure so that it does not nest so deeply. Also ensure that you have a RETURN statement at the end of each subroutine.
GPGNULPGFL
global page has null page file address Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
GPTFULL
global page table is full Facility: SYSTEM, VMS System Services Explanation: Not enough space is available in system memory to maintain information about global sections. This message indicates a system error resulting from insufficient allocated space in the global page table. User Action: Notify your system operator or system manager to increase the SYSGEN parameter GBLPAGES.
GRANTERR
unable to grant identifier 'id-name' to 'user-id' Facility: AUTHORIZE, Authorize Utility Explanation: The specified resource identifier cannot be granted to the specified user ID. This message should be accompanied by a second message showing the specific reason why the identifier could not be granted. Resource identifiers are granted to UIC-format identifiers. Typically, this error occurs either because the specified resource identifier does not exist or because the target user ID is not a UIC-format identifier. The latter can occur when multiple accounts have the same UIC. User Action: Correct the condition identified by the second message and reenter your command.
GRANTMSG
identifier 'id-name' granted to 'user-id' Facility: AUTHORIZE, Authorize Utility Explanation: The specified general identifier has been granted to the specified user. The user has access to all of the rights associated with the identifier. User Action: None.
GSDFULL
global section descriptor table is full Facility: SYSTEM, VMS System Services Explanation: The system cannot create or map a global section because the system space allocated for global section data is full. This message usually indicates that the system is not generated with sufficient space for global section descriptors. User Action: Wait and retry the request. If the failure persists, notify the system manager.
GSDTYP
illegal GSD record type ('number') in module 'module-name' file
'filename'
Facility: LINK, Linker Utility
Explanation: An illegal GSD Record type is found in the specified
object module.
User Action: Submit a Software Performance Report on the
appropriate language compiler.
GSDTYP
illegal GSD record type 'record-type' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
GSDTYP
module 'module-name' file 'library-filespec' has an illegal GSD record 'record-type' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The specified object module is illegally formatted. User Action: Recompile the object module before inserting it into the library.
HALT
halt instruction restart Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
HALTED
transfer has been halted Facility: Shared by several facilities Explanation: If this message is returned from a DR32 support routine call, the DR32 transfer is complete. User Action: If the DR32 transfer halted unexpectedly, determine the cause of the error.
HANGUP
data set hang-up Facility: SYSTEM, VMS System Services Explanation: The associated terminal data set has been hung up. A Ctrl/Y or unsolicited data AST is delivered. User Action: None.
HBREAD
error reading home block of 'volume-name' Facility: SET, SET Facility Explanation: An error occurred while trying to read the home block of a volume. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
HBWRITE
error writing home block of 'volume-name' Facility: SET, SET Facility Explanation: An error occurred while trying to write to the home block of a volume. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
HDRBLK
too many ISDs for image header blocks Facility: PATCH, Patch Utility Explanation: You requested too many image section descriptors; PATCH is unable to create this patch area. User Action: Relink your image file.
HDRCRC
software header CRC error Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the header CRC field (BBH$W_CHECKSUM) of a save set block. Data in the save set is corrupted. User Action: None. The save set data is lost.
HDRERRS
errors occurred writing the dump file header blocks Facility: SDA, System Dump Analyzer Explanation: The first block of the dump file contains information indicating that there were errors while writing out the dump header. User Action: None. The dump file might not be useful for analysis.
HDRNOTMAP
allocated file header not mapped Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
HDRNOTRES
unable to make image header resident Facility: INSTALL, Install Utility Explanation: Insufficient pool is available to make the header resident, or the file has an image header larger than one block. User Action: Use the SYSGEN parameter PAGEDYN to increase the pool. Only files with one block image headers may be made resident.
HDRTRUNC
header truncated Facility: LBR, Librarian Subroutine Package Explanation: This warning message is generated by the Librarian routines. The buffer supplied to LBR$SET_MODULE is smaller than the header. User Action: Supply a larger buffer to LBR$SET_MODULE.
HEADCOPIED
copied 'file-header' header Facility: BACKUP, Backup Utility Explanation: The /LOG message indicating that a file header only is copied. The file is marked NOBACKUP; therefore, no data is saved. User Action: None.
HEADER_DEL
deleted file header Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message is issued along with the BADHEADER message and gives a more detailed reason why the specified file header is bad. In this case, the file header has the format of a deleted header. Additional messages indicate why a deleted file header is invalid in this context. User Action: None. See the BADHEADER message.
HEADERFULL
file header is full Facility: SYSTEM, VMS System Services Explanation: The file header map area on the volume is full and cannot be extended. This error occurs only when the file header extension is inhibited, for example, when the index file is being extended. User Action: Compress the volume by copying it with BACKUP.
HELP
enter HELP for INSTALL help Facility: INSTALL, Install Utility Explanation: This is an informational message. User Action: Enter HELP for INSTALL help. Help file could not be closed Facility: EDT, EDT Editor Explanation: You specified the name of a HELP file that EDT is unable to close. Some problem exists at the system level that prevents EDT from closing the file. User Action: After determining the cause of the system problem, correct it. Help file could not be opened Facility: EDT, EDT Editor Explanation: The requested EDT HELP file cannot be accessed. An error in system storage has occurred (for example, improper installation of the operating system). User Action: Verify that the logical name EDTHELP (with a default of SYS$HELP:.HLB) designates the EDT HELP file, and that the file has not been damaged. Help File Index could not be initialized Facility: EDT, EDT Editor Explanation: You created a new EDT HELP file or modified an existing EDT HELP file, but either you neglected to include an index number or you placed an indexed entry out of the proper nested order. User Action: Include the omitted index number or place the indexed entry in the proper nested order.
HELPERR
error finding or outputting HELP information Facility: AUTHORIZE, Authorize Utility Explanation: An error occurred trying to access the AUTHORIZE HELP file. User Action: Check that the AUTHORIZE HELP file, by default named UAFHLP.HLB, is located in the proper directory and is not protected against read access.
HELPERR
HELP command error Facility: MONITOR, Monitor Utility Explanation: An error occurred during execution of the HELP command of the Monitor Utility. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and rerun the HELP command. This error can occur when the MONITOR help library (SYS$HELP:MNRHELP.HLB) cannot be located or accessed.
HIB
hibernating until requested beginning time . . . Facility: MONITOR, Monitor Utility Explanation: Monitoring of the running system is requested, beginning at a future time. The process that issued the MONITOR request is placed in the hibernate state until the requested beginning time, at which time monitoring will begin. This is an informational message. User Action: If monitoring at a future time is desired, no user action is required. If, however, the /BEGINNING qualifier is incorrectly specified and if future monitoring is not desired, cancel the MONITOR request and reenter it.
HIBER
hibernating until 'time' Facility: SHOW CLUSTER, Show Cluster Utility Explanation: This is an informational message that is returned when the SHOW CLUSTER command is invoked with the /BEGINNING=beginning-time qualifier. The message indicates that the current process will be suspended until the time indicated. User Action: None.
HIDDEN
global variable 'name' by declaration Facility: VAXTPU, VAX Text Processing Utility Explanation: You have declared a parameter, local, or constant that has the same name as a global variable. Your declaration hides the global variable. User Action: None. High Priority Command Queue Insert Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line. User Action: Call the Digital Services Group. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention.
HIGHVER
higher version of 'output-filespec' already exists Facility: Shared by several facilities Explanation: An explicit version number is requested for an output file; the directory already contains an entry for the same file name and file type with a higher version number. User Action: None. The message is informational. Note that if the file is subsequently specified in a command, the system will locate the previously existing version if no version number is specified. The newly created output file will not be used.
HISTERR
error accessing library update history in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: An error occurred while accessing the library update history records. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
HOMBLKBAD
primary home block is bad; backup used Facility: MOUNT, Mount Utility Explanation: The primary home block of a disk is corrupted or unreadable; the backup volume is used to mount the volume. User Action: Repair the disk using the Analyze/Disk_Structure Utility.
HOMBLKCHK
home block software consistency check Facility: MOUNT, Mount Utility Explanation: The home block in the volume has failed the software consistency check during /BIND processing. The first occurrence of this message is a warning; the second is fatal. User Action: Repair or reinitialize the volume and retry the operation.
HRDFAI
hardware failure Facility: NCP, Network Control Program Explanation: The hardware associated with the request could not perform the function required. User Action: Contact your system manager or the Digital Services Group. HSC Error Logging Datagram Received Facility: VAXport, VAXport Driver Explanation: Upon receiving an error message from the HSC, the CI port driver logs the error and takes no other action. Since HSC informational error log datagrams are also recorded on the HSC console, it is useful to read them only if the HSC console does not record them for some reason (if it runs out of paper, for example). User Action: You should disable the sending of HSC informational error log datagrams with the appropriate HSC console command, since HSC informational error log datagrams take up considerable space in the error log data file. I/O error on work file Facility: EDT, EDT Editor Explanation: EDT is unable to access its text storage area for the file. An additional message will explain the error further, such as "Device full" or "Device write locked". User Action: Correct the problem described in the file system message.
IAL
invalid argument list Facility: RMS, VMS Record Management Services Explanation: The argument list in a call to SYS$RMSRUNDWN, SYS$SETDDIR, or SYS$SETDFPROT control routines either cannot be accessed or contains invalid data. User Action: Verify that the call to the VMS RMS service is coded correctly.
IAN
invalid index area number for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The index area number specified in a key definition XAB is not a defined area for the file. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
IBF
illegal bucket format in VBN = 'nnn' Facility: RMS, VMS Record Management Services Explanation: VMS RMS detected a corrupted bucket in an indexed file. Incorrect bucket control flags or an incorrect bucket freespace value is detected. This error is caused by hardware errors, VMS RMS or system software errors, or inadvertent modifications of files by non-RMS programs. User Action: Reorganize the file with the CONVERT command, or re- create the file. The status value (STV) field of the FAB or RAB contains the starting virtual block number of the bucket in error.
IBK
LAN bucket size not equal IAN bucket size for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The bucket size for the index area specified by IAN must be the same as the bucket size of the lowest-level index area specified by LAN. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly. In particular, determine that the correct area numbers and sizes were specified for the index and lowest-level index areas.
IBO
input buffer overflow: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A character string that is too long was entered in an internal line buffer. This is a DSR internal error message. User Action: Submit a Software Performance Report (SPR).
ICONCLUDAT
inconsistent cluster database Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ICONPFNDAT
inconsistent PFN database Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ICPAGELOC
inconsistent page location Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ICVNOTFND
input converter not found Facility: CDA, Compound Document Architecture Explanation: The specified input converter could not be found. User Action: Check the format specified for the input file for errors. See if the file SYS$LIBRARY:'domain'$READ_'format'.EXE exists, where 'domain' is DDIF for document formats or DTIF for tabular formats and 'format' is the input format specified by the calling application or the CONVERT/DOCUMENT command line.
IDD
invalid display descriptor: "text in error" Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You specified an incorrect descriptor in a .DISPLAY directive. User Action: Correct the specified descriptor.
IDENT
DSRTOC version 'version-number' Facility: DSR, DIGITAL Standard Runoff Explanation: This informational message is displayed when the /IDENTIFICATION qualifier is specified. It shows the version number of the DSR Table of Contents Utility. User Action: None.
IDENT
standalone BACKUP 'string'; the date is 'date and time' Facility: BACKUP, Backup Utility Explanation: This is a standalone BACKUP identification message. User Action: Make sure that the displayed data is correct.
IDMISMATCH
ident mismatch with global section or shareable image Facility: SYSTEM, VMS System Services Explanation: The ident is part of the global section name. An attempt is made to create a shared memory global section using a different ident with a name that is the same as that of an existing shared memory section. This error occurs when an attempt is made to install an image in shared memory (MA780) from two processors that do not have identical image files. User Action: Copy the file from one processor to the other and retry the operation.
IDMISMATCH
section NOT restored, section file must be rebuilt Facility: VAXTPU, VAX Text Processing Utility Explanation: This version of VAXTPU is not compatible with the section file that you are trying to access. User Action: Save the section file again by running the source file through the version of VAXTPU you are trying to use.
IDMISMCH
GSMATCH of 'number,number' in shareable image 'image-name' differs from GSMATCH of 'number,number' in shareable image library 'library- name' Facility: LINK, Linker Utility Explanation: A shareable image extracted from a shareable image library has a different GSMATCH than the GSMATCH recorded for that shareable image in the library. User Action: Insert the new shareable image into the shareable image library using the DCL command LIBRARY.
IDOUTRNG
identifier value is not within legal range Facility: AUTHORIZE, Authorize Utility Explanation: The value you specified for an identifier is not within the permissible range. A general identifier may have an integer value between 32,768 and 268,435,455. A UIC identifier takes a value in standard UIC format. User Action: Reenter your command with an identifier value that is within the permissible range.
IDR
invalid directory rename operation Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $RENAME service is requested that would rename a directory file into a directory tree that contained the directory file. The directory would then be inaccessible. An example of incorrect usage is: $RENAME [A]B.DIR [A.B] User Action: Modify the program or reenter the command specifying the correct old and new file specifications for the $RENAME service.
IDX
index not initialized Facility: RMS, VMS Record Management Services Explanation: The index of an indexed file could not be properly initialized when inserting the first record. User Action: Re-create the file. Collect as much information as possible and submit a Software Performance Report (SPR).
IDXCONCAT
indexed file cannot be concatenated Facility: Shared by several facilities Explanation: An indexed file cannot be concatenated with another file. User Action: Use an indexed file load program to load the indexed file.
IDXFILEFULL
index file is full Facility: SYSTEM, VMS System Services Explanation: No more files can be written on the volume, because the maximum size of the index file specified is reached when the volume is initialized. User Action: If the volume is a private volume, delete the unwanted files on the volume. If the volume is a system volume, notify the system operator or system manager.
IDXHDRBAD
index file header is bad; backup used Facility: MOUNT, Mount Utility Explanation: This message is generated by the DCL command MOUNT. The primary index file header is corrupted or unreadable; the backup volume is used to mount the volume. User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE /REPAIR command.
IDX_LIM
exceeded maximum index level Facility: CONVERT, Convert Utility Explanation: The index tree depth exceeded 32 levels. User Action: Redesign the file to make it more shallow.
IDXMAPERR
I/O error on index file bitmap; volume locked Facility: MOUNT, Mount Utility Explanation: I/O error encountered during a mount operation. Existing files in the volume can be accessed but other operations, for example, create and delete, are not possible. User Action: Repair the volume with the ANALYZE/DISK_STRUCTURE /REPAIR command.
IFA
illegal file attributes detected (file header corrupted) Facility: RMS, VMS Record Management Services Explanation: The content of the file header was corrupted; the data is inconsistent and cannot be read. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a system status code that provides additional information about the condition. Take corrective action based on this status code. If the error persists, collect as much information as possible and submit a Software Performance Report (SPR).
IFDIRSYNX
IF directive syntax error Facility: MACRO, VAX MACRO Assembler Explanation: A conditional assembly directive contained a syntax error. User Action: Correct the syntax of the directive.
IFEXPRNABS
IF expression not absolute Facility: MACRO, VAX MACRO Assembler Explanation: The expression in an .IF directive is not an absolute expression or contained undefined symbols. User Action: Change the values in the expression.
IFF
invalid file attributes for requested file access Facility: RMS, VMS Record Management Services Explanation: The attributes of the file do not permit the type of file access requested. For example, usually this means that the user attempted to open an ANSI magnetic tape file for write access, and the file has a nonzero value for buffer offset. VMS RMS will not allow you to create a magnetic tape file with nonzero buffer offset. However, you may access the file for input and output if you specify block I/O. User Action: Correct the type of access requested or change the attributes of the file.
IFI
invalid internal file identifier (IFI) value Facility: RMS, VMS Record Management Services Explanation: The internal file identifier field of the FAB is invalid. This error usually indicates that the file has not been opened for an operation that requires the file to be opened, or that the file is already opened for an operation that requires the file not to be opened. User Action: Check for a programming error. Verify the logic of the program to see that the file is opened or closed as required for the attempted operation.
IFL
index bucket fill size larger than bucket size for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The index bucket fill specified in a key definition XAB exceeds the bucket size for the data area. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
IFLEVLXCED
IF nesting level exceeded Facility: MACRO, VAX MACRO Assembler Explanation: The assembler encountered more than 31 levels of nested conditional assembly blocks. User Action: Restructure the program to decrease nesting of conditional assembly blocks.
IFREPAGCNT
inconsistent free page count Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
IFT
illegal in footnote: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to use an illegal command between the DSR commands .FOOTNOTE and .ENDFOOTNOTE. User Action: Remove the command.
IGNCLIFLAG
line 'line-number': CLI flag ignored in this context Facility: CDU, Command Definition Utility Explanation: CDU encountered an illegal argument for CLI flags for the current context. User Action: Edit the .CLI file so that all CLI flags are valid in the context in which they are used. Refer to the VMS Command Definition Utility Manual for more information on the use of control flags in the Command Definition Utility.
IGNFIL
ignoring input file: 'filespec' Facility: MONITOR, Monitor Utility Explanation: An input file specified in an /INPUT list was excluded from inclusion in a multifile summary. The linked error message accompanying this message provides an explanation for the exclusion. User Action: If the ignored file is one which should be included in the multifile summary, then examine the linked error message, correct the situation described therein, and reenter the MONITOR request.
IGNORED
'string' ignored Facility: DSR, DIGITAL Standard Runoff Explanation: DSR ignored a character string during processing. User Action: None.
IGNORE_DIRE
directory name ignored, not used for this volume type Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ignored the directory name field of a filename. User Action: Do not enter the directory name; it is not needed.
IGNORE_VERS
file version ignored, not used for this volume type Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ignored the version number field of a filename. User Action: Leave the version number off; it is not needed.
IGNQUAL
qualifiers apppearing before this item were ignored Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the qualifiers appearing before the displayed item were ignored. User Action: None.
IIF
^X ignored Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A control character code (^X) was illegally entered in the input file and has not been accepted. User Action: In order to legalize the entry of such codes, you must enter the .CONTROL CHARACTERS command.
ILC
illegal command: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This command is illegal. Command or values you specify for it are unrecognizable. User Action: Check for spelling errors in the command keywords.
ILE
internal logic error 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR has detected an internal failure at the location specified by the indicated string. This is a DSR internal error. User Action: Submit a Software Performance Report (SPR).
ILLANSIBS
ANS magnetic tape block size must be at least 18 characters Facility: MOUNT, Mount Utility Explanation: The label specified for a magnetic tape contains less than 18 characters. User Action: Reenter the command; specify a minimum value of 18 for the block size.
ILL_ARG
wrong number of arguments Facility: FDL, Create/FDL Utility Explanation: You specified too many files in the FDL$CREATE call. User Action: Specify the correct number of files.
ILLARGDESC
illegal operand argument descriptor Facility: MACRO, VAX MACRO Assembler Explanation: The operand descriptor in an .OPDEF directive is invalid. User Action: Use one of the valid operand descriptors.
ILLASCARG
illegal ASCII argument Facility: MACRO, VAX MACRO Assembler Explanation: Either the argument to a .ASCIx directive did not have enclosing delimiters or an expression is not enclosed in angle brackets. User Action: Correct the syntax of the argument.
ILLBATFNC
operation not permitted while display is batched Facility: SMG, Screen Management Facility Explanation: An attempt is made to perform an operation that is not permitted while a virtual display is being batched-for example, when performing input or moving the virtual display. User Action: Terminate batching first by calling SMG$END_DISPLAY_ UPDATE.
ILLBLKNUM
illegal logical block number Facility: SYSTEM, VMS System Services Explanation: The logical block number specified does not exist on the disk. If this error results from a Files-11 I/O operation, the file structure is damaged. User Action: Check for a programming error. If this error results from a Files-11 I/O operation, repair the volume using the Analyze /Disk_Structure Utility.
ILLBRDEST
illegal branch destination Facility: MACRO, VAX MACRO Assembler Explanation: The destination of a branch instruction is not an address, for example, BRB 10(R9). User Action: Change the destination of the branch instruction or use a jump (JMP) instruction.
ILLCDTST
illegal connection descriptor table state Facility: SYSTEM, VMS System Services Explanation: A system facility attempted an operation on a connection that is illegal for the current state of that connection. User Action: Submit a Software Performance Report (SPR).
ILLCHR
illegal character Facility: MACRO, VAX MACRO Assembler Explanation: The source line contained a character that is illegal in its context. User Action: Delete the illegal character.
ILLCNTRFUNC
illegal ACP control function Facility: SYSTEM, VMS System Services Explanation: The control function specified in an IO$_ACPCONTROL QIO request is not a valid function. User Action: Check for a programming error. Consult the documentation for the correct function codes and coding specifications.
ILLCOMPONENT
illegal initialization component Facility: LIB, Library Facility Explanation: An illegal component value is passed to LIB$INIT_ DATE_TIME_CONTEXT. User Action: Examine the component value and correct it, if necessary.
ILLCREOPT
illegal create options Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. Either the create options you specified for LBR$OPEN are illegal or no options were specified. User Action: Correct the create options before calling the routine.
ILLCTL
illegal control index Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. Either the library is not open or you have specified an illegal library index. User Action: Determine that the library is open and that the library index is correct.
ILLDESQUE
illegal destination queue name Facility: SYSTEM, VMS System Services Explanation: In a request to the symbiont manager, the specified destination queue is invalid. User Action: Reenter the command, specifying a valid destination queue.
ILLDFLTARG
illegal argument for .DEFAULT directive Facility: MACRO, VAX MACRO Assembler Explanation: A .DEFAULT directive did not specify DISPLACEMENT or the displacement specified is not one of the three keywords-BYTE, WORD, or LONGWORD. User Action: Correct the .DEFAULT directive.
ILLEFC
illegal event flag cluster Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: An event flag number specified in a system service call is greater than 127. User Action: Correct the source program. Verify that the event flag number is correctly coded, and that it is not modified during the execution of the image.
ILLEGALTYPE
illegal data type Facility: VAXTPU, VAX Text Processing Utility Explanation: The expression or operator contains an invalid data type. User Action: Check the data type being used and make sure that the expression or operator supports this data type.
ILLEVTNUM
illegal event number Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ILLEXPR
illegal expression Facility: MACRO, VAX MACRO Assembler Explanation: A radix unary operator is not followed by a number, or left and right angle brackets did not match in an expression. User Action: Correct the syntax of the expression.
ILLFMLCN
minimum argument count ('decimal-number') exceeds maximum ('decimal-
number') in formal specification of symbol 'symbol-name' in module
'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: A procedure definition subrecord has an illegal
format.
User Action: Submit a Software Performance Report on the
appropriate language compiler.
ILLFMLCNT
minimum argument count exceeds maximum for procedure 'procedure' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLFMT
illegal library format Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The file you specified calling LBR$OPEN is not a library. User Action: Specify the correct library.
ILLFORMAT
illegal format, too many or not enough fields Facility: LIB, Library Facility Explanation: You entered an invalid format string. User Action: Examine the date/time string and correct it.
ILLFUNC
illegal library function Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The library function you specified in LBR$OPEN is illegal. User Action: Correct the library function before calling the routine.
ILLIDXNUM
illegal index number Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The index number you specified is illegal. User Action: Correct the index number before calling the routine.
ILLIFCOND
illegal IF condition Facility: MACRO, VAX MACRO Assembler Explanation: The condition specified in a conditional assembly is not a valid condition, or there were no symbols after a DIFFERENT or IDENTICAL condition. User Action: Correct the syntax of the conditional assembly directive.
ILLINDXREG
invalid index register Facility: MACRO, VAX MACRO Assembler Explanation: The base mode changed the value of the register, and the index register is the same as the register in the base mode; the base mode is literal or immediate mode; or PC is used as the index register. User Action: Correct the addressing mode.
ILLINISTR
illegal initialization string Facility: LIB, Library Facility Explanation: An incorrect initialization string is passed to LIB$INIT_DATE_TIME_CONTEXT. User Action: Verify that the initialization string begins and ends with the same delimiter character.
ILLINROU
input routine improperly specified or missing Facility: LBR, Librarian Subroutine Package Explanation: A librarian function is called with a missing or invalid input routine parameter. User Action: If no input routine is passed to the librarian function, then supply one; or check the values of the other arguments that were passed to ensure that none of the arguments specify that the input routine parameter is required. If a routine value is supplied, then check that it is a valid address (for example, nonzero).
ILLIOFUNC
illegal I/O function code Facility: SYSTEM, VMS System Services Explanation: A function code in an explicit input/output request is invalid. Or if the errors occurred during a DECnet-VAX operation, the user attempted a synchronous disconnect with outstanding transmits. User Action: Check for a programming error. Locate the invalid function code and correct it.
ILL_KEY
illegal key or value out of range Facility: CONVERT, Convert Utility Explanation: You have specified /KEY with a nonnumeric value, or with a numeric value that is outside the range of 0 to 254. User Action: Specify a legal value with /KEY.
ILLKEYLVL
illegal key level 'number' key 'keyname' in 'library-name' expected 'key number' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The help module you want to insert into the library is formatted incorrectly. User Action: Reformat the module before inserting it into the library.
ILLMACARGN
illegal MACRO argument name Facility: MACRO, VAX MACRO Assembler Explanation: The name in the .MACRO directive contained an illegal character. User Action: Delete the illegal character.
ILLMACNAM
illegal MACRO name Facility: MACRO, VAX MACRO Assembler Explanation: No MACRO name is specified in the .MACRO directive. User Action: Specify the MACRO name in the .MACRO directive.
ILLMASKBIT
reserved bits set in ENTRY mask Facility: MACRO, VAX MACRO Assembler Explanation: The register save mask in an .ENTRY or .MASK directive specified R0, R1, AP, or FP registers (corresponding to bits 0, 1, 12, and 13). User Action: Remove these registers from the register save mask.
ILLMODE
illegal mode Facility: MACRO, VAX MACRO Assembler Explanation: An invalid addressing mode for the instruction is specified. User Action: Specify a legal addressing mode.
ILLMODNAM
illegal module name length 'length' for module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLMTCOPY
cannot specify same magtape for both input and output Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility detected an attempt to use a single DOS-11 magtape for both input and output. User Action: Specify different magtapes for input and output, or copy the file onto disk before copying it back out to tape.
ILLNAMELEN
'name' 'name' name length ('decimal-number') is illegal - not 1 to
'decimal-number' in module 'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: The length of a psect, module, or symbol name is
illegal.
User Action: Correct the length and relink.
ILLOP
illegal operation for access requested Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. You have attempted to modify a Version 1.0 library or a read-only library. User Action: Compress the library into the current format or change the access privileges to the library file.
ILLOPDEF
illegal format for .OPDEF Facility: MACRO, VAX MACRO Assembler Explanation: The .OPDEF directive had incorrect syntax. User Action: Correct the .OPDEF directive syntax.
ILLOPDEFVL
illegal value for opcode definition Facility: MACRO, VAX MACRO Assembler Explanation: The value specified in the .OPDEF directive does not fit in two bytes. User Action: Correct the value in the directive.
ILLOPT
qualifiers not appropriate to this device Facility: MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: A DCL command MOUNT or INITIALIZE specified qualifiers that apply only to disk devices for a tape device, or qualifiers that apply only to tape devices for a disk device. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for a list of qualifiers, and reenter the command with the appropriate qualifiers.
ILLOUTROU
output routine improperly specified or missing Facility: LBR, Librarian Subroutine Package Explanation: A librarian function is called with a missing or invalid output routine parameter. User Action: If no output routine is passed to the librarian function, either supply one or check the values of the other arguments that were passed. This ensures that none of the arguments specify that an output routine parameter is required. If a routine value is supplied, check to see that it is a valid address, for example, nonzero.
ILLPAGCNT
illegal page count parameter Facility: SYSTEM, VMS System Services Explanation: The number of pages specified for an expand or contract region request is less than one. User Action: Check for a programming error; verify the number of pages specified for the service call.
ILLPATAS
pattern assignment target only valid in procedure 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The target of a partial pattern assignment, the @ operator, was defined in, and is only valid in, the named procedure. User Action: Use a global variable for the partial pattern assignment or use this pattern only from within the named procedure.
ILLPERNAM
'string' is an illegal personal name Facility: MAIL, Mail Utility Explanation: You specified a string containing an illegal combination of characters, such as, for example, multiple consecutive spaces, special characters that MAIL cannot process, or unbalanced quotation marks. User Action: Specify a personal name that avoids the problem.
ILLPSCLEN
psect 'psect-name' has illegal length 'length' for module 'module- name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLQUAL
invalid qualifier Facility: MOUNT, Mount Utility Explanation: An invalid qualifier is given in the command. User Action: Replace the qualifier and reenter the command.
ILLQUALVAL
illegal qualifier value Facility: LINK, Linker Utility Explanation: The command line contained an illegal value for a qualifier. User Action: Reenter the command correctly.
ILLRECLEN
illegal record length 'length' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLRECLEN
illegal record length ('decimal-number') in module 'module-name'
file 'filename'
Facility: LINK, Linker Utility
Explanation: A module contains a record of illegal length.
User Action: Submit a Software Performance Report on the
appropriate language compiler.
ILLRECLN2
illegal record length 'length' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLRECTY2
illegal record type 'record-type' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLRECTYP
illegal record type 'type' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLRECTYP
illegal record type ('decimal-number') in module 'module-name'
record 'record-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: A module contains an illegal object record type.
User Action: Submit a Software Performance Report on the
appropriate language compiler.
ILLREGHERE
this register may not be used here Facility: MACRO, VAX MACRO Assembler Explanation: The PC register cannot be used in the following addressing modes: register, register deferred, autodecrement, autoincrement, and autoincrement deferred. User Action: Use another register.
ILLREGNUM
illegal register number Facility: MACRO, VAX MACRO Assembler Explanation: A register name is not the AP, FP, SP, or PC register name. Or it is not in the range R0 through R12. User Action: Correct the illegal register name.
ILLREQUEST
request 'name' is invalid Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified request is not valid for this built-in. User Action: Reenter the command with a valid request string.
ILLRQST
illegal operator request Facility: OPCOM, Operator Communication Process Explanation: A DCL command REPLY is entered with no qualifiers. Or, a DCL command REQUEST specified an incorrect value. User Action: Verify the command line and reenter the command.
ILLSAVESET
illegal save set name specified to RESTORE_SAVESET. Facility: VMSINSTAL, Install Procedures Explanation: The product installation procedure contains an incorrect call to RESTORE_SAVESET. User Action: Contact the Digital Services Group.
ILLSELF
illegal self reference Facility: SYSTEM, VMS System Services Explanation: You have unsuccessfully attempted to suspend all action on your own job. User Action: None. Your job is not suspended.
ILLSEQOP
illegal sequential operation Facility: SYSTEM, VMS System Services Explanation: When a sequential access device is used, such as a magnetic tape, certain operations can be performed only at the appropriate time. For example, the control function NEXT VOLUME can be executed only when the tape is positioned within the data section. User Action: Examine the source program to determine the logic problem.
ILLSER
illegal service call number Facility: SYSTEM, VMS System Services Explanation: An image specified an invalid change mode to executive or kernel service number. User Action: Check for a programming error. Locate the invalid call and correct it.
ILLSEVERITY
illegal severity of 'value' specified, error severity used Facility: VAXTPU, VAX Text Processing Utility Explanation: Severities must be between 0 and 3, inclusive. User Action: Specify a valid severity.
ILLSHROPR
illegal shareable image reference expression operator in module 'module-name' record 'record-name' file 'filename' Facility: LINK, Linker Utility Explanation: An attempt is made to perform an operation, other than addition or subtraction, in an expression that contained a symbol from a shareable image. User Action: Correct the expression and relink.
ILLSHRXPR
illegal shareable image reference expression in module 'module-name' record 'record-name' file 'filename' Facility: LINK, Linker Utility Explanation: An expression contains two symbols externally defined in a shareable image. The linker can resolve expressions that contain only one externally defined symbol. User Action: Correct the expression and relink.
ILLSTRCLA
illegal string class Facility: STR, String Manipulation Facility Explanation: The class code found in the class field of a descriptor is not a string class code supported by the VMS Procedure Calling and Condition Handling Standard. User Action: If you are programming in a high-level language and using the string data types and functions that are supplied by the language, check that there are no logic errors where data is written outside array bounds or other errors where data is written incorrectly. If you are creating descriptors, check that all string descriptors are initialized before using them.
ILLSTROPS
illegal string position Facility: STR, String Manipulation Facility Explanation: Successful completion. However, one of the character- position parameters to a string routine pointed to a character- position that is before the beginning of the input string or that is after the end of the input string. User Action: Ensure that any parameter that is a character- position is greater than zero and less than or equal to the length of the input string.
ILLSTRSPE
illegal string specification Facility: STR, String Manipulation Facility Explanation: Successful completion except that the character- position parameters specifying a substring of a string parameter were inconsistent because the ending character-position is less than the starting character-position. A null string is used for the substring. User Action: The applications program should verify that starting character-positions are less than or equal to ending character- positions.
ILLSYMLEN
symbol 'symbol' has illegal length 'length' in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
ILLSYMLEN
symbol exceeds 31 characters Facility: MACRO, VAX MACRO Assembler Explanation: The symbol name is longer than 31 characters. The assembler truncated the name to 31 characters. User Action: Specify a symbol name that has no more than 31 characters.
ILLTIR
illegal relocation command 'command-name' in module 'module-name' record 'record-name' file 'filename' Facility: LINK, Linker Utility Explanation: A module contains an invalid object language command. User Action: Submit a Software Performance Report on the appropriate language compiler.
ILLTYP
illegal library type Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The type of library specified in LBR$INI_CONTROL is invalid. User Action: Correct the library type before calling the routine.
ILLVAL
boolean value must be 0 or 1 Facility: SMG, Screen Management Facility Explanation: A Boolean capability is given a value other than 0 or 1. User Action: Check your terminal definitions. Boolean capabilities must be 0 or 1: on or off, respectively.
ILLVAL
illegal CPU time Facility: RUN, Run Detached Utility Explanation: The CPU time limit entered with the /TIME_LIMIT qualifier value is too large. User Action: Reenter the RUN command with a valid CPU time limit.
ILLVAL
illegal value is present Facility: CLI, Command Language Interpreter (DCL) Explanation: A value is not within the valid range of values. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary, if necessary, for the valid values and reenter the command.
ILL_VALUE
illegal parameter value Facility: CONVERT, Convert Utility Explanation: You have specified an invalid or out-of-range value on a qualifier. User Action: Specify a valid value and try again.
ILLVEC
illegal interrupt or exception vector restart Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ILLVECOP
illegal vector opcode fault, opcode='xx', PC='location', PSL='xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An operation code designated as an illegal vector opcode by the VAX architecture has been encountered during the execution of an image. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC of the vector instruction that caused the exception to be reported. (Note, however, that this instruction is not always the instruction that caused the exception.)
ILLVPS
illegal position ('decimal-number') or size ('decimal-number')
in STO_VPS command 'command-name' in module 'module-name' file
'filename'
Facility: LINK, Linker Utility
Explanation: The STO_VPS object language command has invalid
arguments.
User Action: Submit a Software Performance Report on the
appropriate language compiler.
IMAGEFMT
command tables image has illegal format Facility: CDU, Command Definition Utility Explanation: Input tables have an invalid format. Either an invalid file is entered or a valid file is entered but then became corrupted. User Action: Do not use this file again with the SET COMMAND.
IMAGEFNF
image file not found 'filename' Facility: CLI, Command Language Interpreter (DCL) Explanation: You attempted to run a nonexistent image. User Action: Check for typing errors and retry.
IMAGELEN
an image spec is limited to 'max-length' characters in length Facility: CDU, Command Definition Utility Explanation: CDU encountered a image specification in the CLD file which exceeded the maximum allowable file specification character count. Currently file specification strings are limited to 63 characters in length. User Action: Rename the image and/or use logical names to specify the directory of the image.
IMAGE_NOT_FOUND
this image has not yet been mapped Facility: IMGACT, Image Activator Explanation: An inconsistency exists between the shared image list stored in the image fixup vector and the list of global ISDs stored in the image header. This can possibly occur when images linked on older versions of VMS are run on newer versions where new copies of shareable images are being referenced by the old executable image. User Action: Relink the executable images to achieve a consistent shareable image linkage mechanism within the image header of your image.
IMGADDED
added image for product Facility: SYSMAN, Cluster System Management Utility Explanation: The named image file was added to the loadable image database for the named product. User Action: Verify that the named image and product are correct.
IMGBASED
shareable image 'image-name' is already based Facility: LINK, Linker Utility Explanation: You specified a base address in an options file for a shareable image that is already based. User Action: Make the image position-independent so it can be based anywhere; or remove the cluster option from the options file that tries to base it.
IMGDUPINV
image already in images table Facility: SMI, System Management Integrator/Server Explanation: The specified image name/product name pair already exists in the loadable image file. User Action: Select a different image name or product name.
IMGFILGON
loadable image file is missing Facility: SMI, System Management Integrator/Server Explanation: The loadable image database currently in use is no longer available. User Action: Check for accidental deletion of the file.
IMGFILSPE
the /IMAGE specification must have only device name Facility: BACKUP, Backup Utility Explanation: The file specification for a volume to be processed with the /IMAGE qualifier must contain only a device name. User Action: Reenter the command using the device name only.
IMGHDR
error while accessing the image header Facility: INSTALL, Install Utility Explanation: INSTALL encountered an error when trying to access the image header. An accompanying error message explains the failure. User Action: Correct the situation indicated by the accompanying error message and reenter the command.
IMGINV
image name invalid - must contain valid file name only Facility: SYSMAN, Cluster System Management Utility Explanation: The image name's file specification contains more than just a file name. User Action: Reenter the command with a valid image file name.
IMGNAME
image file 'filename' Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is issued with an associated message indicating the problem. User Action: Take corrective action based on the associated message.
IMGNOTFND
image not found for product Facility: SMI, System Management Integrator/Server Explanation: The specified image file is not found in the loadable image database for the given product. User Action: Specify a product name contained in the database.
IMGRECSIZ
invalid image record size Facility: MOM, Maintenance Operation Module Explanation: The image that is being accessed to downline load is unsupported. User Action: Use a supported image type to downline load.
IMGREMOVED
removed image for product Facility: SYSMAN, Cluster System Management Utility Explanation: The named image file was removed from the loadable image database for the named product. User Action: Verify that the named image and product are correct.
IMG_SIZ
image header descriptor length is invalid Facility: IMGACT, Image Activator Explanation: The length of the fixed part of the image header is invalid. This usually indicates a corrupted or invalid image. User Action: Relink the image.
IMGTRACED
TRACEBACK image cannot be privileged or execute_only Facility: INSTALL, Install Utility Explanation: This message indicates that an attempt is made to CREATE or REPLACE a known file image with either the /PRIVILEGE or /EXECUTE_ONLY qualifiers, and that the image had been linked with the /TRACEBACK qualifier. User Action: Relink the image using the /NOTRACEBACK qualifier and retry the image installation.
IMGVEXC
image exiting with pending vector exceptions Facility: SYSTEM, VMS System Services Explanation: An exception has resulted from the execution of a vector instruction issued by an image, however, the image exited before the exception could be delivered. User Action: The image's source code must be modified to check for pending vector exceptions before exiting. The VAX Procedure Calling and Condition Handling Standard requires that procedures guarantee that no exception can be raised after the procedure has relinquished control. If a procedure executes a vector instruction that might possibly raise an exception, it must execute a SYNC instruction (a form of MFVP instruction) prior to any subsequent CALL or RET.
IMX
invalid duplicate XAB or non-dense XAB at 'location' Facility: RMS, VMS Record Management Services Explanation: More than one XAB of the same type exists for the operation; or another XAB type occurs within a subchain of allocation or key definition XABs. User Action: The status value (STV) field of the FAB provides the address of the XAB in error. Verify that the call to the VMS RMS service is coded correctly. Inappropriate SCA Control Message Facility: VAXport, VAXport Driver Explanation: The VAXport driver closes the port-to-port virtual circuit to the remote port. User Action: Submit a Software Performance Report, including the error logs and the crash dumps from the local and remote systems.
IN_BARRIER_WAIT
barrier in wait state, quorum not modified Facility: PPL, Parallel Processing Facility Explanation: The barrier is already in effect at the time of this call. User Action: Recode the program to ensure that the barrier quorum is established before anyone attempts to wait on the barrier.
INBUILTIN
occurred in built-in 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message specifies the name of the built-in that generated the error. User Action: None.
INCBADDIR
saved directory 'directory-name' has invalid format Facility: BACKUP, Backup Utility Explanation: In response to the /INCREMENTAL qualifier, the saved copy (in the input save set) of the specified directory is not in the expected format for a directory file. The file may have been corrupted when it is saved, or save set data may have been lost. User Action: After you complete the incremental restoration, check the files for correct format.
INCCTXT
incomplete crash context available Facility: SDA, System Dump Analyzer Explanation: A CPU that participated in the system BUGCHECK did not save its context information correctly. Some CPU context information might not be available for analysis. User Action: None.
INCDATTIM
incomplete date_time, missing fields with no defaults Facility: LIB, Library Facility Explanation: An incomplete date or time parameter is supplied. User Action: Examine the date/time string.
INCDELERR
error deleting 'filename' Facility: BACKUP, Backup Utility Explanation: An error is encountered during an attempt to delete the specified file in response to the /INCREMENTAL qualifier. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
INCDELETE
deleted 'filename' Facility: BACKUP, Backup Utility Explanation: The Backup Utility deleted the specified file in response to the /INCREMENTAL qualifier. This message appears if you specify the /LOG qualifier. User Action: None.
INCDEVLIS
disk and tape devices mixed in list Facility: BACKUP, Backup Utility Explanation: Disk and tape devices were mixed in a list of file specifications. User Action: Reenter the command ensuring that if a list is used, the devices in a list are the same type.
INCDISABLED
incoming connections are currently disabled Facility: LAT, LAT Facility Explanation: A LAT connection attempt failed because the driver is not accepting incoming LAT connections. User Action: Enable incoming LAT connections (refer to the VMS LAT Control Program (LATCP) Manual for instructions) and retry the connection.
INCDSTQUE
inconsistent destination queue type Facility: JBC, Job Controller Explanation: The type of the specified destination queue is inconsistent with the requested operation. User Action: Specify an appropriate type of destination queue for the operation.
INCDUMPFORM
dump file format incompatible with this version of SDA Facility: SDA, System Dump Analyzer Explanation: You attempted to analyze a dump file taken under one version of the VMS operating system with an SDA image built against another version. The format of the dump file has changed between the two versions of the VMS operating system, making analysis impossible. User Action: Analyze the dump file with an SDA image built against the version of the VMS operating system that was running when the dump file was taken.
INCENTERR
error creating directory entry for 'filename' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to create a directory entry for the specified file in response to the /INCREMENTAL qualifier. User Action: Correct the condition that caused the error and reenter the command.
INCFILATR
incomplete file attribute data for 'filename' Facility: BACKUP, Backup Utility Explanation: There is an unexpected change in the file identifier and the file attribute data is incomplete for the specified file. BACKUP tried to restore a selected file from a save set, but the mounted volume did not contain the beginning of the file. User Action: Retry the BACKUP operation using the volume which contains the beginning of the selected file as input.
INCFILSPE
the /INCREMENTAL specification must have only device name Facility: BACKUP, Backup Utility Explanation: The file specification for a volume to be processed with the /INCREMENTAL qualifier must contain only a device name. User Action: Reenter the command using only the device name.
INCFORMPAR
inconsistent form parameters Facility: JBC, Job Controller Explanation: The specified length, width, and margin parameters are inconsistent. The sum of the top and bottom margins must be less than the length, and the sum of the left and right margins must be less than the width. User Action: Correct the incorrect form parameters.
INCHMK
inhibited CHMKernel trap Facility: SYSTEM, VMS System Services Explanation: An applications program attempted a system service that is inhibited to it. User Action: Ask the system manager which system services are currently inhibited and remove them from the program.
INCKWDCOM
inconsistent keyword combination Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified keyword combination is inconsistent. User Action: Specify a consistent set of keywords. Include file could not be closed Facility: EDT, EDT Editor Explanation: You specified the name of a file that EDT could not close while using the INCLUDE command. Some problem exists at the system level that prevents EDT from closing the file. User Action: After determining what system problem prevents EDT from closing the file, correct it. Include file could not be opened Facility: EDT, EDT Editor Explanation: You specified the name of a file that EDT could not open while using the INCLUDE command. Some problem exists at the system level that prevents EDT from opening the file. User Action: After determining what system problem prevents EDT from opening the file, correct it. Include file does not exist Facility: EDT, EDT Editor Explanation: You typed a file specification with the INCLUDE command for a file that does not exist. The file might exist in a directory other than the one you specified or implied with the command. Or you might have made a typographical error in the file specification. User Action: Enter the correct include file specification. Include file input record too large, truncated to 255 characters Facility: EDT, EDT Editor Explanation: EDT can handle only 255 characters on a line. The file you want to include has one or more lines in it that exceed 255 characters. EDT truncates the line to be only 255 characters long. User Action: None.
INCMEMNAM
specified shared memory name does not match Facility: SYSGEN, System Generation Utility Explanation: The logical name assigned to the shared memory by the SYSGEN command SHARE does not match the name in the database of shared memory that is specified previously. User Action: Reenter the command with the correct name.
INCMVE
incompatible management version Facility: NCP, Network Control Program Explanation: The requested function cannot be performed because the software versions at the command source and command destination are incompatible. User Action: None. The software at the command destination must be updated for the command to succeed.
INCOMPACP
indicated ACP is incompatible with 'volume' Facility: MOUNT, Mount Utility Explanation: The ACP specified is not an ACP for the requested device. User Action: Reenter the command; specify an ACP that is appropriate for the particular device type.
INCOMPAT
'input-filespec' (input) and 'output-filespec' (output) have incompatible attributes Facility: Shared by several facilities Explanation: This warning message indicates that file incompatibility may exist between files that have been appended or concatenated. This message can occur if files created by different methods are concatenated, for example, files created with the DCL command WRITE and files created by the DCL command SORT/RSX11. The command continues execution. User Action: Determine whether the incompatibility presents a problem and if it does, delete the output files, modify the format of one or more input files, and reenter the command. The format of a file can be modified by editing the file with the SOS or SLP editors and creating a new version of the file.
INCOMPAT
feature incompatible with previous system version Facility: SYSTEM, VMS System Services Explanation: This alternate success status indicates that the function requested is not compatible with the version of the I/O driver in use. This error message typically occurs when a remote terminal link is used between different versions of VMS. For example, it could indicate that the function requested by the newest version of VMS is not implemented on the previous version of VMS. User Action: Upgrade systems using remote terminals so that they use the same version of the operating system.
INCOMPAT
qualifiers incompatible with already mounted volume Facility: MOUNT, Mount Utility Explanation: A DCL command MOUNT is entered to mount a shareable volume that is already mounted; the characteristics of the volume are already established and cannot be changed. User Action: Use the DCL command SHOW DEVICE to determine how the volume is mounted. Reenter the DCL command MOUNT/SHARE without qualifiers.
INCOMPEXI
incompatible element with the same name already exists Facility: PPL, Parallel Processing Facility Explanation: All PPL objects must have unique names. User Action: Recode the call to specify a unique name.
INCOMPL
'LMB-name' not completely written in the dump file Facility: SDA, System Dump Analyzer Explanation: Information corresponding to a Logical Memory Block (LMB) is saved only partially in this subsetted dump file. The dump file may or may not be useful for analysis, depending on which LMB was only partially saved. If the SDA image retains control after the error, then some analysis is possible, but some information may not be available in the dump file. User Action: None. The dump file might not be useful for analysis.
INCOMPLETE
previous incomplete operation prevents execution Facility: JBC, Job Controller Explanation: The requested queue management operation cannot be executed because a previously requested queue management operation has not yet completed. User Action: Retry the operation at a later time. For a queue- related operation, it may be necessary to enter the STOP/QUEUE /RESET command if this error condition persists. However, for a STOP/QUEUE/MANAGER request (which may take a long time to complete), you need to wait until the request is completed.
INCOMPSHR
incompatible sharing requested Facility: RMS, VMS Record Management Services Explanation: File currently being shared is using an incompatible sharing protocol. This may occur in a mixed version cluster environment. User Action: The file being opened must be deaccessed by all current accessors using the incompatible sharing protocol to allow changing of the sharing protocol. All applications attempting to simultaneously access a file must use compatible sharing.
INCONISD
inconsistent ISD structures detected Facility: IMGACT, Image Activator Explanation: Either an image section descriptor is found to cross an image header block boundary, or there is an indication that an ISD would be found in the next header block and there is no such ISD. This usually indicates a corrupted or invalid image. User Action: Relink the image.
INCONQUALS
qualifier /'qualifier' contradicts qualifier /'qualifier' Facility: BACKUP, Backup Utility Explanation: The two qualifiers specified are in conflict with one another and cannot be used together in the BACKUP command. User Action: Reenter the BACKUP command with only one of the two qualifiers. For more information on how qualifiers affect the BACKUP command, see the VMS Backup Utility Manual.
INCONSDEV
inconsistent device types Facility: MOUNT, Mount Utility Explanation: Both disks and magnetic tapes appear in the list of devices to be mounted. User Action: Specify one or the other and reenter the command; check the logical name assignments.
INCONSTATE
inconsistent UBA database Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INCONSTATE
internal consistency state; please submit an SPR with SYS$SYSROOT:[SYSEXE]AUDIT_SERVER.DMP Facility: AUDSRV, Audit Server Explanation: An internal consistency error has occurred in the audit server process. User Action: Please submit a Software Performance Report (SPR) and include the process dump file SYS$SYSROOT:[SYSEXE]AUDIT_ SERVER.DMP, if one exists.
INCPTREF
increment page table reference count error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INCQUETYP
inconsistent queue type Facility: JBC, Job Controller Explanation: The type of the specified queue is inconsistent with the requested operation. User Action: Specify an appropriate type of queue for the operation.
INCQUOTA
QUOTA.SYS indicates 'n' blocks used, actual use is 'n' blocks for ['uic'] Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: Disk usage for the specified UIC, as recorded in the quota file, does not agree with the actual disk usage. User Action: None. The utility corrects the quota file.
INCRVN
incorrect relative volume mounted on 'device-name' Facility: BACKUP, Backup Utility Explanation: Either the wrong volume of a multivolume disk save- set was mounted, or the positional order of the devices in the input specification does not agree with the relative volume numbers recorded on the volumes. User Action: Locate and mount the correct volume.
INCSEGTRA
incomplete segmented transfer request posted Facility: SYSTEM, VMS System Services Explanation: A driver returned a success status but failed to complete the current segment of a segmented transfer. User Action: If this error can be reliably reproduced, the media and program producing the error should be submitted with a Software Performance Report (SPR).
INCSETCNT
incorrect number of devices in input specification Facility: BACKUP, Backup Utility Explanation: The number of devices in the input specification does not agree with the volume set count recorded on relative volume 1. User Action: Reenter the command with the correct number of devices.
INCSHAMEM
system disk membership inconsistency Facility: INIT, INITIALIZE Command Explanation: The boot device is not currently a source member of the shadow set. One or more of the shadow set members named in the storage control block (SCB) of the boot device is inaccessible. User Action: None.
INCVOLLABEL
incorrect volume label Facility: SYSTEM, VMS System Services Explanation: The label specified does not match the label on the volume. User Action: Verify that the correct volume is mounted; verify the label entered. Repeat the request specifying the correct volume label or specifying OVERRIDE:ID, which requires either that you have the volume protection privilege or that you are the volume owner.
INDEX
invalid index file position Facility: INIT, INITIALIZE Command Explanation: The block specified for the position of the index file for a disk volume is larger than the number of blocks on the disk. The DCL command INITIALIZE cannot write the index file. User Action: Reenter the command; specify a position for the index file that is within the range of blocks on the volume.
INDEXERR
index error in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: Possible causes of the error are: o An error occurred while searching or traversing the index o A VMS RMS error occurred o Not enough virtual memory is available User Action: Compress the library before reentering the command string.
INDEXOVFL
index area overflow in section - please submit SPR Facility: MESSAGE, Message Utility Explanation: An internal error in the compiler was detected. User Action: Submit a Software Performance Report (SPR).
INDEXTYPE
array index data type, 'type', unsupported Facility: VAXTPU, VAX Text Processing Utility Explanation: The data type of the array index is not supported. User Action: Use only integers for array indexing.
IND_OVR
indexed output file must already exist Facility: SORT, Sort/Merge Utility Explanation: You specified indexed output file organization, but the file did not already exist. User Action: First create the indexed file with the RMS Define Utility. The primary key of the file should be the same as the sort key for efficiency, but is not required.
INHCHME
inhibited CHMExecutive trap Facility: SYSTEM, VMS System Services Explanation: An applications program attempted a system service that is inhibited to it. User Action: Ask the system manager which system services are currently inhibited and remove them from the program.
INI
improperly nested: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: Your conditional DSR commands (.IF/.IFNOT and .ELSE /.ENDIF) are improperly matched. User Action: Correct the DSR commands so they match.
INIACC
failed to access initialization file Facility: REM, Set Host Facility Explanation: An error occurred in opening the initialization file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
INIALRPRO
DECthreads initialization is already in progress Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A call was made to the DECthreads initialization routine cma_init while DECthreads was still trying to initialize itself on a prior call. DECthreads initialization must complete before any DECthreads routines are used. Once DECthreads is fully initialized, all calls to cma_init complete successfully. User Action: Remove the offending concurrent call to the cma_ init routine or delay it until the first call to cma_init has completed.
INIERR
error writing to initialization file Facility: REM, Set Host Facility Explanation: An error occurred in writing to an initialization file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
INITERR
error initializing 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: An error occurred initializing the specified library. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
INITERR
error initializing 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: There is insufficient virtual memory available. User Action: Ask the system manager to increase your page file quota or VIRTUALPAGECNT.
INITFAIL
job controller initialization failure Facility: JBC, Job Controller Explanation: This message typically indicates that the system is improperly configured. The accompanying message provides more information. User Action: Use AUTOGEN to reconfigure the system. If the problem does not seem to be associated with the system's configuration, submit a Software Performance Report (SPR) and include SYS$SYSTEM:JBC$JOB_CONTROL.DMP plus any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_ CONTROL username.
INITPRS
error code of 'xx' on command line parse init Facility: PATCH, Patch Utility Explanation: A CLI callback failure occurred due to the error represented as xx. User Action: Submit a Software Performance Report (SPR).
INM
illegal number value: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The parameter value is too large, too small, invalid, or not a number. User Action: Check to see that the value is formatted properly.
INOVNORCV
expected integer overflow exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate arithmetic exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
INPBUFOVR
input buffer overflow is detected Facility: DTK, DECtalk Facility Explanation: An input buffer overflow malfunction occurred after the DECtalk device was turned on. User Action: Check the DECtalk hardware.
INPCONERR
input conversion error Facility: OTS, General Purpose Facility Explanation: There is an invalid character in the input string. Or the output value is not within the range of destination data type. User Action: Correct the input string or change the destination data type.
INP_FILES
too many input files Facility: CONVERT, Convert Utility Explanation: You listed more than 10 input files. User Action: Reduce the number of input files or combine them so that you list no more than 10.
INP_FILES
too many input files specified Facility: SORT, Sort/Merge Utility Explanation: You listed more than 10 input files. User Action: Reduce the number of input files or combine them so that you list no more than 10.
INPSTRTRU
input string truncated Facility: LIB, Library Facility Explanation: An input string accepted by LIB$GET_INPUT was truncated to fit the string descriptor passed to it. This message is associated with a status code returned from a Run-Time Library procedure and is not normally displayed by the operating system. User Action: Correct your program by increasing the field length in the descriptor.
INPTOOLON
input string is too long Facility: SMG, Screen Management Facility Explanation: The length of an input string exceeded 255 characters. User Action: Shorten the string to fewer than 255 characters.
INPUT
'filename', 'n' selected, 'n' rejected, 'n' skipped Facility: ERF, Error Log Utility Explanation: This message reports the input file name and the number of entries selected, rejected, or skipped from the input file. User Action: None.
INPUT
'filespec', 'n-records' selected, 'n-records ' rejected Facility: ACCOUNTING, Accounting Utility Explanation: This informational message is displayed when the /LOG qualifier is used. It describes how many records were selected and/or rejected for each input file. User Action: None. Input file could not be closed Facility: EDT, EDT Editor Explanation: EDT could not close the input file that you named in your EDIT/EDT command line or in the line mode INCLUDE command line. Some problem exists at the system level that prevents EDT from closing the file. User Action: After determining what system problem prevents EDT from closing the file, correct it. Input file could not be opened Facility: EDT, EDT Editor Explanation: Either the command contains faulty syntax or a nonexistent directory is specified. User Action: Check your command syntax. Ensure that any directory specified exists. Reenter the command using the correct syntax. Input file does not exist Facility: EDT, EDT Editor Explanation: The input file is not contained in the specified directory. When you are creating a new file using the EDT editor, this message is displayed indicating the creation of a new file. User Action: No action is necessary if you are creating a file. If you are editing an existing file, ensure that you have typed the file specification correctly and reenter the command. Input file does not have standard text file format Facility: EDT, EDT Editor Explanation: You edited a file that does not have standard file attributes (for example, a file that does not have carriage returns at the ends of lines). User Action: This message is only a warning. EDT allows you to edit the file, but be aware that difficulties can arise if you attempt to edit the nonstandard elements. Input record too large, truncated to 255 characters Facility: EDT, EDT Editor Explanation: A record in the input file exceeds 255 characters. User Action: Modify the record in the input file to contain 255 characters or less. This message can also occur due to an attempt to edit a file that does not contain ASCII text.
INPUT_CANCELED
input request canceled Facility: VAXTPU, VAX Text Processing Utility Explanation: Terminal input indicates that the input request was canceled. User Action: None. This is an internal status.
INPUTERR
error opening primary input file SYS$INPUT Facility: LOGIN, Login Processor Explanation: An error occurred while trying to open SYS$INPUT. An accompanying message will provide more information. User Action: Correct the problem described by the accompanying message, and try again.
INSCLIMEM
insufficient CLI memory Facility: LIB, Library Facility Explanation: The CLI could not obtain enough virtual memory to perform the function. This may be caused by having too many symbols defined. User Action: Delete some symbol definitions. Then retry the operation.
INSCOLL
not enough collections for summary processing Facility: MONITOR, Monitor Utility Explanation: An error occurred during summary processing. For summary processing to take place, at least two collections must be completed. User Action: This error may occur if you interrupt (by typing Ctrl/C) a summary request before the second collection has been completed. Reenter your command and allow at least two collections to be completed.
INSDFAIL
the installation of a product has failed. Facility: VMSINSTAL, Install Procedures Explanation: An error occurred in an attempt to defer callbacks during the installation. User Action: Examine the console output to determine the cause of the error. If you are unable to resolve the problem, contact the Digital Services Group.
INSEF
insufficient event flag Facility: LIB, Library Facility Explanation: A call is made to LIB$GET_EF to allocate an event flag number, but all event flag numbers were unavailable. User Action: Use LIB$FREE_EF to free previously allocated event flag numbers if they are no longer being used.
INSERTED
module 'module-name' inserted in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This success message is generated by the DCL command LIBRARY. User Action: None.
INSERTERR
error inserting 'module-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. One of the following conditions prevented the DCL command LIBRARY from inserting the specified modules into the library: o The modules are not formatted correctly. o The organization of the input file is incorrect. o A VMS RMS error has occurred. o There is not enough virtual memory. User Action: Correct the error and insert the file.
INSFAIL
the installation of 'product-name' has failed. Facility: VMSINSTAL, Install Procedures Explanation: The installation failed. User Action: Examine the console output to determine the cause of the error. If you are unable to resolve the problem, contact the Digital Services Group.
INSFANL
insufficient data in Definition and/or Analysis files Facility: FDL, Edit/FDL Utility Explanation: EDIT/FDL is executing an optimize script invoked by the /NOINTERACTIVE qualifier. Certain information about the file is missing from the definition or the analysis file. User Action: Supply the missing information by reexecuting the ANALYZE/RMS_FILE/FDL command to produce another analysis file and /or use the analysis file as the definition file.
INSFARG
insufficient call arguments Facility: SYSTEM, VMS System Services Explanation: A system service argument list contained fewer than the required number of arguments for the service. User Action: Check for a programming error. Refer to the VMS System Services Reference Manual for coding specifications.
INSFBUFDP
unable to allocate a buffered datapath Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned from a request to an LPA11-K interface device. A UBA- buffered data path is not available for allocation. User Action: Rerun the program.
INSFCDT
insufficient CDT entries Facility: SYSTEM, VMS System Services Explanation: There is currently an insufficient number of connection descriptor table entries for completing a request. User Action: Attempt your request at a later time.
INSFMAPREG
insufficient map registers Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned from a request to an LPA11-K interface device to initialize the LPA11-K or start data transfer. Insufficient UNIBUS adapter (UBA) map registers are available to map the command table or buffer areas. User Action: If the map registers were preallocated when the drive is loaded, increase the preallocation.
INSFMEM
insufficient dynamic memory Facility: SYSGEN, System Generation Utility Explanation: There is not enough room in the nonpaged pool to load a driver or create a control block for it. If this message is associated with a vector disabled (VECDIS) status code, the current process has issued a vector instruction, but insufficient system nonpaged dynamic memory exists to establish the process as a vector consumer. User Action: Reboot the system, stopping in SYSBOOT, and increase the value of the parameter NPAGEDYN.
INSFMEM
insufficient dynamic memory Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: A command or image exhausted the system pool of available dynamic memory and the system cannot complete the request. Or, the system manager did not allocate enough dynamic memory. User Action: Check for a programming error; this status code can be returned from a system service request when the image has disabled resource wait mode. Notify the system manager if insufficient memory is allocated.
INSFMEM
insufficient good memory to continue Facility: VAXCLUSTER, VAXcluster Facility Explanation: Too little memory on the satellite is available for bootstrap execution. User Action: Check that the configuration matches the minimum guidelines in the Software Product Description (SPD). If they do not match, add more memory. Run diagnostics on memory to verify that all the system memory is functional.
INSFPRM
missing command parameters - supply all required parameters Facility: CLI, Command Language Interpreter (DCL) Explanation: A command cannot be executed because one or more required parameters are missing from the command. With the DCL command interpreter, this message occurs only during the execution of command procedures; at the interactive level, the command interpreter continues to prompt until all required parameters are entered. User Action: Correct the command procedure.
INSFRAME
insufficient call frames to unwind Facility: SYSTEM, VMS System Services Explanation: An unwind request specified a depth that is greater than the number of call frames on the stack. User Action: Check for a programming error.
INSFSPTS
insufficient SPTs to map process buffer to system Facility: SYSTEM, VMS System Services Explanation: There are insufficient system page table entries to map a process buffer to the system. User Action: Reboot the system and increase the SYSGEN parameter SPTREQ.
INSFVM
unable to obtain virtual memory Facility: EVL, Event Logger Explanation: A program or system configuration problem exhausted virtual memory. User Action: Check the value of the VIRTUALPAGECNT using SYSGEN. If the value is 2048 or greater, then this message indicates a program problem.
INSFWSL
insufficient working set limit Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: A command or image cannot execute because the current working set limit for the process is less than the number of pages that must be resident in memory at the same time for an image to execute. User Action: Check for a programming error; verify that the number of pages requested in a system service request is accurate. If the number of pages is accurate, try to increase the size of the working set limit with the DCL command SET WORKING_SET and retry the program. If this message is associated with a vector disabled (VECDIS) status code, the process's current working set list limit does not allow its mainline vector state to be resident in memory.
INSKIPPED
unreasonable instruction stream - 'n' bytes skipped Facility: SDA, System Dump Analyzer Explanation: SDA cannot decode a range of memory locations into VAX MACRO instruction format because the locations do not begin on an instruction boundary. User Action: None. SDA ignores the bytes it cannot translate.
INSLUN
insufficient logical unit numbers Facility: LIB, Library Facility Explanation: A call is made to LIB$GET_LUN to allocate a logical unit number, but all logical unit numbers were unavailable. User Action: Use LIB$FREE_LUN to free previously allocated logical unit numbers if they are no longer used.
INSNFREPAG
insufficient nonfree pages Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INSOPRND
missing instruction operand Facility: PATCH, Patch Utility Explanation: One or more operands were omitted from the instruction. User Action: Add the required number of operands and retry the operation.
INSQUOCRE
insufficient quota to create a subprocess Facility: SMG, Screen Management Facility Explanation: The current BYTLM or PRCLM quota value is too small to create a subprocess. User Action: Increase the quota value for BYTLM or PRCLM or for both.
INSRES
insufficient resources to complete operation Facility: LAT, LAT Facility Explanation: The system does not have enough resources to service the user request. User Action: Contact the system manager to determine which system resource is inadequate.
INSSWPFIL
insufficient swap file space Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.) Insufficient memory Facility: EDT, EDT Editor Explanation: There is insufficient memory to complete the last command. This message can occur when you define a new text buffer or use the EDT command DEFINE KEY. User Action: Exit from EDT and restart your editing session. To avoid this problem in the future, define fewer keys and text buffers or decrease the size of the text buffers. Insufficient Non-paged Pool for Initialization Facility: VAXport, VAXport Driver Explanation: The port driver will not attempt to start the port. User Action: Increase the NPAGEDYN pool SYSGEN parameter and reboot the system. Insufficient Non-paged Pool for Virtual Circuits Facility: VAXport, VAXport Driver Explanation: After finding that insufficient memory resources are available for normal communication, the port driver breaks a virtual circuit. User Action: Increase the NPAGEDYN pool SYSGEN parameter and reboot the system.
INSUFFMEM
dump file contains less than 512K of memory Facility: SDA, System Dump Analyzer Explanation: The information in the first block of the dump file indicates that less than 512K of memory information was saved in the dump file. The dump file contents are assumed to be invalid, since all the VMS operating systems require more than 512K of memory to boot. User Action: None. The dump file is not useful for analysis.
INSUFPAT
'nn' bytes requested, patch area at 'addr' contains 'nn' bytes Facility: PATCH, Patch Utility Explanation: The user-defined patch area is not large enough to accommodate the specified code. User Action: Use an alternate patch area, for example, the default patch area. Generally, the default patch area is expandable.
INSVIRMEM
insufficient virtual memory Facility: MACRO, VAX MACRO Assembler Explanation: The module being assembled has too many symbols and macro definitions for the virtual memory available or a macro definition called itself (a recursive definition). The assembler terminated the assembly. User Action: Increase the virtual memory available by contacting the system manager; reduce the level of macro nesting; split the module into several smaller modules; or eliminate the recursive macro definition.
INSVIRMEM
insufficient virtual memory Facility: Shared by several facilities Explanation: An attempt to allocate additional memory for working storage failed. User Action: Purge or delete files to free space in memory.
INSVIRMEM
insufficient virtual memory Facility: STR, String Manipulation Facility Explanation: An attempt is made to allocate heap storage for use as dynamic strings, or string temporaries failed. User Action: If you allocate space by calling STR$GET1_DX or LIB$GET_VM, verify, when you finish using the storage, that the storage is released by calling STR$FREE1_DX or LIB$FREE_VM, respectively. If you are using a high-level language and have not directly allocated space, you can cause this error by having a large number of long strings. In this case, make sure to reduce strings to zero length when they are not in use.
INSVIRMEM
insufficient virtual memory available Facility: FDL, Create/FDL Utility Explanation: insufficient virtual memory available for parsing a complex FDL file. User Action: Reduce the complexity of the FDL file or have the system manager increase the available virtual memory. If this does not solve the problem, submit a Software Performance Report (SPR) and include the FDL file.
INSVIRMEM
insufficient virtual memory available Facility: PPL, Parallel Processing Facility Explanation: The calling service does not have sufficient available space to complete the request. User Action: If you use extensive PPL services, try specifying a larger value to PPL$INITIALIZE. Otherwise, check your system quotas to see if more space is needed.
INSVIRMEM
insufficient virtual memory - DIF aborted Facility: DIFF, DIFFERENCES Command Explanation: The Differences Utility has run out of virtual memory for one of the following reasons: (1) the Differences Utility encountered a difference section that contains more records than can be stored in virtual memory, or (2) the Differences Utility ran out of virtual memory while storing records away to be used while generating additional listings. User Action: In the first case, cut down the size of the offending difference section; the listing will have terminated in the middle of the section. You can do this by increasing the value of the /WINDOW parameter if it is not being defaulted. In the second case, rerun the Differences Utility and generate one listing at a time.
INSVIRMEM
insufficient virtual memory for 'number' pages for cluster 'cluster- name' Facility: LINK, Linker Utility Explanation: The linker could not allocate enough virtual memory in the resulting image to contain a cluster. User Action: Determine why the linker ran out of virtual memory by consulting a /FULL map, correct, and relink.
INSWAPERR
inswap read error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INTDATCOR
internal data corrupted in run-time library Facility: OTS, General Purpose Facility Explanation: In a call to the Run-Time Library, a database consistency check failed. An applications program can cause this by referring to a location outside a dimensioned array, or by requesting input from an address outside the program. User Action: Recompile any module that you think may refer outside a dimensioned array with the /CHECK=BOUNDS qualifier. Relink and rerun your program.
INTDELPRC
participant stopped by PPL$STOP Facility: PPL, Parallel Processing Facility Explanation: An application call to PPL$STOP forced the termination of this participant. User Action: Since the application itself terminated this party, any actions are application-dependent.
INTDIV
arithmetic trap, integer divide by zero at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An arithmetic exception condition occurred as a result of an attempt to divide by zero. User Action: Examine the PC location displayed in the message and check the program listing to verify that operands and variables are specified correctly.
INTEGER
please enter an integer value. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL is prompting you for an integer. User Action: Specify an integer.
INTERLOCK
unable to acquire system data structure interlock Facility: SYSTEM, VMS System Services Explanation: The system data structure interlock cannot be acquired. Another processor probably crashed while holding a data structure lock. User Action: Retry the operation, or reboot the system and reinitialize shared memory. Refer to the Guide to Maintaining a VMS System. Internal software error - please submit a Software Performance Report Facility: Shared by several facilities Explanation: A problem exists with the software as installed on your system. User Action: Submit a Software Performance Report (SPR).
INTERNALERROR
internal error caused loss of process status Facility: JBC, Job Controller Explanation: A system error prevented the queue manager from obtaining the completion status of a process. User Action: Ask your system manager to consult the operator log for messages associated with the process.
INTERR
internal logic error Facility: REM, Set Host Facility Explanation: A violation of CTERM protocol occurred. User Action: Submit a Software Performance Report.
INTHCHAR
internal error: encountered character of class h-string Facility: CDU, Command Definition Utility Explanation: CDU encountered a corrupted internal data structure. User Action: Submit a Software Performance Report (SPR). Include the CLD file in the Report (SPR).
INTINVNODE
internal error: invalid node encountered Facility: CDU, Command Definition Utility Explanation: CDU encountered a corrupted internal data structure. User Action: Submit a Software Performance Report (SPR). Include the CLD file in the Report (SPR).
INTLOGERR
internal logic error Facility: LIB, Library Facility Explanation: A LIB$ routine detected an internal logic error. This message is associated with a status code returned from the Run-Time Library. User Action: Submit a Software Performance Report (SPR).
INTNODESPACE
internal error: node space exhausted Facility: CDU, Command Definition Utility Explanation: CDU exhausted internal memory. User Action: Submit a Software Performance Report including the CLD file.
INTOVF
arithmetic trap, integer overflow at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An exception condition occurred as a result of an integer overflow. User Action: Examine the PC location displayed in the message and check the program listing to verify that operands or variables are specified correctly.
INTOVF
integer overflow Facility: LIB, Library Facility Explanation: Either the library routine or the hardware detected an integer overflow. User Action: Choose a destination data type with a larger range.
INTPATHSTKOV
internal error: path stack overflow Facility: CDU, Command Definition Utility Explanation: CDU exhausted internal memory. User Action: Submit a Software Performance Report including the CLD file.
INTRNLERR
internal error: 'code' Facility: INSTALL, Install Utility Explanation: INSTALL encountered an internal error. User Action: Submit a Software Performance Report (SPR).
INTRNLERR
LBR internal error. Please submit SPR. Facility: LBR, Librarian Subroutine Package Explanation: This is an internal consistency check. User Action: Submit a Software Performance Report that includes relevant files wherever possible.
INTSTKOV
linker internal stack of 'number' overflowed in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The linker's internal stack overflowed because of a complex calculation. User Action: Submit a Software Performance Report (SPR).
INTSTKUN
linker internal stack of 'number' underflowed in module 'module- name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module attempted to remove more items from the stack than it pushed on it. User Action: Submit a Software Performance Report for the appropriate language compiler.
INTTERMIN
participant stopped by PPL$TERMINATE Facility: PPL, Parallel Processing Facility Explanation: An application call to PPL$TERMINATE forced the temination of this participant. User Action: Since the application itself terminated this party, any actions are application-dependent.
IN_USE
object referenced is already in use Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The DECthreads operation cannot be performed on the specified object because it is already in use; for example, the routine is attempting to delete a mutex that is locked. User Action: Determine which routine caused the error and make sure the object is in an appropriate state before attempting the operation.
INVACC
invalid access control specified for the executor Facility: NCP, Network Control Program Explanation: You specified invalid or conflicting access control information for connecting to an executor node. User Action: Confirm that the access control specified is correct. Use either the standard VMS access control format (node-spec) or the NCP-specific format (USER, ACCOUNT, PASSWORD), but do not use both.
INVACCESS
error in access specification Facility: AUTHORIZE, Authorize Utility Explanation: The access specification contains a syntax error. User Action: Correct the syntax and reenter the access specification.
INVACCESS
invalid file access specified Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU error occurred. User Action: Submit a Software Performance Report (SPR).
INVACCREC
record 'record' has invalid or unrecognized format Facility: ACCOUNTING, Accounting Utility Explanation: A record in the accounting file has an invalid or unrecognized format. The ACCOUNTING Utility will attempt to continue processing records. User Action: Examine the accounting file and verify that it is a valid VMS accounting file. Check for hardware errors. Submit a Software Performance Report with the accounting file in question, if the problem persists.
INVADAP
invalid adapter name specified Facility: SYSGEN, System Generation Utility Explanation: The specified adapter number is found to be invalid after bootstrap. User Action: Reenter the command using the correct adapter number. Invalid buffer name Facility: EDT, EDT Editor Explanation: Invalid syntax is used for the buffer name in the EDT command. User Action: Reenter the EDT command specifying valid syntax for the buffer name. Invalid character Facility: EDT, EDT Editor Explanation: You attempted to insert a character by using the SPECINS function or ASC command, but did not supply a valid decimal equivalent for the character. User Action: Reenter the command specifying a valid decimal equivalent for the character. Invalid entity Facility: EDT, EDT Editor Explanation: The entity portion of the EDT change mode command is not recognized. User Action: Reenter the EDT change mode command specifying a valid entity. Invalid option for that command Facility: EDT, EDT Editor Explanation: The /OPTION qualifier is specified for an EDT command that does not accept the /OPTION qualifier. User Action: Reenter the EDT command without specifying the /OPTION qualifier. Invalid parameter for SET or SHOW Facility: EDT, EDT Editor Explanation: The EDT commands SET and SHOW do not accept one of the parameters you specified. User Action: Reenter the EDT command specifying a valid parameter. Invalid string Facility: EDT, EDT Editor Explanation: You specified a string that EDT could not handle. For example, this message occurs when you use a search string longer than 64 characters. User Action: Reenter the command specifying a valid string. Invalid subcommand Facility: EDT, EDT Editor Explanation: You have used an improper name for an EDT change mode subcommand. User Action: Use a valid name. For a list of the EDT change mode subcommands, type HELP CHANGE SUBCOMMANDS in line mode. Invalid value in SET command Facility: EDT, EDT Editor Explanation: The EDT command SET has an invalid keyword. User Action: Reenter the command specifying a valid keyword.
INVALIGN
invalid alignment Facility: MACRO, VAX MACRO Assembler Explanation: An unrecognized keyword or no integer or no keyword followed the .ALIGN directive. User Action: Correct the syntax of the .ALIGN directive.
INVALQUAL
the 'qualifier-name' is an invalid qualifier in this context Facility: BAD, Bad Block Locator Utility Explanation: The qualifier indicated is issued in an invalid context. User Action: Consult the documentation for the list of valid, nonconflicting qualifier specifications and usage in various analysis contexts.
INVARG
invalid argument Facility: DCX, Data Compression/Expansion Utility Explanation: A DCX procedure has been called with an incorrect argument. User Action: Correct the application program.
INVARG
invalid argument Facility: DTK, DECtalk Facility Explanation: The value of an argument is not in the correct range. User Action: Examine each argument. Determine which one is out of range, and correct your program.
INVARG
invalid argument Facility: PPL, Parallel Processing Facility Explanation: A specified argument is invalid. User Action: Recode the program to pass a valid argument.
INVARG
invalid argument Facility: SMG, Screen Management Facility Explanation: The value of some argument is not in the correct range. User Action: Examine each argument. Determine which one is out of range and correct your program.
INVARG
invalid arguments Facility: Shared by several facilities Explanation: This message is associated with a status code returned from the Run-Time Library. A calling program passed one or more invalid arguments to a library (LIB$) routine. User Action: Check the arguments for the call to the Run-Time Library and correct the program.
INVARGMAT
invalid argument to math library user PC location Facility: MTH, Mathematics Facility Explanation: One of the math procedures is called with an invalid argument. User Action: Locate the math procedure call that caused the error and correct the argument.
INVARGORD
invalid argument order Facility: LIB, Library Facility Explanation: The arguments were passed in an invalid order. User Action: Examine each argument. Correct the program to pass the arguments in a valid order.
INVARRDSC
invalid array descriptor Facility: PATCH, Patch Utility Explanation: The expression contained an array descriptor that PATCH did not recognize. User Action: Correct the array descriptor and retry.
INVATTSIZ
invalid attribute record size in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the attribute size field of a save set record. Data in the save set is corrupted. User Action: None. Save set data has been lost.
INVATTSTR
invalid attribute record structure level in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the structure level field of a save set record. Data in the save set is corrupted. User Action: None. Save set data has been lost.
INVATTVAL
invalid attribute record value in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in a save set attribute record. Data in the save set is corrupted. User Action: None. Save set data has been lost.
INVBJLEOF
invalid end of file position in BACKUP journal Facility: BACKUP, Backup Utility Explanation: The end-of-file pointer recorded for the journal file specified by the /JOURNAL qualifier is invalid. The journal file is corrupted and cannot be used. User Action: Reconstruct the journal file from backup media.
INVBJLSIZ
invalid record size in BACKUP journal Facility: BACKUP, Backup Utility Explanation: An invalid record size occurred in the journal file specified by the /JOURNAL qualifier. The journal file is corrupted and cannot be used. User Action: Reconstruct the journal file from backup media.
INVBJLSTR
invalid structure level in BACKUP journal Facility: BACKUP, Backup Utility Explanation: The structure level recorded in the journal file specified by the /JOURNAL qualifier is invalid. The journal file is corrupted and cannot be used. User Action: Reconstruct the journal file from backup media.
INVBJLTYP
invalid record type in BACKUP journal Facility: BACKUP, Backup Utility Explanation: An invalid record type occurred in the journal file specified by the /JOURNAL qualifier. The journal file is corrupted and cannot be used. User Action: Reconstruct the journal file from backup media.
INVBKT
invalid bucket at VBN 'number' Facility: CONVERT, Convert Utility Explanation: The Convert/Reclaim Utility has detected a structure error in the bucket specified by 'number'. User Action: Use the ANALYZE/RMS_FILE command to determine the cause of the structure error.
INVBLK
invalid RMS control block at virtual address 'hex-offset' Facility: FDL, Create/FDL Utility Explanation: FDL$GENERATE or FDL$RELEASE passed an address that is not a valid RMS control block. User Action: Correct the invalid address.
INVBLK
invalid RMS control block at virtual address 'XXXXXXXX' Facility: FDL, Edit/FDL Utility Explanation: The FDL parsing facility checks the validity of RMS blocks before deallocating them, and returns this error if a bad control block is found. User Action: Ascertain that the RMS control blocks passed to the FDL$RELEASE routine are in the same state as when they were created by the FDL$PARSE routine.
INVBLKHDR
invalid block header encountered in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the block header of a save set block. Data in the save set is corrupted. User Action: None. Save set data is lost.
INVBLKSIZE
invalid block size in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the block size field of a save set block. Data in the save set is corrupted. User Action: None. Save set data is lost.
INVBLKTYP
invalid block type in specified block Facility: SDA, System Dump Analyzer Explanation: SDA is unable to identify the block type of a particular block. The invalid block type message usually occurs when the SDA command FORMAT tries to identify a block type using a byte offset. User Action: None.
INVBLOCK
internal job controller error; invalid use of the block 'number' Facility: JBC, Job Controller Explanation: This message indicates a logic error in the job controller. User Action: None.
INVBTIMSP
invalid /BEGINNING time specification Facility: MONITOR, Monitor Utility Explanation: The value of the /BEGINNING qualifier is specified incorrectly. You must specify the time as an absolute time, plus or minus a delta time. You can omit either the absolute or the delta time; however, the delta time must always be preceded by the plus or minus sign. Whenever you use a plus sign, enclose the entire time specification in double quotes. See the VMS DCL Dictionary for more information on specifying time values. User Action: Reenter the MONITOR request with a correct value for the /BEGINNING qualifier.
INVBUFDELETE
cannot delete a permanent buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: You attempted to delete a buffer that is set as a permanent buffer. User Action: None.
INVBUSNAM
invalid Local Area VAXcluster BUS name Facility: SYSTEM, VMS System Services Explanation: An invalid BUS name was specified when calling the SYS$LAVC_START_BUS or SYS$LAVC_STOP_BUS routine. User Action: Check the BUS name to make sure it contains at least three ASCII characters to specify the LAN device to be used. For example, XQA is a valid BUS name for the device name _XQA0:. The full device name _XQA0: is also a valid BUS name.
INVCALL
invalid CALL nesting structure or data inconsistency detected
Facility: CLI, Command Language Interpreter (DCL)
Explanation: There are three possible causes for these error
messages:
o You mismatched or unpaired SUBROUTINE and ENDSUBROUTINE
commands in a command procedure.
o You used the GOSUB command with a label defined with the
SUBROUTINE command.
o You entered the command CALL, SUBROUTINE, or ENDROUTINE at an
interactive (DCL) level.
User Action: Correct the command procedure and reexecute the
program.
INVCCFIL
invalid console carrier image file Facility: MOM, Maintenance Operation Module Explanation: The image that is being accessed to downline load the console carrier code is unsupported. User Action: Use a supported image type to downline load the console carrier code.
INVCHA
invalid character Facility: LIB, Library Facility Explanation: A character is unable to be translated when converting either from ASCII to EBCDIC or from EBCDIC to ASCII. User Action: Ensure that translatable characters are used.
INVCHAN
invalid ACP channel number Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVCHANAM
invalid characteristic name Facility: JBC, Job Controller Explanation: The characteristic name specified is not syntactically valid. After logical name translation, the characteristic name must be a character string in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, or underscore (_) characters. User Action: Correctly specify the characteristic name.
INVCHANAM
'name' is an invalid characteristic name Facility: QMAN, Queue Manager Explanation: The characteristic name specified is not syntactically valid. After logical name translation, the characteristic name must be a character string in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, or underscore (_) characters. User Action: Correctly specify the characteristic name.
INVCHANUM
'number' is an invalid characteristic number Facility: QMAN, Queue Manager Explanation: The specified characteristic number is syntactically invalid. User Action: Correct the error and reenter the command.
INVCHAR
invalid character Facility: PATCH, Patch Utility and REM, Set Host Facility Explanation: The command contained an invalid character. User Action: Correct the character and reenter the command.
INVCHAR
invalid character encountered in position 'position'. It is ignored Facility: CDU, Command Definition Utility Explanation: CDU encountered an invalid character while reading from a CLD file. The invalid character is ignored. User Action: Edit the CLD file such that there are no invalid characters.
INVCHDABS
invalid command in /ABSOLUTE context Facility: PATCH, Patch Utility Explanation: The command entered is invalid when patching a file in absolute context. Use of symbol names, patch area, or ECOs is invalid when invoking PATCH with the /ABSOLUTE qualifier. User Action: Enter a valid command. If you are patching an image, invoke the Patch Utility without the /ABSOLUTE qualifier.
INVCJFIOD
invalid IO database structure (journaling) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVCLADSC
invalid class in descriptor Facility: LIB, Library Facility Explanation: An unsupported class of descriptor is specified. User Action: Retry the operation specifying a supported class of descriptor.
INVCLADTY
invalid class data type combination in descriptor Facility: LIB, Library Facility Explanation: An unsupported class and data type combination is specified. User Action: Ensure that both the class and data type specified are supported.
INVCLIFLAG
invalid CLI flag 'flag-name' encountered Facility: CDU, Command Definition Utility Explanation: CDU encountered an invalid CLI flag name while reading from a CLD file. User Action: Edit the CLD file so that all CLI flag names are valid.
INVCLSNM
class-name 'class-name' is invalid or not uniquely identified Facility: MONITOR, Monitor Utility Explanation: The specified class name is not a valid MONITOR class. This message can result from specifying a class name with too few characters to uniquely identify it. User Action: Check the list of valid MONITOR classes by entering the DCL command, HELP MONITOR parameters. Reenter the MONITOR command requesting only valid classes.
INVCMD
invalid command Facility: Shared by several facilities Explanation: Your command is invalid, either because the command parser cannot recognize the command, or because of incorrect syntax. User Action: If necessary, refer to the appropriate documentation, then reenter your command correctly.
INVCMD
invalid command Facility: LAT, LAT Facility Explanation: The specified LATCP command was invalid for the reason given in an accompanying message. User Action: Correct the situation based on the information in the accompanying message.
INVCMD
unrecognized command Facility: NCP, Network Control Program Explanation: The specified verb is invalid. User Action: Check the input command for corrections and reenter the command.
INVCOL
invalid column Facility: SMG, Screen Management Facility Explanation: An invalid column number is specified. It is either less than 0 or larger than the number of columns in the virtual display. User Action: Specify a valid column. Columns are numbered beginning with 1.
INVCOLARG
unknown color specified Facility: SMG, Screen Management Facility Explanation: An attempt is made to change the characteristics of the terminal, changing its background color to a value that is not valid. User Action: Check the symbolic name for the background color desired. Specify it correctly.
INVCOMPID
invalid component ID Facility: SYSTEM, VMS System Services Explanation: An invalid component identification (ID) value was specified in the network path description. SYS$LAVC_DEFINE_NET_ PATH returns the invalid component ID value in the buffer provided for BAD_COMPONENT_ID. User Action: A coding error occurred in the user program that passed the component ID value. Review how the component ID value was obtained and why it was placed into the network component list. Component IDs are valid only on the local system and are not valid across system boots or after calling SYS$LAVC_DISABLE_ ANALYSIS.
INVCOMPLIST
invalid component list Facility: SYSTEM, VMS System Services Explanation: The network component list used when calling SYS$LAVC_DEFINE_NET_PATH was built incorrectly. User Action: Check the network component list to make sure it contains the component identification (ID) values for two NODE components and two ADAPTER components. The first and last component ID values should correspond to NODE components.
INVCOMPTYPE
invalid component type Facility: SYSTEM, VMS System Services Explanation: An invalid component type value was passed to SYS$LAVC_DEFINE_NET_COMPONENT. User Action: Use one of the component type values defined by the macro $PEMCOMPDEF: COMP$C_NODE, COMP$C_ADAPTER, COMP$C_COMPONENT, or COMP$C_CLOUD.
INVCONT
invalid line continuation Facility: INPSMB, Input Symbiont Explanation: In a batch job entered from a card reader, a continued line is followed by a line beginning with a dollar sign. User Action: Correct the error and reenter the job.
INVCPUID
invalid CPU identification Facility: MONITOR, Monitor Utility Explanation: The CPU identification specified with the /CPU qualifier was invalid. Valid CPU identifications are integers 0-31. User Action: Correct the CPU identification specification and reenter the MONITOR command.
INVCTX
invalid context block Facility: DCX, Data Compression/Expansion Utility Explanation: A DCX procedure is called with a context variable that is invalid or with an invalid or corrupted context area. This problem may be caused by failure to call the appropriate routine to initialize the context variable or by an application program error. User Action: Correct the application program.
INVCTXTYP
symbol specified is defined for a different context type Facility: CLI, Command Language Interpreter (DCL) Explanation: You must use a symbol that has a type required by the lexical function you are using. User Action: Refer to the documentation of the lexical function for more information.
INVCVT
invalid conversion Facility: LIB, Library Facility Explanation: The source value is negative and the destination data type is unsigned. User Action: Ensure that the source value is positive and the destination data type is signed.
INVDATA
invalid data presented for expansion or bounded compression
Facility: DCX, Data Compression/Expansion Utility
Explanation: Two possible causes exist:
o DCX$COMPRESS_DATA is called to compress a data record that is
not presented to DCX$ANALYZE_DATA when a bounded compression
function had been requested.
o DCX$EXPAND_DATA is called to expand a compressed data record
that is truncated or corrupted in some fashion.
User Action: Correct the application program.
INVDATIM
invalid date/time in statement 'number' Facility: FDL, Create/FDL Utility Explanation: An invalid date or time is included in the specified statement. User Action: Correct the invalid date or time in the specified statement in the FDL file.
INVDATIM
invalid date/time in statement 'xxx' Facility: FDL, Edit/FDL Utility Explanation: The date or time specified to the FDL parser is incorrectly formed. User Action: Verify that the syntax of the date and time is correct. The valid format is that of the SYS$BINTIM system service.
INVDEF
'directory spec' does not exist Facility: CLI, Command Language Interpreter (DCL) Explanation: You set your default to a nonexistent directory using the SET DEFAULT command and then entered the SHOW DEFAULT command. User Action: Set default to a valid directory and reenter the SET DEFAULT command.
INVDEFATT
invalid key-definition attributes Facility: SMG, Screen Management Facility Explanation: When a key is defined, attributes such as NOECHO may be specified with the definition. An attempt is made to specify an unknown attribute. User Action: Check the list of valid attributes and correct your program.
INVDEFINE
invalid DEFINE statement Facility: CDU, Command Definition Utility Explanation: CDU encountered an invalid DEFINE statement in a CLD file. Valid keywords for the DEFINE statement are: VERB, SYNTAX, and TYPE. User Action: Edit the CLD file so that the DEFINE commands contain proper syntax.
INVDELIM
invalid delimiter Facility: STR, String Manipulation Facility Explanation: The delimiter string passed to STR$ELEMENT is longer than a single character. User Action: Examine the delim_dec argument and make corrections.
INVDESC
invalid descriptor Facility: PPL, Parallel Processing Facility Explanation: The descriptor is invalid. User Action: Recode your program to correct the descriptor.
INVDEV
device is invalid for requested operation Facility: SET, SET Facility Explanation: The device type that is specified for the operation is not allowed in the particular operation. For example, the user enters the command SET DEVICE/SERVED CSA1 to serve the console floppy which is not allowed. User Action: Make sure that the device meets all of the requirements for the operation.
INVDEV
device name too long to add trailing ":" Facility: AUTHORIZE, Authorize Utility Explanation: You specified a device name with more than 15 characters. User Action: Limit the device name to 15 characters.
INVDEVICE
invalid device 'device-name' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An invalid device is specified in the command. User Action: Reenter the command specifying a valid device. The specification must reference a disk device and must not contain any file specification components other than a device name.
INVDEVICE
invalid device 'xxxxxx' specified Facility: SYSMAN, Cluster System Management Utility Explanation: The device indicated does not exist on the target system. If 'xxxxxx' is a logical name, then the translation of that logical name is not a valid device on the target system. User Action: Specify a valid device.
INVDEVTYP
invalid backup device type 'filespec' Facility: BACKUP, Backup Utility Explanation: The specified device must be a disk or tape device. User Action: Reenter the command.
INVDIR
invalid directive Facility: SMG, Screen Management Facility Explanation: The termtable compiler accepts only a few FAO directives. It encountered one that it does not process. User Action: Check your terminal definition. Make sure that you use only valid FAO directives.
INVDIS_ID
invalid display-id Facility: SMG, Screen Management Facility Explanation: An invalid display identifier is specified. User Action: Make sure you are passing the display identifier by reference, not by value. Ensure that the display id is previously set up by a call to SMG$CREATE_VIRTUAL_DISPLAY.
INVDPT
invalid driver image - DPT$_TYPE, VBN 2 .NEQ.DYN$C_DPT
Facility: SYSGEN, System Generation Utility
Explanation: The driver image file specified in a SYSGEN command
LOAD, RELOAD, or CONNECT did not pass a basic validity check. This
error can be caused by one of the following conditions:
o Not having the driver prologue table (DPT) as the first code-
generating component of the driver
o Not linking the driver as an executable image based at zero
o Having PSECT statements in the driver program
o Any other problem that causes the driver prologue table not to
be in the second block (VBN 2) of the image file
User Action: Correct the driver code and reenter the command.
INVDPTINI
invalid driver prologue init table value
Facility: SYSGEN, System Generation Utility
Explanation: One of the following conditions exists:
o The initialization or reinitialization entry in the driver
prologue table has an invalid control block type code, that is,
one other than DDB, UCD, CRB, or IDB.
o The initialization or reinitialization entry in the driver
prologue table has an invalid store function, that is, one
other than B, W, L, R, V, @B, @W, @L, @R, or @V.
User Action: Correct the DPT_STORE macro in the driver prologue
table.
INVDSTQUE
invalid destination queue Facility: JBC, Job Controller Explanation: The destination queue name specified is not syntactically valid. After logical name translation, the destination queue name must be a character string in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, and underscore (_) characters. User Action: Correctly specify the destination queue.
INVDSTREC
invalid DST record Facility: PATCH, Patch Utility Explanation: An invalid Debug Symbol Table record is encountered. This can be caused by a DEPOSIT to a random location or it can be a compiler error. User Action: Submit a Software Performance Report unless the applications program or a DEPOSIT command has altered a Debug Symbol Table record.
INVDSTREC
unimplemented delta-PC command in symbol table Facility: TRACE, Traceback Facility Explanation: A language processor has created a PC-to-line-number record that the traceback facility has not implemented. The symbol table information is either incorrect or is not known to the traceback facility. User Action: Submit a Software Performance Report (SPR).
INVDTYDSC
invalid data type in descriptor Facility: LIB, Library Facility Explanation: An unsupported data type is specified. User Action: Retry the operation specifying a supported data type.
INVELEID
invalid element ID Facility: PPL, Parallel Processing Facility Explanation: The specified element ID is not valid. User Action: Examine the program code. Some modification of the element ID occurred.
INVELENAM
invalid element name Facility: PPL, Parallel Processing Facility Explanation: An invalid character string is detected. User Action: Specify a valid character string.
INVELETYP
invalid element type for requested operation Facility: PPL, Parallel Processing Facility Explanation: You specified an element type that cannot be used by the called routine. User Action: Recode the program to pass a valid element type.
INVETIMSP
invalid /ENDING time specification Facility: MONITOR, Monitor Utility Explanation: The value of the /ENDING qualifier is specified incorrectly. You must specify the time as an absolute time plus or minus a delta time. You can omit either the absolute or the delta time; however, the delta time must always be preceded by the plus or minus signs. Whenever you use a plus sign, enclose the entire time specification in double quotes. See the VMS DCL Dictionary for more information on specifying time values. User Action: Reenter the MONITOR request with a correct value for the /ENDING qualifier.
INVEVE
invalid event range Facility: NCP, Network Control Program Explanation: The range of event types is invalid. User Action: Reenter a valid event list.
INVEXCEPTN
exception while above ASTDEL or on interrupt stack Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVEXHLIST
termination handler control block list is corrupted Facility: SYSTEM, VMS System Services Explanation: The list of exit handler control blocks is in an inconsistent state, either because the same exit handler is declared more than once or because user code has minpulated one of the list pointers. User Action: The program is in error. Change the source code that is incorrectly manipulating the termination handler control block list.
INVEXP
invalid expression Facility: SMG, Screen Management Facility Explanation: The termtable compiler encountered an invalid arithmetic expression. User Action: Check your definition. Make sure that you have used only valid operators and operands in your expressions.
INVEXTBACK
file ('file-id') 'filename' invalid extension file header back link
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The back link in an extension file header for the
specified file does not point to the primary file header.
User Action: None. The utility changes the back link to point to
the primary file header.
INVEXTFID
file ('file-id') 'filename' invalid extension file header forward
link
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The forward link in a file header to the next
extension file header does not point to a valid file header.
User Action: Examine and delete the file. If possible, reconstruct
the file from backup media.
INVEXTHDR
file ('file-id') 'filename' invalid extension file header sequence
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The sequence numbers in the extension file headers
for the specified file are not correct. The sequence number should
increase by one in each extension file header.
User Action: The link that points to the erroneous extension file
header is cleared. Part of the file cannot be accessed by the
operating system. You should delete the file and, if possible,
reconstruct it from backup media.
INVFAOPARAM
FAO parameter 'integer' must be string or integer Facility: VAXTPU, VAX Text Processing Utility Explanation: The FAO built-in procedure allows only string and integer arguments. User Action: Specify string and integer arguments only to the FAO built-in procedure.
INVFCBDESC
descriptor in $FCB for 'address' improperly initialized Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU error occurred. User Action: Submit a Software Performance Report (SPR).
INVFCO
invalid file contents, 'filename' Facility: NCP, Network Control Program Explanation: Your command could not access the file, because the file's contents are invalid. An accompanying VMS RMS message should identify the reason why the file contents are invalid. User Action: Take corrective action based on the accompanying VMS RMS message.
INVFID
invalid file id in save set - cannot restore /IMAGE Facility: BACKUP, Backup Utility Explanation: An attempt is made to restore a file with a zero file identification in /IMAGE mode. This may occur if the save set is written by a non-VMS system. User Action: Use a non-/IMAGE mode to restore the file.
INVFILEXT
invalid file extension linkage in 'filespec' Facility: BACKUP, Backup Utility Explanation: The specified save set file has an invalid pointer to a following segment of the file. The remainder of the file is not accessible. User Action: Attempt to recover data by beginning a restore operation with the first unprocessed file segment.
INVFILSPE
boot file specification too long Facility: VAXCLUSTER, VAXcluster Facility Explanation: You specified an invalid load assist parameter with the system root specification. User Action: Shorten the file specification for the system root.
INVFILSPE
input or output file specification too long - shorten Facility: CLI, Command Language Interpreter (DCL) Explanation: A file specification is invalid. User Action: Reenter the command, specifying a valid file specification.
INVFILSPE
invalid file specification Facility: LIB, Library Facility Explanation: An invalid file specification is specified in a CREATE/DIRECTORY, SET PROTECTION, RENAME, or UNLOCK command. User Action: Refer to the VMS DCL Dictionary and reenter the command.
INVFILSPE
invalid file specification 'filespec' Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command Explanation: The specified file specification is invalid. Files submitted to a batch or print job must be disk files. User Action: Correct the error and reenter the command.
INVFLUSHSP
invalid /FLUSH_INTERVAL specification Facility: MONITOR, Monitor Utility Explanation: The value of /FLUSH_INTERVAL must be an unsigned contiguous string of decimal digits forming a value in the range of 1 to 9,999,999, inclusive. User Action: Reenter the MONITOR request and specify a valid value for /FLUSH_INTERVAL.
INVFORNAM
invalid form name Facility: JBC, Job Controller Explanation: The form name specified is not syntactically valid. After logical name translation, the form name must be a character string whose length is in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, and underscore (_) characters. User Action: Correctly specify the form name.
INVFORNAM
'name' is an invalid form name Facility: QMAN, Queue Manager Explanation: The form name specified is not syntactically valid. After logical name translation, the form name must be a character string whose length is in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, and underscore (_) characters. User Action: Correctly specify the form name.
INVFORNUM
'number' is an invalid form number Facility: QMAN, Queue Manager Explanation: The specified form number is syntactically invalid. User Action: Correct the error and reenter the command.
INVFUNC
invalid function (valid choices are: SAVE, RESTORE, TEST, COMPARE) Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An invalid function was requested for the queue upgrade utility. User Action: Enter one of the valid function choices.
INVFUNCOD
invalid function code Facility: JBC, Job Controller Explanation: The $GETQUI, $SNDACC, $SNDJBC, or $SNDSMB function code is invalid. User Action: Identify and correct the incorrect function code.
INVGBLSELDATA
the selected data cannot be processed Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU cannot process the data of the selected region. User Action: Select 8-bit uniform font text when pasting the global selection into VAXTPU.
INVGOSUB
invalid use of the GOSUB command Facility: CLI, Command Language Interpreter (DCL) Explanation: You entered the GOSUB command in an environment other than a command procedure. This command is invalid in interactive mode. User Action: Use the GOSUB command only in command procedures.
INVHEADER_BUSY
invalid file header marked "busy" in index file bitmap Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message is issued along with the BADHEADER message and gives a more detailed reason why the specified file header is corrupt. In this case, the file header is corrupt (for reasons given in other messages) but the index file bitmap indicates that the file header is busy. User Action: None. See the BADHEADER message.
INVHOMBLK
'device-name' has invalid home block Facility: BACKUP, Backup Utility Explanation: The specified volume has an invalid Files-11 home block. User Action: Repair the volume using the Analyze/Disk_Structure Utility.
INVIDE
invalid identification, 'component-id' Facility: NCP, Network Control Program Explanation: The format of a component identifier is incorrect, or the KNOWN component keyword is used where it is not valid. The 'component-id' will identify the invalid identification. User Action: Check the syntax rules for component identifiers and reenter your command with the correct syntax.
INVIFNEST
invalid IF-THEN-ELSE nesting structure or data inconsistency Facility: CLI, Command Language Interpreter (DCL) Explanation: An IF-THEN-ELSE statement is incorrectly structured. User Action: Modify your command procedure using the correct IF- THEN-ELSE structure. Check for inconsistent data types.
INVIMGHDR
inconsistent debug and symbol data in image header Facility: PATCH, Patch Utility Explanation: The image header inconsistently describes the symbol information causing the absence of symbol information at PATCH time. User Action: Relink the image. If the problem persists, submit a Software Performance Report (SPR).
INVINPDMN
invalid input domain Facility: CDA, Compound Document Architecture Explanation: An invalid input domain was specified for the front end. Only DDIF and DTIF are supported as domains. User Action: Currently, DDIF and DTIF are the only input domains supported.
INVINPFIL
the /INPUT file is not a valid MONITOR recording file Facility: MONITOR, Monitor Utility Explanation: The file specified with the /INPUT qualifier is not a MONITOR recording file. When MONITOR creates a recording file, identification information is stored in the header record; this information is then verified when the file is used for input. The file specified on this MONITOR request failed the verification. User Action: Reenter the MONITOR request, specifying a valid MONITOR recording file with the /INPUT qualifier.
INVINPUT
invalid input format in file 'filename' Facility: DSR, DIGITAL Standard Runoff Explanation: The format of the input file is incorrect. User Action: Correct the format of the input file.
INVINTSP
invalid /INTERVAL specification Facility: MONITOR, Monitor Utility Explanation: The /INTERVAL qualifier value must be an unsigned contiguous string of decimal digits forming a value in the range of 1 to 9,999,999 inclusive. User Action: Reenter the MONITOR request, specifying a valid /INTERVAL qualifier value.
INVIOCODE
invalid operation code passed to an I/O operation Facility: VAXTPU, VAX Text Processing Utility Explanation: An invalid request is passed to enter the file operation routine or the terminal input routine provided by VAXTPU. User Action: If you are using the callable interface, correct your program. If you are not using the callable interface, a software error has occurred. In such a case, please submit a Software Performance Report describing the conditions that lead to the error.
INVITEM
invalid item code or list Facility: DCX, Data Compression/Expansion Utility Explanation: DCX$ANALYZE_INIT is called with either an incorrect number of arguments (the number must be odd) or an unknown item code argument. User Action: Correct the application program.
INVITEM
invalid item 'item-name' encountered. Some text will be skipped Facility: CDU, Command Definition Utility Explanation: CDU encountered an unexpected item while reading from a CLD file. The unexpected item is ignored. User Action: Make sure that all commands in the CLD file contain correct syntax.
INVITEMCODE
invalid item code specified in list Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU error occurred. User Action: Submit a Software Performance Report (SPR).
INVITEMNM
the /ITEM name 'item-name' is invalid or not uniquely identified Facility: MONITOR, Monitor Utility Explanation: The specified item name is not defined for the class with which it is specified. This message can result from specifying an item name with too few characters to uniquely identify it. User Action: Check the list of items defined for the requested class by entering: HELP MONITOR /ITEM. Reenter the MONITOR command requesting only valid items.
INVITMCOD
invalid item code, item code = 'item code (hex)' Facility: PSM, Print Symbiont Explanation: An invalid item code is detected. User Action: Specify a valid item code.
INVITMCOD
invalid item code or option code Facility: JBC, Job Controller Explanation: The $GETQUI or $SNDJBC item list contains an invalid item code, or the $SNDSMB or $SNDACC option list contains an invalid option code. User Action: Correct the invalid item code or option code.
INVJOUDATA
invalid data found in job journal file Facility: QMAN, Queue Manager Explanation: The queue manager could not identify a piece of data in the job journal file. User Action: Submit a Software Performance Report (SPR). Create a copy of all *.QMAN$JOURNAL* files using the BACKUP /IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_ CONTROL username.
INVKBD_ID
invalid keyboard-id Facility: SMG, Screen Management Facility Explanation: An invalid keyboard id is passed. User Action: Make sure you are passing the keyboard id by reference, not by value. Ensure that the keyboard id is previously set up by a call to SMG$CREATE_VIRTUAL_KEYBOARD.
INVKEY
invalid key Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The specified key is either of zero length or it is greater than the maximum allowable length. User Action: Either change the module name or change the name length limit of the library.
INVKEY
unrecognized keyword Facility: NCP, Network Control Program Explanation: NCP could not recognize a keyword in the command string. This error is returned when the keyword is entered in response to a prompt. User Action: Reenter the requested information.
INVKEYCHAR
key not inserted; 'ASCII-character' (%X'hexadecimal-byte') is not a valid key character Facility: LIBRAR, LIBRARY Command Explanation: The flagged character is not permitted in a HELP key. If the HELP key is a level one key (topic), the module will not be inserted into the HELP library. User Action: Edit the module in the HELP file to remove the invalid character from the key.
INVKEYNAM
invalid key name Facility: SMG, Screen Management Facility Explanation: The specified key name is less than 1 character or more than 31 characters. User Action: Choose a key name with 1 to 31 characters.
INVKTB_ID
invalid key-table-id Facility: SMG, Screen Management Facility Explanation: An invalid key table id is passed. User Action: Make sure you are passing the key table id by reference, not by value. Ensure that the key table id is previously set up by a call to SMG$CREATE_KEY_TABLE.
INVLDADR
invalid virtual address Facility: SDA, System Dump Analyzer Explanation: The virtual address lies outside the boundries of the virtual addresses mapped by the system page table (SPT). User Action: Reenter the command, specifying a valid virtual address.
INVLDRESP
invalid operator response Facility: MOUNT, Mount Utility Explanation: The operator responded to a request with an invalid reply. User Action: None. The request is automatically reentered.
INVLOCKID
invalid lock id Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVLOG
transaction log file format is invalid Facility: SYSTEM, VMS System Services Explanation: The format of the transaction log file is invalid. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP and the DCL DUMP commands for the given log file.
INVLOGFIL
invalid log file specification Facility: CLI, Command Language Interpreter (DCL) Explanation: In a SUBMIT command, the log file specification is invalid. This message is issued with an accompanying message providing more information. User Action: Refer to the VMS DCL Dictionary and reenter the command specifying a valid file specification.
INVLOGFIL
invalid log file specification Facility: INPSMB, Input Symbiont, QMAN, Queue Manager, and SUBMIT, SUBMIT Command Explanation: The specified log file specification is syntactically invalid. The accompanying message provides additional information. User Action: Take corrective action based on the accompanying message.
INVLOGFIL
invalid log file specification Facility: Shared by several facilities Explanation: The batch log file specification supplied with the /LOG_FILE qualifier is invalid. The file specification must reference a disk file and must not contain a node name or wildcards. User Action: Respecify the batch log file specification using the correct syntax.
INVLOGIN
login information invalid at remote node Facility: SYSTEM, VMS System Services Explanation: An attempt is made to initiate a DECnet logical link connection. User Action: The access control string specified is incorrect. If default access control is used, notify the system manager that the DECnet configuration database needs to be updated. This error can be returned if the specified access control string is not recognized (for example, no record in the UAF), or is too long, or contained invalid characters.
INVMAP
invalid map Facility: DCX, Data Compression/Expansion Utility Explanation: A DCX procedure is called with an incorrectly formed map argument or with an invalid context area. User Action: Correct the application program.
INVMAXLEN
invalid maximum length (greater than 512) Facility: SMG, Screen Management Facility Explanation: The maximum length specified for an input string is too long. User Action: Correct your program so that it requests an input string of 512 characters or less.
INVMODE
invalid mode parameter Facility: DTK, DECtalk Facility Explanation: The value of the mode argument is not in the correct range. User Action: Examine the argument. Determine which value is out of range and correct your program.
INVMSG
invalid message received Facility: JBC, Job Controller Explanation: The job controller received an invalid message. This message indicates a logic error in the system or in the job controller interface of a user-written symbiont. User Action: Identify the cause of the problem.
INVMSGBUF
invalid message buffer Facility: JBC, Job Controller Explanation: The $SNDSMB or $SNDACC message buffer is invalid because it is not long enough to contain all required fields or an option extends beyond the end of the message buffer. User Action: Correct the message buffer format and retry the system service call.
INVNAM
invalid NAM block Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The NAM block passed to LBR$INI_CONTROL is invalid. User Action: Correct the NAM block before calling the routine.
INVNBDS
invalid Numeric Byte Data String Facility: LIB, Library Facility Explanation: The string of bytes specified as a NBDS is not a NBDS. Numeric Byte Data Strings are explained in the LIB$CVT_DX_DX routine documentation in the VMS RTL Library (LIB$) Manual. User Action: Check the NBDS descriptor against LIB$CVT_DX_DX documentation.
INVNUMBER
invalid numeric string Facility: PATCH, Patch Utility Explanation: You specified a numeric data string that is invalid in the current context. User Action: Specify the value in another numeric format or set the language to one that accepts this type of numeric string.
INVNUMCHI
invalid number of children, must be positive Facility: PPL, Parallel Processing Facility Explanation: You tried to create a number less than 1. User Action: Recode the program to request a value greater than or equal to 1.
INVNUMSTR
invalid numeric string Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified string can not be converted to a number. User Action: Use a string that correctly represents a number.
INVOOB
invalid out of band character Facility: REM, Set Host Facility Explanation: An attempt was made to define an illegal out-of-band character. User Action: Redefine the out-of-band character. Under VMS, characters 0-31 are legal out-of-band characters.
INVOPCODE
opcode in delayed work queue is invalid Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
INVOPER
invalid operation specified Facility: LIB, Library Facility Explanation: The operation code is out of range or invalid User Action: Examine the operation code. Replace it with a valid operation code.
INVOPEZON
invalid operation for zone Facility: LIB, Library Facility Explanation: The item code is invalid for the specified zone. This message is also returned for an invalid use of an unspecified user zone action routine. User Action: Specify a valid item code.
INVOPR
unrecognized operator in expression Facility: PATCH, Patch Utility Explanation: The expression contains a character that PATCH does not recognize as a valid operator. User Action: Reenter the command with a valid expression.
INVOPRND
unable to resolve operand 'xx' Facility: PATCH, Patch Utility Explanation: You specified an operand that PATCH does not recognize. Operands such as 4(R0) must be preceded by B^, for example, B^4(R0). User Action: Retry the operation specifying a valid operand.
INVOPTION
non-supported flow control parameter received Facility: DTR, DECnet Test Program Protocol Explanation: This message indicates a DECnet test program protocol incompatibility. User Action: Run with a compatible version of DTRECV or equivalent.
INVOPTIONS
to specify options, parameter 3 must be the word OPTIONS. Facility: VMSINSTAL, Install Procedures Explanation: If you are specifying VMSINSTAL options, the third parameter to VMSINSTAL must be the word OPTIONS. User Action: Restart VMSINSTAL, and specify the options in the correct format.
INVOUTDMN
invalid output domain Facility: CDA, Compound Document Architecture Explanation: An invalid output domain was specified for the back end. Only DDIF and DTIF are supported as domains. User Action: Currently, DDIF and DTIF are the only output domains supported.
INVOUTSPE
invalid output file assignment Facility: CLI, Command Language Interpreter (DCL) Explanation: You specified an invalid or null file specification in defining SYS$OUTPUT. User Action: Reenter the command with a correct file specification.
INVOVERQUOTA
invalid overdraft quota specified Facility: SYSMAN, Cluster System Management Utility Explanation: A DISKQUOTA ADD or MODIFY function specified an invalid overdraft quota (nonnumeric, negative, or larger than 32 bits). User Action: Respecify the command with a valid quota.
INVPAGARG
height of 0 is not permitted Facility: SMG, Screen Management Facility Explanation: An attempt is made to change the characteristics of the terminal, setting the height (page size) to 0. User Action: Correct the code. A height of 0 is invalid.
INVPARAM
parameter 'numbers', datatype 'type' illegal, expected 'type' Facility: VAXTPU, VAX Text Processing Utility Explanation: A built-in procedure is invoked with an invalid data type as one of its parameters. User Action: Specify a valid data type.
INVPARAM
parameter value illegal (nonnumeric or too large) Facility: SYSMAN, Cluster System Management Utility Explanation: A PARAMETERS SET command specified an invalid value for a parameter. The parameter is too large (for a numeric parameter) or contains invalid numeric digits. User Action: Supply a valid parameter value.
INVPARFIL
invalid parameter file Facility: SYSGEN, System Generation Utility Explanation: An error occurred accessing the file specified in a USE or WRITE operation. User Action: Check that the file is not protected against read or write access and then reenter your command. If the error reoccurs, but the file can be read or written by other utilities, submit a Software Performance Report (SPR). Include a copy of the invalid parameter file with the SPR.
INVPARLEN
invalid parameter length Facility: JBC, Job Controller Explanation: The buffer length specified for a $GETQUI or $SNDJBC item, or the length of a string specified with a $SNDSMB option, is outside the valid range for that item. User Action: Specify a valid buffer length and retry the system service call.
INVPARM
parameter identifiers must be in the form Pn Facility: CDU, Command Definition Utility Explanation: CDU encountered a parameter definiton in which the parameter being defined is not in the form Pn. All parameters must be in the form Pn. User Action: Edit the CLD file so that all defined parameters are in the form Pn.
INVPARVAL
invalid parameter value Facility: JBC, Job Controller Explanation: The parameter value specified for a $GETQUI or $SNDJBC item, or a $SNDACC or $SNDSMB option, is outside the valid range for that item. User Action: Specify a valid value for the specified item and retry the system service call.
INVPAS_ID
invalid pasteboard-id Facility: SMG, Screen Management Facility Explanation: An invalid pasteboard identifier is specified. User Action: Make sure that you are passing the pasteboard identifier by reference, not by value. A reference to a 0 is valid, since 0 is a valid pasteboard identifier. Make sure the pasteboard is previously set up by a call to SMG$CREATE_PASTEBOARD and that the pasteboard has not been deleted.
INVPASS
invalid password 'password' Facility: INPSMB, Input Symbiont Explanation: The specified password is syntactically invalid. User Action: Correct the error and reenter the job.
INVPATH
invalid path name started by 'string' Facility: PATCH, Patch Utility Explanation: This message indicates an incorrect use of path name rules. User Action: Correct the path name according to path name rules and retry.
INVPERMQUOTA
invalid permanent quota specified Facility: SYSMAN, Cluster System Management Utility Explanation: A DISKQUOTA ADD or MODIFY function specified an invalid permanent quota (nonnumeric, negative, or larger than 32 bits). User Action: Respecify the command with a valid quota.
INVPGP
invalid parameter grouping Facility: NCP, Network Control Program Explanation: The request contained multiple parameters that are in incompatible groups. For example, the executor name and address cannot be set together. User Action: Divide the command into multiple commands, one command for each parameter group.
INVPLACE
placement must be GLOBAL, LOCAL, or POSITIONAL Facility: CDU, Command Definition Utility Explanation: An invalid keyword value is specified for the PLACEMENT qualifier. Valid keyword values for the PLACEMENT qualifier are GLOBAL, LOCAL, and POSITIONAL. User Action: Edit the CLD file so that each PLACEMENT keyword value is one of the following: GLOBAL, LOCAL, or POSITIONAL.
INVPREFIX
invalid prefix format string - check FAO directives Facility: CLI, Command Language Interpreter (DCL) Explanation: The prefix format string specified with SET PREFIX is invalid for one of the following reasons: it is too long; it has invalid FAO directives; or it has FAO directives that are not supported with this command. User Action: Check the SET PREFIX description in the VMS Version 5.5 New Features Manual for restrictions on the format string contents and resulting length. Modify the string accordingly and retry the command.
INVPRVNAM
'privilege' is not a valid privilege Facility: INSTALL, Install Utility Explanation: An invalid privilege name is specified. User Action: Correct the privilege name and reenter the command.
INVPTEFMT
invalid page table entry format Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVPVA
invalid parameter value Facility: NCP, Network Control Program Explanation: The specified value for a parameter is invalid; for example, a line identifier or a load address is incorrect. User Action: Check the rules for specifying the parameter value and reenter the command.
INVPWD
invalid password Facility: CAF, Cluster Authorization File Service Explanation: A cluster password contains characters other than A-Z, 0-9, $, hyphen, and underscore. User Action: Reenter the command with a valid password.
INVPWDLEN
invalid password length - password not changed Facility: CAF, Cluster Authorization File Service Explanation: A cluster password is null or has more than 31 characters. User Action: Reenter the command with a valid password.
INVPWDLEN
invalid password length - password not changed Facility: SET, SET Facility Explanation: A password is specified whose length is outside the range established for valid passwords. User Action: Make sure the password is the correct length and, if necessary, change the password and reenter the command.
INVQMANMSG
queue manager received an improper message Facility: QMAN, Queue Manager Explanation: The queue manager encountered an internal error. User Action: Submit a Software Performance Report (SPR). Create a copy of all *.QMAN$JOURNAL* files using the BACKUP /IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR, along with any SYS$SYSTEM:QMAN$QUEUE_ MANAGER.DMP files. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_ CONTROL username.
INVQUAL
invalid qualifier Facility: CLI, Command Language Interpreter (DCL) Explanation: You entered an invalid qualifier for a DCL command. User Action: Check your documentation for the command and reenter it using the correct qualifier name.
INVQUAVAL
value 'value' invalid for /'qualifier' qualifier Facility: Shared by several facilities Explanation: The specified value is not valid for the specified qualifier. User Action: Check the range of valid values for the qualifier and reenter the command.
INVQUAVAL
value 'value' invalid for qualifier 'qualifier' Facility: ERF, Error Log Utility Explanation: An invalid qualifier was specified. User Action: Use the DCL HELP command or refer to the VMS DCL Dictionary for the valid qualifier values. Then reenter your command.
INVQUENAM
invalid queue name Facility: JBC, Job Controller Explanation: The queue name specified is not syntactically valid. After logical name translation, the queue name must be a character string whose length must be in the range of 1 to 31 characters. The character string must consist of alphanumeric characters, dollar signs, and underscore (_) characters. User Action: Specify a syntactically valid queue name.
INVQUO
quoted argument not allowed in current mode Facility: PATCH, Patch Utility Explanation: You attempted to enter an argument enclosed in quotation marks or apostrophes when you were not in INSTRUCTION or ASCII mode. User Action: Remove the quotation marks or apostrophes and retry the operation. Or if you are entering instructions or ASCII data, indicate this in the command.
INVRANGE
field specification is out of bounds - check sign and size Facility: CLI, Command Language Interpreter (DCL) Explanation: The offset and/or length arguments specify a location that is out of the valid range of this operation. User Action: Check the offset and length; also check the size of the item on which you are operating.
INVRANGE
invalid range enclosure specified Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified range encloses text in an invalid way. User Action: Specify a range of text that consists of either complete lines or a fragment of a single line.
INVRECFMT
record format specified inconsistent with volume format Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility found that the format option on the /RECORD_FORMAT qualifier is not valid for the volume against which it is applied. User Action: It is very seldom necessary to use a /RECORD_FORMAT qualifier, since the defaults taken by EXCHANGE are usually correct. If it is necessary to use a /RECORD_FORMAT qualifier, make sure it is on the correct file specification. It is possible to put /RECORD_FORMAT on either input or output specifications (or even on both), depending on the command.
INVRECORD
invalid record type in file 'filename' Facility: DSR, DIGITAL Standard Runoff Explanation: An invalid record type is encountered in the file. User Action: Make sure that the file contains the correct record type.
INVRECSIZ
invalid record size in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the record size field (BRH$W_RSIZE) of a save set record. Data in the save set is corrupted. User Action: None. Save set data is lost.
INVRECTYP
invalid record type in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the record type field of a save set record. Data in the save set is corrupted. User Action: None. Save set data is lost.
INVREF
invalid object reference Facility: QMAN, Queue Manager Explanation: The queue manager encountered an internal error. User Action: Submit a Software Performance Report (SPR). Create a copy of all *.QMAN$JOURNAL* files using the BACKUP /IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR, along with any SYS$SYSTEM:QMAN$QUEUE_ MANAGER.DMP files. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_ CONTROL username.
INVREPTYP
invalid report type Facility: ERF, Error Log Utility Explanation: An internal consistency error was encountered. User Action: Submit a Software Performance Report (SPR).
INVREQ
invalid startup parameter Facility: STDRV, System Startup Driver Explanation: The startup driver is executed with an invalid first parameter. User Action: If the error occurs during a system boot, check the value of the SYSGEN parameter STARTUP_P1. If errors occur after a @STARTUP command procedure, verify that the first parameter is FULL, MINIMUM, UPGRADE, or the name of the system component to restart.
INVREQCOD
not a valid request code Facility: SMG, Screen Management Facility Explanation: Data is requested from termtable through request codes that are available as symbolic names. The code you have specified is invalid. User Action: Check the spelling of the symbolic name you are using.
INVREQPARM
line 'line-number': All required parameters must precede optional ones Facility: CDU, Command Definition Utility Explanation: CDU encountered a REQUIRED parameter specification after an OPTIONAL parameter is specified. All REQUIRED parameter specifications must precede OPTIONAL parameter specifications.
INVREQTYP
invalid request type Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is associated with an internal status code returned from the command interpreter result parse routine; it indicates a request to perform an unimplemented function. User Action: Submit a Software Performance Report (SPR).
INVRFA
invalid RFA Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The specified RFA is invalid. User Action: Correct the RFA before calling the routine.
INVRFM
invalid record format - file must be FIXED length Facility: CAF, Cluster Authorization File Service Explanation: The file SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT has an invalid format. User Action: Delete and re-create the file on all cluster members with a CONFIGURATION SET CLUSTER_AUTHORIZATION command at the SYSMAN> prompt.
INVRFM
invalid record format for record I/O - file not opened Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is returned by the DCL command OPEN if the file you are trying to open has a record format that is incompatible with record I/O. User Action: You cannot use DCL to read or write to this file.
INVROUT
invalid routine specified in command tables - check .CLD file Facility: CLI, Command Language Interpreter (DCL) Explanation: A user-defined command attempted to invoke a routine that DCL could not find. User Action: Correct the command definition file.
INVROUT
line 'line-number': A ROUTINE clause is only valid when generating an object file Facility: CDU, Command Definition Utility Explanation: CDU encountered a ROUTINE clause while not generating an object file. The ROUTINE clause is only valid when object file generation is requested. User Action: Edit the CLD file to remove the ROUTINE clause or specify the /OBJECT qualifier in the SET COMMAND.
INVROW
invalid row Facility: SMG, Screen Management Facility Explanation: An invalid row number is specified. It is either less than 0 or larger than the number of rows in the virtual display. User Action: Specify a valid row number. Rows are numbered beginning with 1.
INVRSP
invalid management response Facility: NCP, Network Control Program Explanation: Either NCP could not recognize the form of the response from the network management listener (NML) or the response is inappropriate. User Action: Submit a Software Performance Report (SPR).
INVRSP
invalid response Facility: AUTHORIZE, Authorize Utility Explanation: Your response is invalid. User Action: Respond to the "Do you . . . " message that follows this message.
INVRSPID
RSPID not valid Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVSCRPOS
invalid screen position Facility: LIB, Library Facility Explanation: Zero is specified for either the line number or the column number. User Action: Do not specify zero for either the line number or the column number.
INVSECDOMAIN
request originated outside of local security domain Facility: SYSTEM, VMS System Services Explanation: A VAXcluster node has received a service request containing user or object security profile information that originates outside the security domain of the receiving node. The request cannot be serviced without potentially compromising system security. User Action: Make sure that all VAXcluster nodes refer to the same rights database file (SYS$SYSTEM:RIGHTSLIST.DAT).
INVSEMINI
invalid semaphore initial value, cannot exceed its maximum value Facility: PPL, Parallel Processing Facility Explanation: A semaphore initial value must be less than or equal to its maximum value. User Action: Lower the specified initial value. Check the values of the parameters semaphore_maximum and semaphore_initial, and adjust the incorrect value accordingly.
INVSEMMAX
invalid semaphore maximum value, must be positive Facility: PPL, Parallel Processing Facility Explanation: A semaphore's maximum value must be positive. User Action: Change the specified maximum value to a positive value.
INVSHDWMEM
shadow set member 'ddcu:' is 'newer' than the shadow set Facility: MOUNT, Mount Utility Explanation: Volumes being added to an existing shadow set cannot have a higher generation number than the shadow set. User Action: Determine which volume should be the target of the shadow copy operation. Recreate the shadow set, and add the target of the copy operations to it.
INVSMG
invalid message format Facility: NCP, Network Control Program Explanation: The network management message is too long or too short (for example, it may contain too much data or not enough data), or a field is not correctly formatted for the data expected. User Action: Submit a Software Performance Report; include the command that caused this error.
INVSPEED
invalid speed Facility: REM, Set Host Facility Explanation: The selected speed is invalid. User Action: Correct the speed and reenter the command.
INVSTANAM
invalid state name Facility: SMG, Screen Management Facility Explanation: The specified state name is less than 1 character or more than 31 characters. User Action: Choose a state name with 1 to 31 characters.
INVSTLEVEL
structure level is invalid or already up to current structure level Facility: MONITOR, Monitor Utility Explanation: An error occurred while executing a MONITOR CONVERT command. The structure level of the input file is either unknown or already up to the current MONITOR structure level. User Action: Try to play back the MONITOR recording file. If it plays back properly, it is already up to the current structure level. If it still does not play back, the structure level is unknown to this version of MONITOR.
INVSTMNBR
invalid stream number Facility: SMB, Symbiont Services Explanation: An invalid stream number is detected. This is a fatal return status. User Action: Please submit a Software Performance Report (SPR).
INVSTR
string too long for field Facility: AUTHORIZE, Authorize Utility Explanation: The character string you specified is too long. User Action: See the VMS Authorize Utility Manual for information on character string length restrictions.
INVSTRDES
invalid string descriptor Facility: LIB, Library Facility and OTS, General Purpose Facility Explanation: A string descriptor passed to a general library procedure did not contain a valid DSC$B_CLASS field. User Action: Locate the call to the library that caused the error, and initialize the field to the proper class of descriptor. Refer to the VMS Run-Time Library Routines Volume for a description of the classes of descriptors.
INVSTRLEV
invalid structure level Facility: SMB, Symbiont Services Explanation: An invalid structure level is returned by the SMB$INITIALIZE routine. This is a fatal return status. User Action: Specify a valid structure level not greater than SMBMSG$K_STRUCTURE_LEVEL.
INVSTRUCT
invalid structure level in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the structure level field of a save set block. Data in the save set is corrupted. User Action: None. Save set data is lost.
INVSYMNAM
invalid symbol name Facility: LIB, Library Facility Explanation: The length of the specified symbol is greater than 255 characters or the symbol did not begin with a letter. User Action: Do not specify a symbol name with more than 255 characters. Ensure that all symbol names begin with letters.
INVTAB
command tables have invalid format - see documentation Facility: CLI, Command Language Interpreter (DCL) Explanation: An unrecognizable command table format is encountered while attempting to automatically upgrade old command tables to the current format. User Action: Use the Command Definition Utility command SET COMMAND to re-create the tables.
INVTABSPEC
tabs specification incorrect, not changed Facility: VAXTPU, VAX Text Processing Utility Explanation: Your argument to the built-in procedure SET (TAB_ STOPS) is invalid. You must specify an integer value between 1 and 65535, or a string consisting of only spaces and integers. If you specify a string, then the integers must be given in ascending order to achieve predictable behavior. User Action: Correct your argument with the built-in procedure SET (TAB_STOPS).
INVTERTAB
invalid terminal table Facility: SMG, Screen Management Facility Explanation: An invalid terminal table address is specified. User Action: Make sure you are passing the terminal table argument by reference and not by value. Make sure the terminal table address is acquired by calling SMG$INIT_TERM_TABLE.
INVTIME
invalid time interval Facility: VAXTPU, VAX Text Processing Utility Explanation: An invalid time interval was specified. User Action: Correct the specified time interval.
INVTOKEN
unrecognized token 'symbol-name' Facility: PATCH, Patch Utility Explanation: The symbol you specified is not recognized as a valid PATCH command name or qualifier. User Action: Specify valid symbol and retry.
INVTQEFMT
invalid time queue entry format Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
INVTYPE
built-in type 'type-name' is not defined Facility: CDU, Command Definition Utility Explanation: CDU encountered an invalid keyword in a built-in definition while reading from a CLD file. User Action: Edit the CLD file so that all built-in keywords are defined.
INVTYPE
invalid LIB$TPARSE state table entry Facility: LIB, Library Facility Explanation: The state table passed to the LIB$TPARSE procedure is invalid and could not be processed. User Action: Correct the format of the state table in your program. Refer to the VMS Run-Time Library Routines Volume for the correct format.
INVUIC
invalid UIC Facility: SYSMAN, Cluster System Management Utility Explanation: An invalid UIC is entered. Either the format is bad or an alphanumeric UIC does not have a numeric equivalent. User Action: Enter a valid UIC. See the VMS DCL Concepts Manual.
INVUIC
invalid UIC - must be of the form [group,member] Facility: CLI, Command Language Interpreter (DCL) Explanation: The command contains an invalid UIC. The group and member portions of a UIC must be specified within square brackets [ ] and must be separated by a comma. User Action: Correct the UIC and reenter the command.
INVUIC
invalid UIC specified Facility: SMI, System Management Integrator/Server Explanation: A UIC is nonexistent or has an invalid format. User Action: Respecify the associated SYSMAN command with a valid UIC.
INVUIC
'UIC' is an invalid UIC specification Facility: RUN, Run Detached Utility Explanation: UIC value specified with the /UIC qualifier is invalid. User Action: Enter a valid UIC.
INVUSER
invalid user name 'name' Facility: INPSMB, Input Symbiont Explanation: The specified user name is syntactically invalid. User Action: Correct the error and reenter the job.
INVUSERNAME
user name syntax error Facility: AUTHORIZE, Authorize Utility Explanation: You specified an incorrect user name. User Action: Enter a user name specifying a string of 1 through 12 alphanumeric characters, underscores, wildcard characters (dollar signs are permissible, but usually reserved for system names), or a UIC.
INVUSERSPEC
error in user specification Facility: AUTHORIZE, Authorize Utility Explanation: Your command included an incorrect user specification. In a user specification, you may use a numeric UIC format (for example, [007,007]), an alphanumeric format (for example, [COMPOSERS,HAYDN]), or a user name (for example, HAYDN). You can use wildcards to specify multiple users. Refer to the VMS Authorize Utility Manual for specific syntax rules for the command you are using. User Action: Correct the user specification and reenter your command.
INVVAL
unrecognized value Facility: NCP, Network Control Program and REM, Set Host Facility Explanation: A value entered for a parameter is invalid. User Action: Check the rules for the parameter value and reenter the command.
INVVALCLAUSE
invalid value clause encountered Facility: CDU, Command Definition Utility Explanation: CDU encountered a invalid VALUE keyword while reading from a CLD file. User Action: Edit the CLD file so that all VALUE keywords are valid.
INVVEC
invalid or unspecified interrupt vector Facility: SYSGEN, System Generation Utility Explanation: Either no interrupt vector is specified in a SYSGEN command CONNECT, or the one that is specified is not within the UNIBUS interrupt vector address range. User Action: Reenter the command specifying a valid vector number.
INVVIEWSP
invalid /VIEWING_TIME specification Facility: MONITOR, Monitor Utility Explanation: The /VIEWING_TIME value must be an unsigned contiguous string of decimal digits forming a value in the range of 1 to 9,999,999 inclusive. User Action: Reenter the MONITOR request, specifying a valid /VIEWING_TIME value.
INVVMSOSC
invalid VMS operating system command in record "record number" Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont format routine indicating invalid VMS operating system command in record. User Action: Please submit a Software Performance Report (SPR).
INVVOI_ID
invalid voice-id Facility: DTK, DECtalk Facility Explanation: An invalid voice identifier is specified. User Action: Ensure that you are passing the voice identifier by reference, not by value. Ensure that the voice identifier is previously set up by a call to DTK$INITIALIZE.
INVVOLFMT
volume format specified is not consistent with file spec Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a /VOLUME_FORMAT qualifier which did not make sense for the volume type implied by the file specification. User Action: It is very seldom necessary to use a /VOLUME_FORMAT qualifier, since the defaults taken by EXCHANGE are usually correct. Either leave the /VOLUME_FORMAT off, or use the correct option.
INVWIDARG
width of 0 is not permitted Facility: SMG, Screen Management Facility Explanation: An attempt is made to change the characteristics of the terminal, setting its width to 0. User Action: Correct the code. A width of 0 is invalid.
IO_CONCLO
I/O continued to closed file Facility: OTS, General Purpose Facility Explanation: An attempt is made to perform I/O to a file being closed. This error can occur only at AST level. User Action: Correct the program so that AST level routines do not perform I/O on files which may be closing.
IOERROR
I/O error initializing volume on 'device-name' Facility: INIT, INITIALIZE Command Explanation: The operator requested a volume initialization. An I/O error occurred during the write process. User Action: Attempt to perform the operation again using another volume. Dump the error log to determine whether a hardware error occurred.
IOP
operation invalid for file organization or device
Facility: RMS, VMS Record Management Services
Explanation: An invalid VMS RMS operation is attempted. This error
can be caused by any of the following conditions:
o An attempt to perform block I/O when block I/O access is not
specified
o An attempt to perform record I/O when record I/O access is not
specified
o An attempt to rewind a process-permanent file
o An operation not valid for the device type (for example, a
rewind request on a line printer) or the file organization (for
example, an erase or extend request for a magnetic tape file)
User Action: Verify that the call to the VMS RMS service is coded
correctly. If necessary, modify your program to detect and respond
to the condition.
IRC
illegal record encountered; VBN or record number STV = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The byte count field or the control byte for a record in a file is invalid. For sequential and indexed files, the status value (STV) field contains the virtual block number of the block containing the record. For relative files, the status value (STV) field contains the record number of the corrupted record. User Action: For sequential and indexed files, try to re-create the rest of the file. For relative files, reinsert the bad record with the $PUT service using the UIF option in the ROP parameter. This error is caused by hardware errors, VMS RMS or system software errors, or inadvertent modification of files by non-RMS programs.
ISD_OFF
image section descriptor offset is invalid Facility: IMGACT, Image Activator Explanation: The offset in an image header block points beyond the end of that block. This usually indicates a corrupted or invalid image. User Action: Relink the image.
ISD_SIZ
image section descriptor length is invalid Facility: IMGACT, Image Activator Explanation: The length field of an ISD is invalid. This usually indicates a corrupted or invalid image. User Action: Relink the image.
ISD_VBN
ISD VBN greater than header block count Facility: IMGACT, Image Activator Explanation: The list of ISDs has extended to a block beyond the maximum number of blocks allocated to the image header. This usually indicates a corrupted or invalid image. User Action: Relink the image.
ISI
invalid internal stream identifier (ISI) value Facility: RMS, VMS Record Management Services Explanation: The internal stream identifier of the RAB does not specify a valid stream. User Action: This error usually indicates that the stream has not been connected; or that the RAB is inadvertently altered.
ISQUAL
qualifier required; not found Facility: AUTHORIZE, Authorize Utility Explanation: The CREATE, GRANT, or REVOKE command is given without its required qualifier. User Action: Respecify the command with the required qualifier, for example, GRANT/IDENTIFIER.
ITC
index entry too complicated or long Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The entry exceeds the limit of the index buffer for a single item. User Action: Reduce the length of the index entry.
ITD
.IF commands nested too deep: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The number of nested conditional commands (.IF, .IFNOT) exceeds the maximum limit of 10. User Action: Reduce the number of conditional commands.
ITEMNOTFOUND
requested item cannot be returned Facility: SYSTEM, VMS System Services Explanation: The parameter specified in the item list cannot be found. User Action: Verify the parameter specified and correct.
ITERATION
have completed iteration xxx of the VAX Vectors support device test Facility: UETP, User Environment Test Package Explanation: The vector processor device test has completed xxx repetitions of the vector processor device test. User Action: None.
ITMNOTDEF
item requested with the /ITEM qualifier not defined for this revision level Facility: MONITOR, Monitor Utility Explanation: At least one of the items requested with the /ITEM qualifier is not defined. For a playback request, this situation can occur if the file being played back is recorded by MONITOR in a previous version of VMS. For that version, the item may not have been defined. For a live request, the item may no longer be defined for the current revision of VMS. User Action: Reenter the MONITOR command, requesting only those items that were defined when the input file is recorded or, for a live request, are currently defined. As an alternative, specify the /ITEM=all qualifier to obtain all items available in the file for the requested class.
ITMREMOVED
meaningless items were removed from request Facility: JBC, Job Controller Explanation: You specified one or more item codes or qualifiers that are not meaningful in this command. The command is processed and the meaningless items are ignored. User Action: Determine which item codes and qualifiers are meaningless in this command and discontinue using them in this context.
IVADDID
system # 'id-number' cannot be added to the display Facility: SHOW CLUSTER, Show Cluster Utility Explanation: Information for the system identified by the system ID number entered is not available, or the system ID number entered is not the system ID of a node which is previously removed from the display using the REMOVE SYSTEM/ID=system-id command. It should be noted that the system ID number must match the ID number in the SYS_ID field and that it must be entered in the same radix as that of the SYS_ID field. For more information about changing the radix of a field, enter the HELP SET field/FORMAT. User Action: Verify that the system ID entered is correct and reenter the command with the correct system ID, or enter the INIT command to initialize the display and restore all nodes to the display. If the system ID is correct, then be sure to remove the node from the display before attempting to add it to the display.
IVADDNODE
node 'node-name' cannot be added to the display Facility: SHOW CLUSTER, Show Cluster Utility Explanation: Information for the system identified by the node name entered is not available, or the node name entered is not the name of a node which is previously removed from the display using the REMOVE SYSTEM/NODE=node-name command. User Action: Verify that the node name entered is correct and reenter the command with the correct node name, or enter the INIT command to initialize the display and restore all nodes to the display. If the node name is correct, then be sure to remove the node from the display before attempting to add it to the display.
IVADDR
invalid media address Facility: SYSTEM, VMS System Services Explanation: A disk address specified in a physical disk read or write operation is not valid. This error occurs for physical read and write operations or as a result of a hardware error. User Action: Verify the disk address specified and update the program.
IVATIME
invalid absolute time - use DD-MMM-YYYY:HH:MM:SS.CC format Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified absolute time is in an incorrect format. User Action: Reenter the time in the format shown in the error message.
IVBAKADIO
invalid backing store address for I/O Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
IVBLKENT
invalid bad block specifier in string 'string' Facility: BAD, Bad Block Locator Utility Explanation: The block, as specified, contains an invalid character. User Action: Correct the value in the given field.
IVBLKNUM
'string' is an invalid block number, 'position' value 'nnnnnnnn' is out of range Facility: BAD, Bad Block Locator Utility Explanation: The block number as specified is invalid due to the value in the 'position' field. User Action: Correct the value in the given field.
IVBUFLEN
disk boot driver invalid buffer Facility: VAXCLUSTER, VAXcluster Facility Explanation: An internal MSCP error occurred. User Action: Submit a Software Performance Report (SPR).
IVBUFLEN
invalid buffer length
Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal
Explanation: The exact meaning of this message depends on the
device.
If the device is an LPA11-K and if this error occurs for an
initialize LPA11-K request, the initialize command table length is
not the required 278 bytes. If this error occurs for a start data
transfer request, there are several possible causes:
o Command table length is not the required 40 bytes.
o Buffer area size is not evenly divisible by the number of
buffers assigned.
o Individual buffer size is 0.
o Individual buffer size is not a multiple of 2 for a
multirequest mode request, or is not 4 for a dedicated mode
request.
o Random Channel List length is 0 or is not a multiple of 2.
o Bit 15 in the last word of the Random Channel List is not set.
If the device is a DR32 interface, the command block size or the
buffer block size is zero or equal to or greater than 2**29, or
the command table length is not XF$K_CMT_LENGTH.
If this error was returned by the Pseudo Terminal Facility, it
indicates that the buffer size supplied is illegal. This is
returned if the buffer size is less than 0 or greater than 508
characters.
User Action: Action depends on the type of device to which the I/O
request is directed. Refer to the VMS I/O User's Reference Volume
for additional information.
If the error was returned by the Pseudo Terminal Facility, check
the buffer size.
IVCHAN
invalid I/O channel Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: The channel number specified in an input or output request is not a valid channel number; the I/O operation cannot be performed. User Action: Check for a programming error. Verify that the request to assign the I/O channel completed successfully and returned a valid channel number.
IVCHAR
invalid numeric value - check for invalid digits Facility: CLI, Command Language Interpreter (DCL) Explanation: The command interpreter encountered a character string in a context where it expected a numeric value (as the object of an arithmetic operation in an expression, or following a qualifier that requires a numeric value.) User Action: Examine the command string for an undefined or incorrectly spelled symbol name, a missing radix operator (for example, %X) preceding a hexadecimal or octal value, an invalid value following a radix operator (for example, %O9), or for a syntax error. Reenter the command.
IVCHNLSEC
invalid channel for create and map section Facility: SYSTEM, VMS System Services Explanation: The channel number specified in a request to create and/or map a section file is busy; the section cannot be mapped. User Action: Verify that the $OPEN request (to open the section file) completed successfully and returned a valid channel number.
IVDEVNAM
invalid device name Facility: SYSTEM, VMS System Services Explanation: A device name contains invalid characters, no device is specified, or a command or program accepts only certain types of devices in a particular context. User Action: Verify that the device name is specified correctly and is suitable for the requested operation. If a logical name is used, verify that it has been assigned a proper equivalence name.
IVDTIME
invalid delta time - use DDDD-HH:MM:SS.CC Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified delta time is in an incorrect format. User Action: Reenter the delta time in the format shown in the error message.
IVFNAM
invalid lexical function name - check validity and spelling Facility: CLI, Command Language Interpreter (DCL) Explanation: A command contains the character string F$name() where name is not a valid function. User Action: Verify the spelling of the lexical function. Use the DCL command HELP or refer to the VMS DCL Dictionary for a list of lexical functions.
IVGBLTYP
invalid global master PTE type Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
IVGSDNAM
invalid global section name Facility: SYSTEM, VMS System Services Explanation: An invalid global section name is specified. User Action: Refer to the VMS System Services Reference Manual for global section name requirements.
IVKEYNAM
unrecognized key name - check validity and spelling Facility: CLI, Command Language Interpreter (DCL) Explanation: You specified a key name incorrectly. User Action: Correct the spelling of the key name.
IVKEYW
unrecognized keyword - check validity and spelling Facility: CLI, Command Language Interpreter (DCL) Explanation: A keyword specified in a command is not valid for the command. The rejected portion of the command is displayed between backslashes. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for a list of valid keywords.
IVLISTK
interrupt stack invalid restart Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
IVLOCKID
invalid lock id Facility: SYSTEM, VMS System Services Explanation: The lock identification specified in a system service request (for example, $ENQ or $DEQ) is not a valid lock identification for that process. User Action: Check for a programming error. Verify that the $ENQ system service request, which returned the lock identification, completed successfully.
IVLOGNAM
invalid logical name Facility: SYSTEM, VMS System Services Explanation: A name string exceeds the maximum length permitted, or has a length of zero, or is longer than the specified maximum length logical name string, table name string, or equivalence string. Logical names are limited to a length of 255 characters; global section names are limited to 63 characters; common event flag, process names, and cluster names are limited to 15 characters. An error can be returned when a name table is defined and the name for the new name table contains invalid characters. User Action: If the error occurs during command processing, verify the command. If the error occurs during execution of a program, check that the character string descriptors pointing to name strings indicate the correct lengths.
IVLOGTAB
invalid logical name table number Facility: SYSTEM, VMS System Services Explanation: A create or delete logical name system service request specified a logical name table number that is not 0 (system), 1 (group), or 2 (process). User Action: Check for a programming error. Verify that the logical name table number is 0, 1, or 2.
IVLVEC
section not installed with privilege Facility: SYSTEM, VMS System Services Explanation: A shareable image has not been installed with privilege. User Action: All privileged, shareable images, that is, those images that contain user-written system service vectors, must be installed using the /PROTECT qualifier.
IVMODE
invalid mode for requested function Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned by an initialize LPA11-K request. The first three bits (2:0) of the first word (mode word) in the command table are not 0. User Action: Correct the LPA11-K command table.
IVOPER
unrecognized operator in expression - check spelling and syntax Facility: CLI, Command Language Interpreter (DCL) Explanation: An arithmetic expression contains a period (.), indicating a logical, arithmetic, or string operator, but the operator is not a recognized operator. The rejected portion of the command is displayed between backslashes. User Action: Correct the command. Enter the DCL command HELP EXPRESSIONS for a list of valid operators or refer to the VMS DCL Dictionary.
IVORDER
order of ACEs being modified is incorrect for object Facility: SET, SET Facility Explanation: The order of the ACEs being replaced is incorrect. User Action: Verify the order of the ACEs being replaced with the DIRECTORY/ACL command or the DCL SHOW ACL command.
IVPFAIL
the IVP for 'product' has failed. Facility: VMSINSTAL, Install Procedures Explanation: The installation verification procedure (IVP) for the specified product failed. User Action: If you can resolve the problem, reinstall the product. Otherwise, contact the Digital Services Group.
IVPROT
invalid protection code only use combinations of R,W,E, and D Facility: CLI, Command Language Interpreter (DCL) Explanation: The protection code specified for a file or volume is not in the correct syntax. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary, if necessary, for the correct syntax and reenter the command.
IVPROTECT
invalid page protection code Facility: SYSTEM, VMS System Services Explanation: A page protection code is specified as 1 or is greater than 15. User Action: Check for a programming error.
IVQLOC
invalid qualifier location - place after a parameter Facility: CLI, Command Language Interpreter (DCL) Explanation: A qualifier that can be used only to qualify a parameter value in a command is placed following the command name. User Action: Reenter the command; place the qualifier following the parameter value it actually qualifies. Use the DCL command HELP or refer to the VMS DCL Dictionary to determine the meaning and placement of the qualifier.
IVQUAL
invalid qualifier name Facility: INSTALL, Install Utility Explanation: An invalid qualifier is specified. User Action: Reenter the command line.
IVQUAL
unrecognized qualifier - check validity, spelling, and placement Facility: CLI, Command Language Interpreter (DCL) Explanation: The qualifier is spelled incorrectly or is improperly placed in the command line. User Action: Correct the command line.
IVQUOTAL
invalid quota list Facility: SYSTEM, VMS System Services Explanation: The quota list specified for a Create Process system service is not in the proper format, or it contained invalid quota names. User Action: Check for a programming error. Verify that the call to the service is programmed correctly. Refer to the VMS System Services Reference Manual for programming specifications.
IVREMID
system # 'id-number' cannot be removed from the display Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The system ID number entered is not the system ID number of a node which is currently being displayed. User Action: Verify that the SYS_ID field in the SYSTEMS class is being displayed and if not, display the SYS_ID field by entering in the command ADD SYS_ID. Verify that the system ID entered is one of the system IDs being displayed in the SYS_ID field.
IVREMNODE
node 'node-name' cannot be removed from the display Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The node name entered is not the name of a node which is currently being displayed. User Action: Verify that the NODE field in the SYSTEMS class is being displayed and if not, display the NODE field by entering in the command ADD NODE. Verify that the node name entered is one of the node names being displayed in the NODE field.
IVS
illegal /VARIANT qualifier Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The name specification for conditional commands is invalid. User Action: Correct the name specification.
IVSECFLG
invalid process/global section flags Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: Flags specified as input arguments to a system service were not valid. User Action: Verify that the call to the service is coded correctly. See the VMS System Services Reference Manual for coding specifications.
IVSECIDCTL
invalid section identification match control Facility: SYSTEM, VMS System Services Explanation: The match control field in the section identification argument to identify a global section contains an invalid number. User Action: Verify that the call to the service is coded correctly. See the VMS System Services Reference Manual for coding specifications.
IVSSRQ
invalid system service request Facility: SYSTEM, VMS System Services Explanation: A call is made to a service that does not exist. User Action: Check for a programming error.
IVSSRVRQST
invalid system service request Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
IVSTSFLG
invalid status flag Facility: SYSTEM, VMS System Services Explanation: If the Create Process system service ($CREPRC) is called, this message indicates that a reserved bit is set in a status flag argument. If the Create Mailbox and Assign Channel system service ($CREMBX) is called, this message indicates that the prmflg byte is not set correctly. User Action: If $CREPRC is called, verify that the call is coded correctly. Refer to the VMS System Services Reference Manual for coding specifications. If $CREMBX is called, set the prmflg argument to either 1 or 0.
IVSYMB
invalid symbol name - start with an alphabetic character Facility: CLI, Command Language Interpreter (DCL) Explanation: An assignment statement specified a symbol name that does not begin with an alphabetic character. User Action: Choose a name for the symbol that begins with one of the letters A through Z and reenter the command.
IVTIME
invalid time Facility: SYSTEM, VMS System Services Explanation: A time value specified in a system service call is invalid. Either a delta time is greater than 10,000 days, or a calculated absolute time is less than the system date and time. User Action: Check for a programming error. Verify that the call to the service is coded correctly.
IVTIME
invalid time passed in, or computed Facility: LIB, Library Facility Explanation: The value of an argument is out of range, or the computed delta time is out of range. User Action: Examine each argument. Determine which one is out of range or is causing the computed delta time to be out of range, and correct the program.
IVTYPE
invalid system type 'system-type', - must match HW_TYPE field or ALL Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The hardware type entered is not a valid hardware type or information for systems of the type entered is not available. User Action: Verify that the HW_TYPE field in the SYSTEMS class is being displayed and if not, display the HW_TYPE field by entering in the command ADD HW_TYPE. If using the REMOVE SYSTEMS /TYPE=hardware-type command, then verify that the hardware type entered is one of the hardware types being displayed in the HW_ TYPE field. If using the ADD SYSTEMS/TYPE=hardware-type command, then verify that the hardware type entered is one of V785, V780, V750, or HS50, or simply use the command ADD SYSTEM/TYPE=ALL
IVVALU
invalid value syntax - see command documentaion Facility: CLI, Command Language Interpreter (DCL) Explanation: A value for a command qualifier is not specified correctly, or a command is not being used in its proper context. The rejected portion of the command is displayed between backslashes. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary to determine the proper syntax or use of the command.
IVVERB
unrecognized command verb - check validity and spelling Facility: CLI, Command Language Interpreter (DCL) Explanation: The first word on the command is not a valid DCL command or a symbol name equated with a command. The rejected portion of the command is displayed between backslashes. User Action: Check the spelling of the command name or symbol name and reenter the command.
IVWSETLIST
invalid working set list entry Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
JBCERROR
error communicating with job controller Facility: SYSTEM, VMS System Services Explanation: An error occurred in communicating with the job controller while handling an implicitly spooled file. User Action: The file may or may not be printed. If it is not printed, a lost file results. The system manager should ensure that the job controller is functioning properly.
JBRTAINHLD
job 'job-name' for user 'username' in queue 'queue-name' has had option retained replaced with hold Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: The status of a job has been changed from retain to hold. User Action: Contact the owner of the job to determine what corrective actions should be taken prior to releasing the job to be scheduled for execution.
JEC
Unexpected text at end of command: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: Extraneous text (not a valid terminator) follows this command. User Action: Insert a valid terminator after the command.
JNLACP
Fatal error detected by journal ACP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
JNLACTIVE
asynchronous actions prohibited when journal file open Facility: VAXTPU, VAX Text Processing Utility Explanation: Asynchronous action routines are prohibited when a journal file is open. User Action: You must choose between journaling routines and action routines.
JNLDRV
Fatal error detected by journal driver Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
JNLNOTAUTH
RMS Journaling not authorized; operation not performed Facility: RMS, VMS Record Management Services Explanation: An attempt was made to open a file marked for RMS journaling for write access on a node that is not authorized to perform RMS journaling. Access to the file has been denied. The secondary status value (STV) contains the error status from the License Management Utility. User Action: If you want to journal the file, RMS journaling must be authorized on the node from which you access the file. Either attempt to access the file on a node that is authorized to perform RMS journaling, or fix the error condition specified in the secondary status value (STV). See the VMS License Management Utility Manual for more information. If you do not want to journal the file, unmark the file for journaling by entering a command in the following form: SET FILE/NOAI_JOURNAL/NOBI_JOURNAL/NORU_JOURNAL filespec
JNLNOTOPEN
journal file not open, recovery aborted Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU is asked to recover data from a journal file, but the journal file was not opened. User Action: Modify your section file to open the journal file during a recovery.
JNLOPEN
journal file already open Facility: VAXTPU, VAX Text Processing Utility Explanation: A journal file is already open. User Action: Close the current journal file before opening another.
JNLPUT
error writing to journal file
Facility: PATCH, Patch Utility
Explanation: An output error occurred while PATCH is writing to
the journal file.
User Action: This message is issued with accompanying messages.
Take corrective action based on the accompanying messages.
Job 'name' (queue 'name', entry 'number') completed
Facility: JBC, Job Controller
Explanation: This informational message is issued in response to
the /NOTIFY qualifier of the PRINT or SUBMIT command to indicate
that the specified job has completed. If the job completed
unsuccessfully, this message is followed by the completion status
of the job.
User Action: None.
Job 'name' (queue 'name', entry 'number') holding
Facility: JBC, Job Controller
Explanation: This informational message is issued in response to
the /IDENTIFY qualifier of the PRINT or SUBMIT command to indicate
that the specified job has been successfully entered on the queue
listed. By default, this information is displayed on the current
output device for the PRINT and SUBMIT commands.
User Action: None.
Job 'name' (queue 'name', entry 'number') holding until 'time'
Facility: JBC, Job Controller
Explanation: This informational message is issued in response to
the /IDENTIFY qualifier of the PRINT or SUBMIT command to indicate
that the specified job has been successfully entered on the queue
listed. By default, this information is displayed on the current
output device for the PRINT and SUBMIT commands.
User Action: None.
Job 'name' (queue 'name', entry 'number') pending
Facility: JBC, Job Controller
Explanation: This informational message is issued in response to
the /IDENTIFY qualifier of the PRINT or SUBMIT command to indicate
that the specified job has been successfully entered on the queue
listed. By default, this information is displayed on the current
output device for the PRINT and SUBMIT commands. This message is
accompanied by one of the following lines of text:
o Pending status caused by insufficient access to queue
o Pending status caused by characteristic mismatch
o Pending status caused by lowercase attribute not present on
queue
o Pending status caused by job size below queues minimum job size
limit
o Pending status caused by job size above queues maximum job size
limit
o Pending status caused by form/stock mismatch
o Pending status caused by 'reason'
User Action: None.
Job 'name' (queue 'name', entry 'number') started on 'name'
Facility: JBC, Job Controller
Explanation: This informational message is issued in response to
the /IDENTIFY qualifier of the PRINT or SUBMIT command to indicate
that the specified job has been successfully entered on the queue
listed. By default, this information is displayed on the current
output device for the PRINT and SUBMIT commands.
User Action: None.
JOBABORT
job aborted during execution Facility: JBC, Job Controller Explanation: The execution of the affected job is aborted by a STOP/ABORT, STOP/ENTRY, or DELETE/ENTRY command. User Action: If necessary, resubmit the job.
JOBCARD
job beginning 'command' Facility: INPSMB, Input Symbiont Explanation: The system encountered an error in a batch job entered from a card reader. This message displays the text of the JOB command; it is followed by the error messages for the batch job. User Action: Take corrective action based in the accompanying messages.
JOBCTLABORT
request failed because job controller aborted Facility: JBC, Job Controller Explanation: The $GETQUI, $SNDACC, $SNDJBC, or $SNDSMB system service operation failed because the job controller process terminated execution. The job controller voluntarily aborts and restarts itself if it encounters a fatal system error or an internal logic error. User Action: None.
JOBDELETE
job deleted before execution Facility: JBC, Job Controller Explanation: The affected job was deleted by a DELETE/ENTRY or DELETE/QUEUE command before it executed. User Action: If necessary, resubmit the job.
JOBDELFO
job 'job-name' (entry 'number' for user 'username') deleted during queue manager failover Facility: QMAN, Queue Manager Explanation: The queue manager detected corruption in the specified job and deleted the job. User Action: Notify the user that the specified job was deleted. The user might want to resubmit the job. Submit a Software Performance Report (SPR). Create a copy of all *.QMAN$JOURNAL* files using the BACKUP/IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_CONTROL username.
JOBNOTEXEC
specified job is not executing Facility: JBC, Job Controller Explanation: You used STOP/ENTRY or STOP/ABORT to try to abort a job that was not being processed at the time. User Action: Use DELETE/ENTRY to eliminate the job.
JOBQUEDIS
system job queue manager is not running Facility: JBC, Job Controller Explanation: The requested operation cannot be executed because the system job queue manager has not been started. This error is returned on queue operations before the START/QUEUE/MANAGER command has been executed. User Action: Consult the system manager.
JOBQUEENA
system job queue manager is already running Facility: JBC, Job Controller Explanation: The system job queue manager cannot be started because it is already running. This error is returned in response to the START/QUEUE/MANAGER command when the queue manager has been previously started. User Action: If the system job queue manager must be restarted to specify different queue file parameters, first issue the STOP /QUEUE/MANAGER command. Otherwise, no action is necessary.
JOBREQUEUE
job aborted during execution and then requeued Facility: JBC, Job Controller Explanation: The execution of the affected job is aborted by a STOP/REQUEUE command. The job is requeued and will be executed again. User Action: None. Journal file could not be closed Facility: EDT, EDT Editor Explanation: You used the /RECOVER qualifier in your EDIT/EDT command line, but EDT is unable to close the journal file after processing the commands in it. Some problem exists at the system level with that file. User Action: Correct the problem indicated by the file system message. Journal file could not be opened Facility: EDT, EDT Editor Explanation: The journal file given in the command line cannot be opened. EDT will display an associated file system message for the error. User Action: Correct the problem indicated by the file system message.
JOURNAL
journaling to 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility is writing journal records to the specified file in response to the /JOURNAL qualifier. This message is displayed only if the /LOG qualifier is specified. User Action: None.
JOURNALBEG
Journal of edit session started Facility: VAXTPU, VAX Text Processing Utility Explanation: The journaling of your VAXTPU session has begun. User Action: None is required. However, you may execute the built- in procedure JOURNAL_CLOSE if you want to close the journal file.
JOURNALCLOSE
Journal file successfully closed, journaling stopped Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure JOURNAL_CLOSE has closed the journal file. Your subsequent commands will not be written to the journal file. User Action: None.
JOURNALEOF
End of journal file found unexpectedly Facility: VAXTPU, VAX Text Processing Utility Explanation: Journal recovery is aborted due to an unexpected end of file. User Action: If the recovered information is sufficient, resume editing from this point. VAXTPU has recovered as much as it can from your journal file.
JPITSTERR
error encountered while testing $GETJPI system service Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error testing VMS system services. This error is received in relation to a previously displayed error condition or could be the result of a more serious VMS problem. User Action: If a condition is identified which is causing the problem, correction the condition and re-run the test. If the error persists, submit a Software Performance Report. If no condition can be identified, run diagnostics for VAX Vectors, or contact the Digital Services Group.
KBF
invalid key buffer Facility: RMS, VMS Record Management Services Explanation: The specified key buffer is in an area of memory that cannot be correctly accessed by the caller. User Action: Verify that the call to the VMS RMS service is programmed correctly. Specifically, check that the key buffer address is correctly specified.
KEY
invalid record key Facility: CONVERT, Convert Utility Explanation: You have specified a key of the wrong data type. User Action: Supply a key with the correct data type.
KEY
invalid record number key or key value
Facility: RMS, VMS Record Management Services
Explanation: An invalid key value is specified in one of the
following ways:
o A negative or zero record number is specified for a random
operation on a sequential or relative file.
o A packed decimal key value specified for an indexed value
contained an invalid nibble.
User Action: Modify the program, if necessary, to detect and
respond to the condition.
KEYALRINS
key already inserted in tree Facility: LIB, Library Facility Explanation: A key is found in the tree, so a new key is not inserted. User Action: None. The operation is successful.
KEYAMBINC
key specification is ambiguous or inconsistent Facility: SORT, Sort/Merge Utility Explanation: You specified duplicate key parameters for a single /KEY qualifier. User Action: Specify each key parameter only once. For multiple keys, use a /KEY qualifier for each key.
KEYCNV
synonym 'key name' has been converted to 'key name' Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the key name specified in the DEFINE/KEY command is a synonym for a definable key name. The synonym name is converted to the actual key name prior to defining the key. User Action: None.
KEYDEFPRO
key definition is protected - cannot be changed or deleted Facility: SMG, Screen Management Facility Explanation: The specified key is already defined, and since its definition is protected, it cannot be changed or redefined. User Action: None.
KEYED
mismatch between sort/merge keys and primary file key Facility: SORT, Sort/Merge Utility Explanation: You created an empty indexed file with a primary key that does not match the sort key. The sort operation is less efficient than it is when the two keys match. User Action: For greater efficiency, create a new indexed file or change your sort key.
KEY_LEN
invalid key length, key number n, length n Facility: SORT, Sort/Merge Utility Explanation: The key size is incorrect for the data type, or the total key size is greater than 32,767. User Action: Specify the correct key field size. Size must be less than or equal to 32,767 for character data; 1, 2, 4, 8, or 16 for binary data; and less than or equal to 31 for decimal. Also, only ascending or descending order is allowed.
KEYMAPNOTFND
key map 'key-map-name' not found in key-map list 'key-map-list-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You are trying to remove a key map that is not in the key-map list. User Action: Enter the built-in procedure SHOW (KEY_MAP_LISTS) on the command line to obtain the names of the key maps in your key-map list.
KEYNAMLNG
key 'key-name' name length illegal in library 'filespec' Facility: LIBRAR, LIBRARY Command Explanation: The name of the module you are inserting exceeds the name length limit for the library. User Action: Rename the module before inserting it into the library.
KEYNOTDEF
key is not defined Facility: SMG, Screen Management Facility Explanation: An attempt is made to perform an operaton, such as SMG$GET_KEY_DEF, on a key which is not defined. User Action: Check your program to see if this key should have been defined.
KEYNOTFND
key not found Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. The Librarian could not find the key you specified in the key name argument to the LBR$LOOKUP_KEY routine. User Action: Correct the key name argument before calling the routine.
KEYNOTFOU
key not found in tree Facility: LIB, Library Facility Explanation: The specified key is not found in the tree. User Action: Take appropriate action. Keys cannot be defined in Nokeypad mode Facility: EDT, EDT Editor Explanation: The nokeypad DEFK command can reassign the key definition function only in keypad mode to a key other than Ctrl /K. It cannot be used to redefine keys. The attempted operation cannot be performed. User Action: None.
KEYSUPERSEDED
definition of key 'name' superseded Facility: VAXTPU, VAX Text Processing Utility Explanation: The key you are defining is already defined. The new definition, which you supplied, will replace the old one. User Action: None.
KEYWORDPARAM
keyword 'name' used as procedure, variable, or constant Facility: VAXTPU, VAX Text Processing Utility Explanation: A keyword is being used as a user-defined procedure variable or constant. User Action: Use a name that is not a keyword and recompile your program.
KFF
known file found Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to search the known file list completed successfully, and the RMS file open is not required. User Action: None. This message is provided for DIGITAL-supplied component usage.
KNM
key name buffer not accessible for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The key name buffer address in a key definition XAB specifies an area of memory that cannot be correctly accessed by the caller. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly; in particular, verify that the buffer is readable for a $CREATE operation, and writeable for a $DISPLAY or $OPEN operation.
KRF
invalid key-of-reference for $GET/$FIND Facility: RMS, VMS Record Management Services Explanation: The key-of-reference value specified in the RAB is greater than the number of keys defined for the file. User Action: Verify that the call to the VMS RMS service is coded correctly.
KRNLSTAKNV
kernel stack not valid Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
KSI
index bucket will not hold two keys for key-of-reference = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The size of the index buckets specified for the key must be large enough to hold at least two key values. User Action: The status code (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the VMS RMS service is coded correctly.
KSZ
invalid key size for $GET/$FIND Facility: RMS, VMS Record Management Services Explanation: The key size specified for a relative or sequential file does not specify a length of four bytes. Or the key size specified for an indexed file is greater than the key length or is zero for a string key. User Action: Verify that the call to the VMS RMS service is coded correctly.
LABELERR
error in tape label processing on 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to process the file labels on the specified volume. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
LAN
invalid lowest-level-index area number for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The lowest-level-index area number specified in a key definition XAB is not a defined area for the file. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
LARGECNT
'device-name' is too large to be processed Facility: BACKUP, Backup Utility Explanation: The specified volume is too large to be processed by the Backup Utility. The error may be caused because the specified cluster factor is too small. User Action: Retry the operation using a larger volume cluster factor.
LARGECNT
disk too large to be supported Facility: INIT, INITIALIZE Command Explanation: This version of Files-11 does not support a disk of this size. User Action: Check the device driver to determine if it is initializing the device database correctly. You may have a need for Digital-supplied custom software.
LATSTOPPING
LAT shutdown in progress Facility: LAT, LAT Facility Explanation: The LAT software has been stopped on the local node. User Action: None.
LCKPAGFUL
no more pages may be locked in memory Facility: SYSTEM, VMS System Services Explanation: An attempt to lock pages in memory failed because the system limit for the number of locked pages is reached. User Action: See your system manager. If some pages were successfully locked, unlock them and attempt to load the new pages.
LDE
literal doesn't end with .END LITERAL: 'STRING' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A DSR command .END LITERAL does not immediately follow the final line of a DSR command .LITERAL n (where n is the number of lines to be produced). User Action: Put the DSR command .LITERAL on the correct line, recount the number of lines of literal text and reset n, or remove the n value.
LENMUSONE
length of fill string and clear string must be 1 Facility: SMG, Screen Management Facility Explanation: A call to SMG$READ_VERIFY specified a fill string or a clear string more than 1 character long. Since fill character matching is done one character at a time, only one character may be specified for the fill and clear string. User Action: Modify the fill string or the clear string, or both, to be 1 character long.
LENNOTEQL
length of picture string and initial string are not equal Facility: SMG, Screen Management Facility Explanation: A call to SMG$READ_VERIFY specified a picture string and an initial string of unequal lengths. Since the initial string is used as the default value for the input, it must match the picture string in length. User Action: Modify the initial string so that is is the same length as the picture string.
LENVIO
address space length violation Facility: SYSTEM, VMS System Services Explanation: A virtual address specified in a system service call is beyond the end of the process's program or control region. User Action: Check for a programming error. Verify that the call to the service is coded correctly.
LEX
invalid $EXTEND for area 'nnn' containing an unused extent Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $EXTEND operation attempted to extend the specified area, and an unused extent is already allocated. Each area has, at most, one current extent and one unused next extent. User Action: The status value (STV) field of the FAB contains the area number in error. Verify that the call to the VMS RMS service is coded correctly.
LIBFIND
failed to find valid module or STB at RFA 'number:number' for module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The linker tried to read the stated object module at the specified Record File Address, but did not find a valid module. This is generally due to someone deleting a module out of a library between Pass 1 and Pass 2. User Action: Retry the link operation. If it continues to fail with the same error, try rebuilding the library.
LIBNAMLNG
library module name 'module-name' has illegal length ('decimal-
number')
Facility: LINK, Linker Utility
Explanation: A library module name specified in the /INCLUDE
qualifier has illegal length.
User Action: Reenter the command correctly.
LIBNOTOPN
library not open Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. Except for LBR$INI_CONTROL and LBR$OPEN, all routines require that the library be open. User Action: Open the library before calling the routine.
LIBOPN
library already open Facility: LBR, Librarian Subroutine Package Explanation: This warning message is generated by the Librarian routines. The library you attempted to open is already open. Processing of your program continues. User Action: None.
LINCOM
line communication error Facility: NCP, Network Control Program Explanation: The requested line is unavailable, or an error occurred during transmission to the line. For example, this error occurs if the line identifier is incorrect. User Action: Make sure that you are correctly identifying the line, and that the line is in the correct state for the function you are performing. Line exceeded 255 characters, truncated Facility: EDT, EDT Editor Explanation: The input for the line exceeds 255 characters; the excess is deleted. User Action: None.
LINEABRT
host aborted transmission or failed to respond Facility: SYSTEM, VMS System Services Explanation: The IBM host either aborted the current transmission with a protocol sequence (EOT) or failed to respond to an emulator-generated ENQ. In the latter case, the emulator sent the number of ENQ sequences specified by the ENQ count in IO$_ SETCHAR, and the IBM host did not issue an appropriate response. User Action: Retry the transmission. If you continue to receive this message after several attempts, the line is probably defective and/or unusable.
LINERR
command line segment in error 'text' Facility: LINK, Linker Utility Explanation: Errors were found during command line processing. The given segment of the command line is in error. User Action: Correct the error and retry the operation.
LINETOOLONG
line is maximum length, cannot add text to it Facility: VAXTPU, VAX Text Processing Utility Explanation: The line in the text buffer is already at the maximum length allowed. User Action: Use the built-in procedure SHOW to find the maximum length and then shorten the line.
LINK
error on logical link Facility: CNF, NI Configurator Explanation: An error occurred on a logical link. User Action: See the accompanying message to determine the appropriate action.
LINKABORT
network partner aborted logical link Facility: SYSTEM, VMS System Services Explanation: The remote process disconnected the logical link either because the process exited prematurely or because it is the normal way for the process to disconnect the link. User Action: Check to see if the node is reachable and retry.
LINKDISCON
network partner disconnected logical link Facility: SYSTEM, VMS System Services Explanation: The remote process disconnected the logical link. This is an expected action. User Action: None.
LINKEXIT
network partner exited
Facility: SYSTEM, VMS System Services
Explanation: The remote process exited before confirming the
logical link for one of the following reasons:
o A problem with the log file on the remote node
o An unopened remote log file because of a write-locked disk (on
the remote node)
o A premature exit of the process
User Action: Refer to the VMS Networking Manual. Then either read
the remote log or retry the operation.
LINNOTFND
requested line is not found Facility: SMG, Screen Management Facility Explanation: The input line requested in a call to SMG$RETURN_ INPUT_LINE is not found. User Action: If necessary, modify your program to recognize this condition and respond to it.
LINPRO
line protocol error Facility: NCP, Network Control Program Explanation: Indicates an invalid line protocol message or operation during direct line access. In the case of a line loop test, an error that should have been detected by the line protocol is detected during message comparison. User Action: Make sure that the line protocol and the line characteristics are set correctly.
LINTOOLONG
line too long Facility: MACRO, VAX MACRO Assembler Explanation: A source line in a macro definition is longer than 1000 characters. User Action: Restructure the source code so that the line is shorter.
LISINPSAV
the /LIST qualifier requires save set as input Facility: BACKUP, Backup Utility Explanation: The input specification for a listing operation must reference a save set. User Action: Correct the specification and reenter the command.
LISTENDSB
event listening disabled Facility: AUDSRV, Audit Server Explanation: Security audit event listening has been disabled. User Action: None. This is an informational message.
LISTENENAB
event listening enabled on device 'device' Facility: AUDSRV, Audit Server Explanation: The specified device has been successfully enabled as a security audit event listener device. User Action: None. This is an informational message.
LISTENFAIL
device 'device' does not exist or is not accessible; requestor PID: 'pid' Facility: AUDSRV, Audit Server Explanation: The specified listener device could not be accessed because the device does not exist or it is not accessible to the audit server process. User Action: Insure that the device exists and allows (SYSTEM:RWLP) access.
LISTENNOTMBX
requested listener device 'device' is not a mailbox; requestor PID: 'pid' Facility: AUDSRV, Audit Server Explanation: The audit server could not associate the specified listener device because the listener device is not a mailbox device. User Action: Specify an existing mailbox device.
LISTNOTFND
attribute name not previously defined Facility: CDU, Command Definition Utility Explanation: There is an undefined symbol reference in the syntax of the CLD file. User Action: Define the syntax list in the CLD file.
LISTTOOSHORT
itemlist too short Facility: LAT, LAT Facility Explanation: A LAT SETMODE $QIO request cannot be fulfilled because the specified item list is not large enough. User Action: Increase the size of the item list specified in the $QIO request.
LKBGRANTED
LKB is granted, but shouldn't be Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
LKBREFNEG
LKB reference count negative Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
LKPNOTDON
lookup has not been done Facility: LBR, Librarian Subroutine Package Explanation: This error message is generated by the Librarian routines. LBR$LOOKUP_KEY is not called before calling up LBR$GET_ RECORD. User Action: Call LBR$LOOKUP_KEY before calling LBR$GET_RECORD.
LKWSETFUL
locked portion of working set is full Facility: SYSTEM, VMS System Services Explanation: No more pages can be locked in the working set because there would not be enough remaining pages available dynamically for the image to continue execution. User Action: Use the DCL command SET WORKING_SET to increase the working set limit, if the limit is not already set at the maximum allowed. If the working set limit is already at the maximum allowed, correct the program that attempted to lock too many pages in the working set.
LNE
logical name translation error
Facility: RMS, VMS Record Management Services
Explanation: VMS RMS encountered an error while translating a
logical name. This can be an error from the following:
o The limit of 10 levels of logical name translation has been
exceeded.
o A logical name is recursively entered in a logical name table.
o A logical name translates to an invalid process permanent file
name equivalence string.
User Action: Use the DCL command SHOW LOGICAL to verify the
current result of translation on the specified logical name.
Verify that the call to the VMS RMS service is coded correctly.
LNK
invalid link identification Facility: NCP, Network Control Program Explanation: The format of the link identification is incorrect. User Action: Check the syntax rules for link identifiers, and reenter your command with the correct link identifier.
LOADERR
error loading image, 'image-name' Facility: ERF, Error Log Utility Explanation: An error occurred during an attempt to load the specified image. User Action: Obtain the specified image from your distribution kit. If the specified image is not part of your distribution kit, submit a Software Performance Report (SPR).
LOADIDX
error loading secondary index n Facility: CONVERT, Convert Utility Explanation: Some error occurred during the load of the specified key of reference on the output file. This message will be accompanied by another message that will describe the error. NOTE: Indexes 0 through n-1 are intact. User Action: Correct the error described by the other message and try again.
LOCKHEADER
file ('file-id') 'filename' deaccess locked
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file is marked as deaccess locked.
User Action: If the /CONFIRM qualifier is specified, you can
either unlock or delete the file.
LOCKMGRERR
error detected by Lock Manager Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
LOCKVOL
error locking volume set - /REPAIR canceled Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to lock the volume set to execute a /REPAIR operation. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command. The /REPAIR qualifier requires a system UIC or SYSPRV privilege, or the user must be the owner of the volume.
LOCNEG
entity explicitly and locally negated in command string Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified qualifier is present in its negated form (with /NO) and is used as a local qualifier. User Action: None.
LOCNOTEST
lock is not established Facility: PPL, Parallel Processing Facility Explanation: You cannot release a lock you have not been granted. User Action: Code your program to ensure that the lock is held by the caller attempting to release it.
LOCPRES
entity value is locally present in command string Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified qualifier is present and is used as a local qualifier. User Action: None.
LOGCLOS
logfile closed by operator 'filespec' logfile is 'filespec' Facility: OPCOM, Operator Communication Process Explanation: This message indicates that OPCOM has closed the operator's log file. User Action: None.
LOGDBUR
event receiver database update at 'dd-mm-yy hh:mm:ss.ms' Facility: EVL, Event Logger Explanation: The event receiver updated its internal database as a result of a startup or notification from NETACP. This informational message displays the time stamp for the update. User Action: None.
LOGDBUT
event transmitter database update at 'dd-mm-yy hh:mm:ss.ms' Facility: EVL, Event Logger Explanation: The event transmitter updated its internal database as a result of EVL startup or notification from NETACP. This informational message displays the time stamp for the update. User Action: None.
LOGFAI
failed to open log file Facility: REM, Set Host Facility Explanation: An error prevented the creation of a log file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
LOGFAIL
failed logfile operation on file 'filespec' Facility: OPCOM, Operator Communication Process Explanation: The DCL command REPLY/LOG failed to create a new operator communication log file. This message generally indicates a file system failure. User Action: Accompanying messages indicate the reason for the failure.
LOGIC
logic error in NCP Facility: NCP, Network Control Program Explanation: A logic error occurred in NCP. User Action: Submit a Software Performance Report detailing the command that caused this error.
LOGIC
program logic error or unexpected condition Facility: CNF, NI Configurator Explanation: A condition or circumstance is encountered which NICONFIG logic is unprepared to handle. User Action: This is a programming error and should be reported. LOGIN - account is auto-login only Facility: LOGIN, Login Processor Explanation: The automatic login feature permits users to log in to the system without specifying a user name. An automatic login account cannot be accessed by a normal interactive login or by an explicit DECnet access control string. This message is not displayed to the user; it is written to the system accounting and security audit records. The message displayed to the user is "User authorization failure"; the message displayed to the system manager is AUTOLOGIN. User Action: None. LOGIN - account is disabled Facility: LOGIN, Login Processor Explanation: An attempt is made to log in to an account when the account is disabled. An account's system access can be restricted by setting the DISUSER flag in the user authorization file. This message is not displayed to the user; it is written to the system accounting and security audit records. The message displayed to the user is "User authorization failure"; the message displayed to the system manager is DISUSER. User Action: None. LOGIN - breakin evasion in effect Facility: LOGIN, Login Processor Explanation: Access to an account is denied because break- in evasion is in effect for that account. This message is not displayed to the user; it is written to the system accounting and security audit records. The message displayed to the user is "User authorization failure"; the message displayed to the system manager is EVADE. User Action: None. LOGIN - error accessing authorization record Facility: LOGIN, Login Processor Explanation: The Login Processor could not read the specific user record for this user. The message displayed to the system manager is USERAUTH. User Action: Try the operation again later. LOGIN - error accessing network authorization file Facility: LOGIN, Login Processor Explanation: LOGIN could not read the SYS$SYSTEM:NETPROXY.DAT network user authorization file. The message displayed to the system manager is NETUAFERR. User Action: Determine whether the file SYS$SYSTEM:NETPROXY.DAT exists and, if it does, make sure it is not protected against system read access. LOGIN - error accessing system authorization file Facility: LOGIN, Login Processor Explanation: LOGIN could not read SYS$SYSTEM:SYSUAF.DAT. The message displayed to the system manager is FILEACC. User Action: Check to see that the file exists and that it has system read access. LOGIN - error activating command interpreter 'CLI name' Facility: LOGIN, Login Processor Explanation: An error occurred when you tried to activate the specified command interpreter. The message displayed to the system manager is CLIFAIL. User Action: Ensure that the command interpreter image exists and that the image file has read access. LOGIN - error activating command interpreter tables 'table name' Facility: LOGIN, Login Processor Explanation: LOGIN cannot access the specified command language interpreter tables. The message displayed to the system manager is CLITBLFAIL. User Action: Determine whether the specified tables exist and, if they do, make sure they are not protected against system read access. LOGIN - error changing expired password Facility: LOGIN, Login Processor Explanation: An error occurred while changing an expired password. This message is usually accompanyied by an additional message describing the exact cause of the error. (This message appears as FRCPWDERR to the system manager.) User Action: Take corrective action based in the accompanying message. LOGIN - error connecting to 'terminal-name' Facility: LOGIN, Login Processor Explanation: An error occurred when the system attempted to reconnect to the specified disconnected terminal. The message displayed to the system manager is CONNERR. User Action: Try again. If the error reoccurs, report it to your system manager. LOGIN - error creating space for command interpreter symbol table Facility: LOGIN, Login Processor Explanation: There is not enough virtual address space available to create the command interpreter symbol table. The message displayed to the system manager is CLISYMTBL. User Action: Check that the system is set up with the value of VIRTUALPAGECOUNT large enough to allow the CLI to be mapped. LOGIN - error opening 'filename' as input Facility: LOGIN, Login Processor Explanation: A file to be read by LOGINOUT (for example, a file containing the announcement message) cannot be opened. The message displayed to the system manager is OPENIN. User Action: Ensure that the file exists and that it has read access. LOGIN - error opening primary input file SYS$INPUT Facility: LOGIN, Login Processor Explanation: The system cannot open the current input device and cannot perform the login. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. The message displayed to the system manager is INPUTERR. User Action: Take corrective action based on the VMS RMS message, and repeat the login procedure, if possible. LOGIN - error opening primary output file SYS$OUTPUT Facility: LOGIN, Login Processor Explanation: The system cannot open the current output device and cannot perform the login. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. The message displayed to the system manager is OUTPUTERR. User Action: Take corrective action based on the accompanying message, and repeat the login procedure, if possible. LOGIN - error protecting command interpreter pages Facility: LOGIN, Login Processor Explanation: An error occurred when you tried to write-protect the CLI code. The message displayed to the system manager is CLIPROT. User Action: Try the operation again later. LOGIN - error protecting command interpreter tables pages Facility: LOGIN, Login Processor Explanation: An error occurred when the system tried to write- protect the command interpreter table pages. The message displayed to the system manager is CLITBLPROT. User Action: Try again. If the error reoccurs, report it to your system manager. LOGIN - error reading command input Facility: LOGIN, Login Processor Explanation: An error occurred during the entry of the command; for example, the timeout period following the prompt for user name or password expired before you entered the responses. The message displayed to the system manager is CMDINPUT. User Action: Repeat the login procedure. LOGIN - fatal job controller interaction problem Facility: LOGIN, Login Processor Explanation: An internal error occurred in the job controller during the login; the login cannot be performed. The message displayed to the system manager is JBCMIXUP. User Action: Repeat the login procedure. If the failure persists, notify the system operator or manager of the problem. LOGIN - invalid password Facility: LOGIN, Login Processor Explanation: The specified password is incorrect. This message is not displayed to the user; it is written to the system accounting and security audit records. The message displayed to the user is "User authorization failure"; the message displayed to the system manager is INVPWD. User Action: None. LOGIN - invalid SYS$INPUT for interactive login Facility: LOGIN, Login Processor Explanation: SYS$INPUT is a logical name for the input from a process to the system. When you use the system interactively, SYS$INPUT is assigned to your terminal by default. The system then acts upon the input it receives from your terminal. During your process, you can redefine SYS$INPUT to a data file; the system will then read input from the file. However, you cannot initiate an interactive process while SYS$INPUT is defined as a file. File-structured storage devices are not permitted as SYS$INPUT for interactive processes. The purpose of this restriction is to prevent LOGIN from reading a user name and password from a file. The message displayed to the system manager is INVINPUT. User Action: Use a non-file-structured device as SYS$INPUT for an interactive process. LOGIN - licensed number of system users exceeded Facility: LOGIN, Login Processor Explanation: The maximum number of interactive users for which your system is licensed have already logged in. Further logins are currently disabled. The message displayed to the system manager is EXLICENSE. User Action: Log in after another user has logged off. If the maximum number of users is exceeded frequently, ask your system manager whether the system's license can be upgraded. LOGIN - logins are currently disabled - try again later Facility: LOGIN, Login Processor Explanation: Logins are currently disabled. The message displayed to the system manager is LOGDISABLE. User Action: Do not attempt to log in at this time. Try again later. LOGIN - maximum number of users exceeded - try again later Facility: LOGIN, Login Processor Explanation: The installation-defined maximum number of users has been reached. The message displayed to the system manager is EXQUOTA. User Action: Wait and try to log in later, after other users have logged out. LOGIN - no such user Facility: LOGIN, Login Processor Explanation: The specified user name does not exist. This message is not displayed to the user; it is written to the system accounting and security audit records. The message displayed to the user is "User authorization failure"; the message displayed to the system manager is NOSUCHUSER. User Action: None. LOGIN - qualifier not allowed in captive accounts Facility: LOGIN, Login Processor Explanation: You attempted to use qualifiers (for example, /CLI or /DISK) on an account logging in that is a captive account. If the account logging in is a captive account, no qualifiers may be changed. The message displayed to the system manager is CAPTIVE. User Action: Retry without specifying qualifiers. LOGIN - system password timeout Facility: LOGIN, Login Processor Explanation: A user failed to correctly enter the system password within the allotted time period (as defined by the SYSGEN parameter LGI_PWD_TMO). This message is not displayed to the user; it is written to the system accounting and security audit records. The user does not receive a message display when this error occurs. The message displayed to the system manager is SYSPWDTMD. User Action: None. LOGIN - unrecognized qualifier keyword Facility: LOGIN, Login Processor Explanation: An invalid qualifier is specified on the LOGIN command line. The message displayed to the system manager is CLIFAIL. User Action: Verify the command line you entered and repeat the login procedure. LOGIN - user authorization failure Facility: LOGIN, Login Processor Explanation: You incorrectly entered your user name, your password, or both. The message displayed to the system manager is USERAUTH. User Action: Repeat the login procedure. LOGIN - value required on qualifier Facility: LOGIN, Login Processor Explanation: You specified a qualifier without a value. User Action: Verify the command line you entered; specify a value and repeat the login procedure. LOGIN - VMS host system modem not wired correctly - contact your system manager Facility: LOGIN, Login Processor Explanation: The modem connected to the VMS system is not asserting the proper signal control as described in the VMS I/O User's Reference Volume. (This message appears as NOTMODEM to the system manager.) User Action: Contact your system manager. LOGIN - you are at maximum allowed processes for your account name Facility: LOGIN, Login Processor Explanation: No more processes may be logged in under this account. The message displayed to the system manager is ACNTEXC. User Action: Wait until another process logged in under this account has logged out. LOGIN - you are at maximum processes for your user name Facility: LOGIN, Login Processor Explanation: No more processes may be logged in under this user name. The message displayed to the system manager is EXQUOTA. User Action: Wait until another process using this user name has logged out and retry. LOGIN - you are not authorized to do reconnections Facility: LOGIN, Login Processor Explanation: You are not authorized to reconnect to disconnected processes. The message displayed to the system manager is DISRECONNECT. User Action: Log in again without specifying the /CONNECT qualifier after your user name. LOGIN - you are not authorized to log in at this time Facility: LOGIN, Login Processor Explanation: At the present time, you are restricted from the class of login you are attempting. The login classes are: LOCAL, DIALUP, REMOTE, NETWORK, and BATCH. The system manager can restrict your use of each login class at specific times. The message displayed to the system manager is BADHOUR. User Action: If possible, try a different login class. For example, if you are currently restricted from BATCH logins, try an interactive class (LOCAL, REMOTE, or DIALUP). If you are currently restricted from all login classes, you cannot log in until you are permitted to use the system. You may also want to ask your system manager about the login restrictions for your account. LOGIN - you are not authorized to log in from this source Facility: LOGIN, Login Processor Explanation: You do not have authorization for the login class you are attempting from the current source. The login classes are: LOCAL, DIALUP, REMOTE, NETWORK, and BATCH. The system manager can restrict your use of each login class at specific times. The message displayed to the system manager is RESTRICT. User Action: If possible, try a different login class. For example, if you are currently restricted from BATCH logins, try an interactive class (LOCAL, REMOTE, or DIALUP). If you are currently restricted from all login classes, you cannot log in until you are permitted to use the system. You may also want to ask your system manager about the login restrictions for your account. LOGIN - you are not authorized to log in today Facility: LOGIN, Login Processor Explanation: You are restricted from the class of login you have attempted today. The system manager can restrict your use of a login class on specific days. The message displayed to the system manager is BADDAY. User Action: If possible, try a different login class. For example, if you are restricted from BATCH logins today, try an interactive class (LOCAL, REMOTE, or DIALUP). If you are restricted from all classes of logins today, you cannot log in until you are permitted to use the system. You may also want to ask your system manager about the login restrictions for your account. LOGIN - you are not authorized to specify CLI parameters Facility: LOGIN, Login Processor Explanation: You do not have authorization to specify an alternate command language interpreter (CLI), or alternate CLI tables. The message displayed to the system manager is DEFCLI. User Action: Log in again without specifying the /CLI or /TABLES qualifiers after your user name. LOGIN - your account has expired - contact your system manager Facility: LOGIN, Login Processor Explanation: When creating an account, the system manager can limit it to a specific time period, after which the account becomes invalid. Your account has exceeded its time limit. The message displayed to the system manager is ACNTEXPIR. User Action: Ask your system manager to renew your account. LOGIN - your password has expired - contact your system manager Facility: LOGIN, Login Processor Explanation: Your password is valid for a specific length of time as determined by your system manager. When a password reaches the end of its specified time period, it expires and can no longer be used to gain access to the system. This is a system security feature that forces users to change their passwords on a regular basis. You should have been receiving advance messages notifying you when your password would expire. The message displayed to the system manager is PWDEXPIR. User Action: Ask your system manager for a new password.
LOGINIT
logfile initialized by operator 'filespec' logfile is 'filespec' Facility: OPCOM, Operator Communication Process Explanation: A DCL command REPLY/LOG successfully initialized a new operator communication log file. This message is informational. User Action: None.
LOG_IN_USE
unable to locate current end of file - dump aborted Facility: LMCP, Log Manager Control Program Explanation: The attempted log file dump aborted when LMCP was unable to locate the end of the log file because the system was too busy (transaction start rate was too high). User Action: Try the dump again when the system is less active.
LOGIO
NICONFIG requires LOG_IO privilege Facility: CNF, NI Configurator Explanation: NICONFIG must run with LOG_IO privilege. User Action: Install NICONFIG with LOG_IO privilege or run it from an account with LOG_IO privilege.
LOGLINK
network error creating link to node 'node-name::' Facility: MAIL, Mail Utility Explanation: An error occurred when MAIL attempted to use DECnet-VAX to communicate with another system. This message is usually accompanied by a system error message indicating the reason for the error. User Action: Resolve the problem and reenter the command.
LOGNAME
logical name is too long Facility: MOUNT, Mount Utility Explanation: A logical name contains more than 63 characters. User Action: Reenter the command; specify a logical name that has fewer than 63 characters.
LOGNAME
transaction log name is 'file-name' Facility: SYSTEM, VMS System Services Explanation: This informational message identifies the name of the transaction log file. User Action: None.
LOGOPNM
open link to event monitor 'sink-name' at 'dd-mm-yy hh:mm:ss.ms' Facility: EVL, Event Logger Explanation: The event receiver opened a logical link to the specified event monitor program. This informational message displays the name of the program and the time stamp for the operation. User Action: None.
LOGOPNR
connect accepted by event receiver from node 'node-id' at 'dd-mm-yy hh:mm:ss.ms' Facility: EVL, Event Logger Explanation: The event receiver accepted a link from an event transmitter on the specified node. This informational message displays the identification of the node and the time stamp for the operation. User Action: None.
LOGOPNT
open link to event receiver on node 'node-id' at 'dd-mm-yy hh:mm:ss.ms' Facility: EVL, Event Logger Explanation: The event transmitter attempted to open a logical link to the event receiver on the specified node. This informational message displays the identification of the node and the time stamp for the operation. User Action: None.
LOGTIME
logfile time stamp Facility: OPCOM, Operator Communication Process Explanation: This message, written periodically in the operator's log file, indicates that the system is functioning properly at the time specified. User Action: None.
LOGZERNEG
logarithm of zero or negative value Facility: MTH, Mathematics Facility Explanation: The LOG or DLOG math procedure is called with a zero or a negative number. The result returned is the reserved operand, minus zero. User Action: Locate the call to the library procedure that caused the error, and correct the argument that is zero or negative.
LONGDST
unable to include all module names in symbol table Facility: PATCH, Patch Utility Explanation: When you initialized its symbol, the image table could not accommodate all the module names it found. User Action: To determine which modules were placed in the symbol table, enter the PATCH command SHOW MODULE. To make room for the new modules, enter the PATCH command CANCEL MODULE specifying the module names whose symbols are no longer required. Then reenter the PATCH command SET MODULE.
LOOKUPERR
error looking up 'module-name' in 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: The Librarian could not find the requested module in the MNT, a VAX RMS error occurred, or there is not enough virtual memory available. User Action: Reenter the command line specifying an existing module name.
LOSTEXTHDR
file ('file-id') 'filename' lost extension file header
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An extension file header is not in the extension file
header chain of any file. The utility rewrites the file header
with a deleted header, and the blocks allocated to the file header
are marked free. The /CONFIRM qualifier is ignored in this action.
User Action: None.
LOSTHEADER
file ('file-id') 'filename' not found in a directory
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file is not cataloged in a directory.
This error is neither reported nor repaired if any errors occurred
in processing the directories on the volume set.
User Action: If the /CONFIRM qualifier is specified, you may elect
to catalog the file in directory [SYSLOST], or to delete the file.
You may want to rerun the utility after repairs have been made.
LOSTINFO
information for 'name' was lost due to database corruption Facility: QMAN, Queue Manager Explanation: The queue manager detected corruption in the definition of the specified queue, form, or characteristic. The corrupt information was deleted. User Action: Review the full definition of the affected object and correct the definition to include the deleted information. Submit a Software Performance Report (SPR). Create a copy of all *.QMAN$JOURNAL* files using the BACKUP/IGNORE=INTERLOCK command as soon as possible and include the copy with the SPR. Also provide a copy of any messages written to the console or operator log file with the QUEUE_MANAGE or JOB_CONTROL username.
LOSTMSG
broadcast message was lost Facility: LAT, LAT Facility Explanation: LATCP encountered an error while trying to display a broadcast message. User Action: None.
LOSTSCAN
due to directory errors, lost files will not be entered Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: During the directory scan, errors were encountered that were reported by previous messages. Therefore, lost files will not be entered in directory [SYSLOST]. User Action: Refer to the suggested user actions for the previously reported errors, correct the errors, and reenter the command. Low Priority Command Queue Insert Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Call the Digital Services Group.
LOWDISKSPACE
disk space is low on 'disk-name' Facility: QMAN, Queue Manager Explanation: The queue manager is still progressing through its work, but a lack of disk space has been detected. This message indicates a potential problem if preventive action is not taken. The accompanying FREEDISK message provides details. User Action: Purge and delete files to make more space on the disk.
LOWMEMORY
the queue manager process may require more virtual memory than is currently available Facility: QMAN, Queue Manager Explanation: The queue manager is still progressing through its work, but a lack of virtual memory has been detected. This message indicates a potential problem if preventive action is not taken. User Action: You might need to run AUTOGEN to increase the SYSGEN parameter VIRTUALPAGECNT.
LOWQUOTA
one or more account quotas may be too low. Facility: VMSINSTAL, Install Procedures Explanation: When VMSINSTAL begins an installation, it makes sure that your process quotas are valid. This check failed. User Action: You are asked if you want to continue the installation. Digital recommends that you correct this situation before continuing.
LRJACCESSDENIED
access denied Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because access was denied. User Action: Check group codes of the local node against group codes of the object node.
LRJACCESSREJECT
immediate access is rejected Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because immediate access was rejected. User Action: Retry the connection later.
LRJCORRUPT
corrupted request Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because of a corrupted network message. User Action: Retry the connection. Contact the network manager if problems persist.
LRJDELETED
queue entry deleted by server Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the connection request was deleted from the local queue at the object node. User Action: Retry the connection later.
LRJDISABLE
service is disabled Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object service is disabled. User Action: Enable the object service and retry the connection.
LRJILLEGAL
illegal request parameters Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object node detected illegal request parameters or an inconsistency in a LAT command message received from the local node. User Action: Submit a Software Performance Report (SPR).
LRJINUSE
port or service in use Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object port or object service is in use. User Action: Retry the connection when the object service or object port becomes available.
LRJIVPASSWORD
invalid service password Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object service password is invalid. User Action: Retry the connection using the correct service password.
LRJNAMEUNKNOWN
port name is unknown Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the name of the object port you are trying to connect to is unknown. User Action: Verify the object port name and retry the connection.
LRJNOSERVICE
no such service Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the specified object service does not exist. User Action: Verify that the object service name is correct and retry the connection.
LRJNOSTART
session cannot be started Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the session cannot be started. User Action: Try the connection again later.
LRJNOTOFFERED
service is not offered on the requested port Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object service is not offered on the requested port. User Action: Specify a port that offers the desired service.
LRJNOTSUPPORT
requested function is not supported Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because the object node has detected an unsupported command operation message code in a LAT command message received from the local node. User Action: Submit a Software Performance Report (SPR).
LRJRESOURCE
insufficient resources at server Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because of insufficient resources on the object node. User Action: Retry the connection later.
LRJSHUTDOWN
system shutdown in progress Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established because a system shutdown of the object node is in progress. User Action: None.
LRJUNKNOWN
unknown Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the connection cannot be established for an unknown reason. User Action: None.
LRJUSERDIS
user requested disconnect Facility: LAT, LAT Facility Explanation: This LAT rejection message indicates that the session was normally disconnected from the object node. User Action: None.
LRL_MISS
LRL must be specified Facility: SORT, Sort/Merge Utility Explanation: If a record I/O interface subroutine package is selected, the longest record length (LRL) must be passed to SORT in the call. User Action: Specify the LRL.
LSTERR
error generating listing file Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
LSTMSG1
writing listing file Facility: AUTHORIZE, Authorize Utility Explanation: This message is informational. User Action: None.
LSTMSG2
listing file SYSUAF.LIS complete Facility: AUTHORIZE, Authorize Utility Explanation: This is an informational message. User Action: None.
LSTTOTBK
device 'device-name' contains a total of 'number' blocks; 'number' defective blocks detected Facility: BAD, Bad Block Locator Utility Explanation: This informational message details the number of bad blocks. User Action: None.
LTC
line too complicated: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: There is excessive use of boldface, underlining, overstriking, and hyphenation on the line. User Action: Simplify the line.
LUNALRFRE
logical unit number already free Facility: LIB, Library Facility Explanation: A call is made to LIB$GET_LUN to free a logical unit number that is not allocated. User Action: Ensure that you use the correct logical unit number in the call to LIG$GET_LUN.
LUNRESSYS
logical unit number reserved to system Facility: LIB, Library Facility Explanation: A call is made to LIB$GET_LUN to reserve an invalid logical unit number. The range for logical unit numbers is 100 to 119. User Action: Retry the operation specifying a valid logical unit number.
LVSADDER
error encountered testing longword vector-scalar addition Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVSMLTER
error encountered testing longword vector-scalar multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVSSBTER
error encountered testing longword vector-scalar subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVSSHLER
error encountered testing longword vector-scalar shift left Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVSSHRER
error encountered testing longword vector-scalar shift right Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-scalar arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVVMLTER
error encountered testing longword vector-vector multiplication Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVVSBTER
error encountered testing longword vector-vector subtraction Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVVSHLER
error encountered testing longword vector-vector shift left Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
LVVSHRER
error encountered testing longword vector-vector shift right Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error during integer longword vector-vector arithmetic instruction set testing. User Action: Run diagnostics for VAX Vectors or contact the Digital Services Group.
MACHINECHK
machine check while in kernel mode Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable hardware error. Because of the severity of the error, further operation is impossible, or if it is possible, it might corrupt user data. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to one. User Action: Thoroughly test all system hardware components. If no hardware errors are located and if the problem persists, submit a Software Performance Report (SPR). The SPR should describe the conditions at the time of the error, and should include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command to produce the save set.)
MACLBFMTER
macro library format error Facility: MACRO, VAX MACRO Assembler Explanation: A format error occurred in the MACRO library. User Action: Retry the assembly and, if the error still occurs, use the DCL command LIBRARY (see the VMS DCL Dictionary) to re- create the library from the source code.
MACNAMLNG
macro 'macro-name' name is too long in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The name of the macro you attempted to insert into the library exceeds the name-length limit. User Action: Either rename the macro or extend the library's name- length limit. MACRO or KEY required Facility: EDT, EDT Editor Explanation: The EDT command DEFINE is incomplete. You must specify either MACRO or KEY with the EDT command DEFINE using the format DEFINE MACRO or DEFINE KEY. User Action: Reenter the command including either MACRO or KEY.
MAILBOX
mailbox error Facility: CNF, NI Configurator Explanation: An error occurred while reading a mailbox. User Action: See the accompanying message to determine the appropriate action.
MAKEWSLE
make working set list entry error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MANY_TO_ONE
input specifies multiple files, output a single file Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a COPY command which has an input file specification which potentially represents more than one file, and an output specification which gives exactly one file. User Action: Reenter the command with a wildcard output file. EXCHANGE does not append multiple input files into a single output file, if that is what is desired it will be necessary to copy the files to a Files-11 volume and use the VMS COPY or APPEND commands to concatenate them. EXCHANGE can then be used to copy the result file to the output volume.
MAPAREA
file ('file-id') 'filename' invalid map area
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified file has a corrupted map area.
User Action: The damage can probably be repaired by copying the
file to a new version and deleting the original version. It might
be necessary to reconstruct the file from backup media.
MAPCNTZER
attempted to generate zero length map pointer Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MAPHDRBAD
storage map header is bad; volume locked Facility: MOUNT, Mount Utility Explanation: An I/O error is encountered during a mount operation or the header is corrupted. Existing files on the volume can be accessed but other operations, for example, create and delete, are not possible. User Action: Copy the files that are still accessible to a new volume. Reconstruct, as necessary, from backup media.
MATCH
match found against input string Facility: STR, String Manipulation Facility Explanation: A match is found for the input string that is passed to the routine. This message indicates a success. User Action: None.
MATCHED
file specification - 'xxx' records, 'yyy' matches Facility: SEARCH, SEARCH Command Explanation: This informational message displays the name of the file, the number of records searched, and the number of records containing matches. User Action: None. Max input line of 2814749767 exceeded, file input terminated Facility: EDT, EDT Editor Explanation: You attempted to put more than 2,814,749,767 lines into a buffer. EDT stops accepting additional lines when it reaches this limit. User Action: None. Max line number exceeded - lines no longer ascending; resequence recommended Facility: EDT, EDT Editor Explanation: EDT reached the limits of its line numbering capacity. If you continue to add lines to your buffer, EDT is no longer able to number them uniquely. User Action: You should resequence the buffer if you have fewer lines than line numbers. Max number of lines for this buffer exceeded Facility: EDT, EDT Editor Explanation: You cannot add any more lines to this buffer. User Action: You can place any remaining lines in a different buffer.
MAXBAD
bad block table overflow Facility: INIT, INITIALIZE Command and BACKUP, Backup Utility Explanation: The specified volume has too many bad blocks; either the DCL command INITIALIZE cannot initialize the volume or the Backup Utility cannot process the volume. This message generally indicates that the disk volume can no longer be used. User Action: Check the status of the device and reenter the command. If the failure persists, reformat the disk. Notify the system manager. If the failure still persists and the disk pack is under warranty, it should be returned to Digital.
MAXDEV
too many devices Facility: MOUNT, Mount Utility and DISMOUNT, DISMOUNT Command Explanation: More than 16 tape devices were specified in the DCL command MOUNT or the DCL command DISMOUNT. User Action: Reenter the DCL command MOUNT or the DCL command DISMOUNT; specify fewer than 16 devices.
MAXDIF
maximum number of difference records encountered - DIF aborted Facility: DIFF, DIFFERENCES Command Explanation: The number of differences that have been found exceed the number that you specified with the /MAXIMUM_DIFFERENCES qualifier. Therefore, the Differences Utility has terminated, listing only those difference records that it encountered before the maximum is reached. User Action: None.
MAXLAB
too many volume labels Facility: MOUNT, Mount Utility Explanation: More than 16 tape labels were specified in a DCL command MOUNT. User Action: Reenter the DCL command MOUNT; specify fewer than 16 volume labels.
MAXLINKS
maximum links already defined Facility: LAT, LAT Facility Explanation: The link cannot be created because the maximum number of allowable links is already defined. User Action: None.
MAXMAPPEDBUF
a single buffer can be mapped to at most 'count' windows Facility: VAXTPU, VAX Text Processing Utility Explanation: You attempted to map a window to a buffer that already has its maximum upper limit of windows mapped to it. User Action: Map the window to a different buffer.
MAXPARM
too many parameters - reenter command with fewer parameters
Facility: CLI, Command Language Interpreter (DCL)
Explanation: A command contained more than the maximum number of
parameters allowed. This error can be caused by:
o Leaving blanks on a command line where a special character, for
example, a comma or plus sign, is required.
o Using symbol names or logical names which, when substituted or
translated, contain embedded blank characters.
o Failing to place quotation marks around a character string with
embedded blanks.
User Action: Determine the reason for the error and correct the
syntax of the command. Use the DCL command HELP or refer to the
VMS DCL Dictionary to determine the correct number of parameters
for the command.
MAXSERV
maximum number of services exceeded Facility: LAT, LAT Facility Explanation: You attempted to create more than 255 services on the local node. User Action: You must delete a service in order to add one.
MAXTOOBIG
maxunits specified is too large Facility: SYSGEN, System Generation Utility Explanation: The /MAXUNITS qualifier, as specified, caused an overrun in a word-sized length field when the length of the IDB is calculated. User Action: reenter the SYSGEN command CONNECT with a smaller /MAXUNITS number.
MAXUNITS
unit number greater than the maximum units specified Facility: SYSGEN, System Generation Utility Explanation: A unit number is encountered in creating the I/O database that is larger than the maximum number of units allowed (default = 8). User Action: Retry the operation using the /MAXUNITS qualifier on the SYSGEN command CONNECT.
MAXVALUE
maximum value is 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: The argument value that you used exceeds the maximum value allowed. User Action: Use an argument that is within the valid boundaries.
MAXVOLS
too many volumes in volume set 'device-name' Facility: ANALDISK, Analyze/Disk_Structure Utility and BACKUP, Backup Utility Explanation: The volume set count recorded in the home block of relative volume 1 of an input volume set is greater than 255. Possibly, this value has been corrupted. Neither the Backup Utility nor the Analyze/Disk_Structure Utility can process the volume. User Action: Reconstruct the volume set from backup media.
MAYNOTINDX
this mode may not be indexed Facility: MACRO, VAX MACRO Assembler Explanation: The base mode is register, immediate, or literal mode. User Action: Change the addressing mode.
MBACBHUNG
MBA CBHUNG bit set Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MBC
invalid multi-block count Facility: RMS, VMS Record Management Services Explanation: The multiblock count field of the RAB contains an invalid value. The multiblock count must be in the range of 0 to 127. User Action: Verify that the call to the VMS RMS service is coded correctly.
MBFULL
mailbox is full Facility: SYSTEM, VMS System Services Explanation: A write request to a mailbox failed because the mailbox is full and resource wait mode is not enabled. Its reader has not read the messages it contains. User Action: The writer of the mailbox can wait and try to write a message later, if possible. If the error occurs frequently, the amount of buffer space allocated when the mailbox is created should be increased so that more messages can be written before any are read.
MBTOOSML
mailbox is too small for request Facility: SYSTEM, VMS System Services Explanation: A write request to a mailbox failed because the message is larger than the maximum message size specified when the mailbox is created. User Action: Verify that the call to the service is coded correctly. Verify the maximum message size specified for the mailbox, and increase the size if necessary.
MBXASGERR
error assigning channel to vector information mailbox Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
MBXCRERR
error creating operator reply mailbox Facility: MOUNT, Mount Utility Explanation: The reply mailbox could not be created. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
MBXCRTERR
error creating vector information mailbox Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
MBXRDERR
error reading operator reply mailbox Facility: MOUNT, Mount Utility Explanation: You are unable to read a mailbox. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
MBXREDERR
error reading from vector information mailbox Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
MBXWRTERR
error writing to vector information mailbox Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
MCHECK
detected hardware error Facility: SYSTEM, VMS System Services Explanation: A hardware machine check has occurred. User Action: Notify the system manager.
MCHECK
unexpected Machine Check Facility: VAXCLUSTER, VAXcluster Facility Explanation: A machine check exception occurred during bootstrap execution. User Action: Run diagnostics on the satellite to check for hardware problems.
MCHINSTSYN
machine instruction syntax error Facility: MACRO, VAX MACRO Assembler Explanation: A syntax error occurred in an instruction, for example, MOVL, A. User Action: Correct the instruction syntax.
MCNOTVALID
device microcode is not valid Facility: SYSTEM, VMS System Services Explanation: The microcode has not yet been successfully loaded or has become invalid. This is true only for the start microprocessor, initialize LPA11-K, set clock, and start data transfer request. User Action: Contact the Digital Services Group.
MDBSFCRUPT
manufacturer's detected bad sector file is corrupt on 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: The header information in the redundant MDBSF is corrupted. User Action: Have the medium inspected.
MDBSFRFAI
failed to read the manufacturer detected bad sector file on 'device-
name'
Facility: BAD, Bad Block Locator Utility
Explanation: This error can occur as the result of any the
following reasons:
o The Bad Block Locator Utility could not locate a valid MDBSF.
o The Bad Block Locator Utility could not rebuild the MDBSF
and SDBSF as a result of the execution context, for example,
/EXERCISE=KEEP or /BAD_BLOCKS.
o The Bad Block Locator Utility could not locate a track copy
of the SDBSF (before the last track copy) for display purposes
as a result of the execution context /NOEXERCISE/BAD_BLOCKS
/OUTPUT.
User Action: Reinvoke the Bad Block Locator Utility with a
suitable execution context to allow the utility to either display
a converted device's bad block file without any attempt to modify
its contents. Note that the device is converted through the MCR
BAD/OVR command. Do not use the /BAD_BLOCKS qualifier or the
/EXERCISE=KEEP qualifier or allow the Bad Block Locator Utility
to re-create the bad blocks files with the default execution
context of ANALYZE/MEDIA/EXERCISE 'device-name'. This implies
the /EXERCISE=NOKEEP qualifier and no user-supplied bad block
information. Therefore, do not specify the /BAD_BLOCKS qualifier.
MDFYERR
unable to update record Facility: AUTHORIZE, Authorize Utility Explanation: Your record is not updated. User Action: Take corrective action based on the accompanying messages.
MDFYMSG
user records updated Facility: AUTHORIZE, Authorize Utility Explanation: Your records were updated. This is an informational message. User Action: None.
MEDOFL
disk boot driver failure to open boot device Facility: VAXCLUSTER, VAXcluster Facility Explanation: The satellite node could not put its remote system disk on line. User Action: Check the state of the system disk on the boot node. Use the SHOW DEVICE/SERVED command to ensure that the system disk is servable and on line.
MEDOFL
medium is offline Facility: SYSTEM, VMS System Services Explanation: An I/O request cannot be satisfied because the device specified is not on line and does not have a physical volume mounted on it. For example, on a STARTUP request the DEUNA hardware detected that the cable from the DEUNA on the UNIBUS is not connected to the DEUNA bulkhead panel. User Action: Connect the cable from the DEUNA module on the UNIBUS to the DEUNA bulkhead panel. Mount the required volume on the device and repeat the request.
MEI
missing at least one .ENDIF command Facility: RUNOFF, DIGITAL Standard Runoff Explanation: End-of-file is detected and at least one conditional DSR command (.IF/.IFNOT) is not legally terminated. User Action: Insert the missing conditional commands. Check to see that DSR commands .IF/.ENDIF are matched within .REQUIRE files.
MEMBUG
dynmem error size = 'nn' addr = 'nn' error = 'nn' Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report with a copy of the Image File and the Link Map. Indicate the information contained in the error message.
MEMBUG
memory (de)allocation bug 'number', 'address', 'number' Facility: LINK, Linker Utility Explanation: There is a problem with the linker. User Action: Submit a Software Performance Report (SPR).
MEMERRS
errors occurred writing memory contents to the dump file Facility: SDA, System Dump Analyzer Explanation: The first block of the dump file contains information indicating that there were errors while writing out the contents of memory to the dump file. User Action: None. The dump file might not be useful for analysis.
MEMFUL
insufficient virtual address space to complete this link Facility: LINK, Linker Utility Explanation: Your virtual address space is not large enough to complete the link. User Action: Either increase the virtual address space available or decrease the size of the image. You can decrease the size of the image by (1) using shareable images or by (2) encouraging demand-zero compression if the image contains large data arrays. Contact your system manager to increase your VIRTUALPAGCNT or PAGFILQUOTA.
MEMNOTSVD
memory not saved in the dump file Facility: SDA, System Dump Analyzer Explanation: An attempt was made to examine the contents of a physical memory location that was not saved when the subsetted dump file was written. The requested information is not contained in the dump file. User Action: None. Memory dump complete Facility: SYSTEM, VMS System Services Explanation: No errors were encountered during the dump write. This message indicates a normal status. User Action: None. Memory dump complete after 'nn' write error(s) Facility: BUGCHECK, System Bugcheck Explanation: This message indicates that the memory dump is finished; however, there are one or more write errors. User Action: When the system reboots, copy the dump to another file. You can determine the text associated with the hexadecimal status of pervious messages by using the F$MESSAGE lexical function or its equivalent. If the status indicates a possible disk problem, see the user action for the accompanying message. Memory dump complete after "nn" write errors Facility: SYSTEM, VMS System Services Explanation: Errors were encountered during the dump write operation. User Action: Be aware that analysis of the crash dump might not be possible. Memory dump incomplete - dump file "nn" blocks too small Facility: SYSTEM, VMS System Services Explanation: Output after writing out the memory dump if there is no room in the dump file before writing out the full contents of physical memory and the dump file is at least two blocks too small. User Action: Make the memory dump file larger. Memory dump incomplete - dump file 1 block too small Facility: SYSTEM, VMS System Services Explanation: Output after writing out the memory dump if there is no room in the dump file before writing out the full contents of physical memory and the dump file is one block too small. User Action: Make the memory dump file larger. Memory dump incomplete - dump file 'nn' blocks too small Facility: BUGCHECK, System Bugcheck Explanation: This message indicates that the system was unable to write out the remaining 'nn' pages of a complete, physical memory dump (SYSGEN parameter DUMPSTYLE set to 0). The dump cannot be used because analysis depends on the System Page Table, which is kept in the uppermost physical pages of memory (that is, the last data to be written if this style of dump is written). User Action: If you have room on the volume that holds the system dump file, you can expand the dump file. If space is limited, you can try to write a selective dump. Refer to the Guide to Setting Up a VMS System for the correct procedures.
MERGE
'n' records to be merged Facility: ACCOUNTING, Accounting Utility Explanation: When the /LOG qualifier is used with the /SORT qualifier, this informational message describes the number of records to be sorted. User Action: None. Message Free Queue Insert Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Contact the Digital Services Group. Message Free Queue Remove Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Call the Digital Services Group.
MFN
number illegal or malformed: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A plus sign (+) or a minus sign (-) is used alone, instead of +n or -n. User Action: Insert the n value.
MFS
missing or improperly delimited file spec: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The file specification for the DSR command .REQUIRE is not enclosed in apostrophes or quotation marks. User Action: Enclose the file specification in apostrophes or quotation marks.
MFYNULPGFL
FREWSLE - no backing store, page not modified Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MGTPRM
management program error Facility: NCP, Network Control Program Explanation: A software error occurred in the network management software. User Action: Submit a Software Performance Report (SPR).
MHDERR
module header error for 'module-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: The specified module has an invalid header. User Action: Compress the library before reentering the command line. Micro-code Verification Error Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts it marks the device off line. User Action: Call the Digital Services Group to check the port hardware.
MINVALUE
minimum value is 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: You specified an argument value that is less than the minimum value allowed. User Action: Specify an argument that is within the valid boundaries.
MIRBFOVF
mirror buffer exceeded Facility: MOM, Maintenance Operation Module Explanation: An attempt to allocate a buffer to be used for a LOOP NODE or LOOP EXECUTOR command has failed. This might be because virtual memory has been exhausted. User Action: Increase the amount of virtual memory available for the process.
MIRCTF
mirror connect failed 'error' Facility: NCP, Network Control Program Explanation: This error occurs if the connection to a loopback mirror fails. A loopback mirror is a process created by the Network Control Program command LOOP NODE to transmit test messages. The 'error' indicates the reason for the connection failure. Some possible reasons for connection failure are an invalid or unrecognizable node name, a lack of network resources, or a busy or unreachable node. User Action: If the error occurred because of an incorrect node identifier, correct the identifier and reenter your command. If network resources are currently insufficient or if the node is inaccessible, reenter your command when the network and node become available.
MIRDIS
mirror link disconnected 'error' Facility: NCP, Network Control Program Explanation: This error occurs if the connection to a loopback mirror is made but subsequently disconnected. A loopback mirror is a process created by the Network Control Program command LOOP NODE to transmit test messages. The 'error' indicates the reason for the disconnection. User Action: If the error occurred because of an incorrect node identifier, correct the identifier and reenter your command. If network resources are currently insufficient or if the node is inaccessible, reenter your command when the network and node become available.
MISCONFUNI
unibus/qbus 'device-name' is misconfigured Facility: SYSGEN, System Generation Utility Explanation: The vector on the device specified in the message needs to be changed. User Action: Call Field Service.
MISENDSTA
missing END statement Facility: SMG, Screen Management Facility Explanation: The Termtable compiler expected an END statement to terminate the current terminal definition and this END statement is missing. User Action: Check your terminal definitions.
MISFILSPE
missing file specification in REQUIRE statement Facility: SMG, Screen Management Facility Explanation: The REQUIRE statement needs a file name in order to locate external definitions which should become part of your Termtable. User Action: Check your TERMTABLE.TXT. Add a file name to the REQUIRE statement.
MISNAMREQ
expected NAME or REQUIRE Facility: SMG, Screen Management Facility Explanation: The Termtable compiler expected TERMTABLE.TXT to begin with a terminal definition NAME statement or a REQUIRE statement. Something else is encountered. User Action: Check your TERMTABLE.TXT.
MISREQPAR
missing required parameter Facility: JBC, Job Controller Explanation: An item code that is required for the requested function is not present. User Action: Specify the required item.
MISSINGEND
missing .END statement Facility: MACRO, VAX MACRO Assembler Explanation: There is no .END directive at the end of the module. The assembler inserted an .END directive after the last line. User Action: Insert an .END directive.
MISSINGQUOTE
missing quote Facility: VAXTPU, VAX Text Processing Utility Explanation: Your program has an opening quote character without a matching closing quote on the same line. User Action: Add the missing closing quote and recompile your program.
MISSNGPARM
missing parameter 'parameter-name' Facility: CDU, Command Definition Utility Explanation: The parameters specified for a designated verb in the command definition file are not consecutively named P1, P2, _ . . . User Action: Rename the parameters consecutively.
MISSNGSYM
missing argument Facility: CDU, Command Definition Utility Explanation: A required argument is missing from the CLD file. User Action: Add the missing argument to your CLD file.
MISS_PARAM
a required subroutine parameter is missing Facility: SORT, Sort/Merge Utility Explanation: You have omitted a required argument. User Action: Identify which argument is missing and specify it.
MISSPASS
missing PASSWORD command Facility: INPSMB, Input Symbiont Explanation: A batch job entered from a card reader does not contain a PASSWORD command following the JOB command. User Action: Correct the error and reenter the job.
MISSQUO
unmatched quotation marks in argument Facility: PATCH, Patch Utility Explanation: You did not use matching quotation marks or apostrophes to enclose an argument. User Action: Reenter the command using the correct quotation.
MISSQUOTE
quoted string not terminated before end of line Facility: CDU, Command Definition Utility Explanation: CDU encountered an end-of-line while reading a quoted string from a CLD file. User Action: Edit the CLD file so that quoted strings do not cross line boundaries.
MISSYMTAB
missing symbol table Facility: VAXTPU, VAX Text Processing Utility Explanation: A required symbol table is missing. User Action: Use the required symbol table or create one.
MISTERNAM
definition must begin with a terminal name Facility: SMG, Screen Management Facility Explanation: Capabilities were preceded by the name of a terminal. User Action: Check your terminal definitions. Make sure that each definition starts with NAME = 'terminal-name'.
MIXEDTYPES
operator with mixed or unsupported data types Facility: VAXTPU, VAX Text Processing Utility Explanation: An operator is being used with operands of different or unsupported data types. User Action: Check the data type of each operand being used and make sure that the operator supports this.
MKD
ACP could not mark file for deletion Facility: RMS, VMS Record Management Services Explanation: The file system ACP cannot delete the file. This message is associated with a system status code returned from a file system ACP QIO requests made by VMS RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
MLBOPNERR
error opening macro library Facility: MACRO, VAX MACRO Assembler Explanation: An error occurred while attempting to open a macro library. User Action: Ensure that the file specification is a valid macro library.
MNL
missing number or letter: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A required numerical value or text value is missing. User Action: Insert the missing value.
MODIFIED
'file/directory/volume' modified Facility: SET, SET Facility Explanation: The requested file, directory, or volume is modified. This message is displayed when you specify the /LOG qualifier. The operation is successful. User Action: None.
MODIFYERR
modify error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: A VMS RMS $MODIFY request failed because of the error code, represented as 'xx'. User Action: Correct the error (represented as xx) and retry the request.
MODLINK
modified link 'link-name' Facility: LAT, LAT Facility Explanation: The specified link has been modified by LATCP. User Action: None.
MODNAM
module 'module-name' name length is illegal - not 1 to 'decimal- number' Facility: LINK, Linker Utility Explanation: A module contained a header record with an invalid module name. User Action: Submit a Software Performance Report on the appropriate language processor.
MODNAMLNG
illegal module-name 'module-name' of 'nnn' characters in 'library- name ' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The name of the object module you attempted to insert into the library exceeds the name-length limit. User Action: Rename the module before inserting it into the library.
MODNODE
modified characteristic(s) of local node Facility: LAT, LAT Facility Explanation: Characteristics of the local node have been modified by LATCP. User Action: None.
MODNOTADD
insufficient symbol table space to add module 'module-name'
Facility: PATCH, Patch Utility
Explanation: The PATCH command SET MODULE failed. This typically
occurs when there is not enough space in the symbol table to
accommodate the additional module or modules.
User Action: To make room for the new modules, enter the following
PATCH commands:
o SHOW MODULE command to determine which modules are in the
symbol
o CANCEL MODULE command specifying the module names whose symbols
are no longer required
o SET MODULE command
MODNOTFND
library module 'module-name' not found in record 'number' Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont library input routine indicating the specified library module is not found while processing this record. The print symbiont failed to locate the specified module in the device control library associated with this queue. User Action: Insert the library module or specify the correct module library.
MODOUTAI
RMS after-image journaling disabled on saved copy of 'filespec' Facility: BACKUP, Backup Utility Explanation: After-image journaling has been disabled on the saved copy of the file. This message is informational. User Action: None.
MODOUTAIS
RMS after-image journaling disabled on saved copy of 'filespec'
('file-id')
Facility: BACKUP, Backup Utility
Explanation: After-image journaling has been disabled on the saved
copy of the file in the standalone BACKUP operation. That is, if
the disk is restored, the journal command must be reentered. This
message is informational.
User Action: None.
MODOUTBI
RMS before-image journaling disabled on saved copy of 'filespec' Facility: BACKUP, Backup Utility Explanation: Before-image journaling has been disabled in the BACKUP operation. That is, if the disk is restored, the journal command must be reentered. This message is informational. User Action: None.
MODOUTBIS
RMS before-image journaling disabled on saved copy of 'filespec'
('file-id')
Facility: BACKUP, Backup Utility
Explanation: Before-image journaling has been disabled on the
saved copy of the file in the standalone BACKUP operation.
That is, if the disk is restored, the journal commands must be
reentered. This message is informational.
User Action: None.
MODPORT
modified port 'port-name' Facility: LAT, LAT Facility Explanation: The specified port has been modified by LATCP. User Action: None.
MODQUOTA
error modifying quota record for ['UIC'] Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to modify the usage data in the quota file entry for the specified UIC. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
MODRANGEMARKS
MODIFY_RANGE requires either two marks or none Facility: VAXTPU, VAX Text Processing Utility Explanation: You must specify both new ends of the range to be modified or that there are no new ends. User Action: Correct the call to MODIFY_RANGE, using the BEGINNING_OF or END_OF built-in procedure.
MODRELNBAK
no backing store address for modified page Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MODSERVICE
modified service 'service-name' Facility: LAT, LAT Facility Explanation: The specified service has been modified by LATCP. User Action: None.
MOUNEWVOL
MOUNT new relative volume nn (volume label) on 'device-name' Facility: MOUNT, Mount Utility Explanation: During a write operation, the end-of-tape has been reached on the last reel of a volume set. User Action: Mount a new relative volume to be added to the tape set.
MOUNTDEV
please mount 'name' device 'device-name' Facility: MOUNT, Mount Utility Explanation: A request for operator assistance on MOUNT has occurred. User Action: You can wait for operator assistance, perform the request yourself, or abort the request.
MOUNTED
'volume-label' mounted on 'device-name' Facility: MOUNT, Mount Utility Explanation: This is an informational message that verifies a request. User Action: None.
MOUNTERR
volume 'volume' on 'device' was not mounted because 'reason'
Facility: BACKUP, Backup Utility
Explanation: BACKUP was unable to mount the specified volume for
one of the following reasons:
o The expiration date specified in the volume label is in the
future. That is, the data on the volume has not expired.
o Its label does not match the one requested. The label specified
in the BACKUP command (either explicitly or implicitly) does
not match the label on the volume.
o It is protected against access. The protection specified in
the volume header disallows access by the person entering the
BACKUP command.
User Action: At this point BACKUP allows you to either quit
the operation, overwrite the volume label and continue, or put
a new volume in the drive and continue processing. To abort
the operation, enter the QUIT command at the BACKUP> prompt.
To overwrite information in the volume header and continue
processing, enter the OVERWRITE command at the BACKUP> prompt. To
restart the operation with a new volume, enter the NEW command at
the BACKUP> prompt. If the QUIT or NEW command is chosen, BACKUP
will automatically dismount the volume.
MOUNTERROR
error occurred during VMS mount on 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encounted an error while using the $MOUNT system service to mount a volume. User Action: A second message will follow, giving the specific condition discovered by the $MOUNT service. Take corrective action based on the second message.
MOUNTF11
'filespec' must be mounted Files-11 Facility: BACKUP, Backup Utility Explanation: The specified volume is mounted with the /FOREIGN qualifier. However, for the given operation, the volume must be mounted without the /FOREIGN qualifier. User Action: Reevaluate the operation, checking that the correct I/O devices have been specified and that the /SAVE_SET, /PHYSICAL, and /IMAGE qualifiers are properly used. Then, if appropriate, mount the specified volume without the /FOREIGN qualifier, and reenter the command.
MOUNTFOR
'device' must be mounted /FOREIGN Facility: BACKUP, Backup Utility Explanation: The specified volume is mounted without the /FOREIGN qualifier. However, for the given operation, the volume must be mounted with the /FOREIGN qualifier. User Action: Reevaluate the operation, checking that the correct I/O devices have been specified and that the /SAVE_SET, /PHYSICAL, and /IMAGE qualifiers are properly used. Then, if appropriate, mount the specified volume with the /FOREIGN qualifier, and reenter the command. MOUNTVER 'shadow-unit' all shadow set copy operations are completed Facility: SYSTEM, VMS System Services Explanation: All required shadowing copy operations have been completed for the named shadow set virtual unit. The shadow set is not internally consistent and is fully subject to normal shadowing data propogation and availability rules. User Action: None. MOUNTVER 'device-name' contains the wrong volume. Mount verification in progress. Facility: SYSTEM, VMS System Services Explanation: The media in the named disk or tape drive has been changed and is no longer that expected by the system. Mount verification recovery procedures started. User Action: Return the correct media to the named disk or tape drive. MOUNTVER 'shadow-unit' contains zero working members Facility: SYSTEM, VMS System Services Explanation: The named shadow set virtual unit has no working member drives. Accompanying "possible shadow set member" messages name previously working member drives that mount verification expects to be returned to operational status. User Action: Take action to make one of the subsequently named member drives operational. MOUNTVER 'shadow-unit' does not contain the member named to VMB. System may not reboot. Facility: SYSTEM, VMS System Services Explanation: The named shadow set virtual unit is the virtual unit from which the system has been booted. For this partictuar shadow set virtual unit, the single shadow set member named in the input to the primary bootstrap program (VMB) is no longer a shadow set member. Because of shadow set booting mechanics, this condition may render the system unbootable. User Action: The single shadow set member named in the input to the primary bootstrap program (VMB) MUST be returned as a member of the system disk shadow set ASAP. MOUNTVER 'device-name' has aborted mount verification Facility: SYSTEM, VMS System Services Explanation: Mount verification was unable to restore access to the named disk or tape. Either access could not be restored in the timeout interval specified by system parameters, or an error occurred during the attempts to restore access from which no recovery was possible. User Action: The named disk or tape is inaccessable to system users. Access can be restored only by dismounting and remounting device. MOUNTVER 'member-unit' has been removed from shadow set Facility: SYSTEM, VMS System Services Explanation: The named shadow set member unit has been removed from its shadow set. The name of the shadow set virtual unit appears in an accompanying "shadow set has been reduced" message. User Action: Correct the problem that caused the member's removal and return the member to the shadow set using a MOUNT command. MOUNTVER 'device-name' has been write-locked. Mount verification in progress Facility: SYSTEM, VMS System Services Explanation: The write-locking hardware on the named disk or tape drive was activated at a time when there is write activity for the device. Mount verification recovery procedures have started. User Action: Deactivate the write-locking hardware on the named disk or tape. MOUNTVER 'device-name' has completed mount verification Facility: SYSTEM, VMS System Services Explanation: The previously named problem, which initiated mount verification is corrected. Normal access is restored to the named disk or tape. User Action: None. MOUNTVER 'member-unit' is a possible shadow set member Facility: SYSTEM, VMS System Services Explanation: The named member drive was recently operational in a shadow set that has been reduced to zero working members. The name of the affected shadow set virtual unit appears in a previous "zero working members" message. User Action: Take action to make the member drive operational. MOUNTVER 'member-unit' is an incorrect shadow set member volume. Facility: SYSTEM, VMS System Services Explanation: The media in the named member drive has been changed and is no longer that expected. In most cases, this message is followed by a message indicating that the named member has been removed from the shadow set. However, if the shadow set has been reduced to zero members, mount verification does not remove the member drive but waits for the correct media to be returned to the member drive. User Action: If the member is not removed from the shadow set, return the correct media to the named member drive. MOUNTVER 'device-name' is offline. Mount verification in progress Facility: SYSTEM, VMS System Services Explanation: The named disk or tape is off line. Mount verification recovery procedures have been initiated. User Action: If manual intervention is required to make the named disk or tape operative, perform the necessary action. For example, if a disk has become off line because its unit plug was removed, replace the unit plug. MOUNTVER 'member-unit' shadow copy has been completed Facility: SYSTEM, VMS System Services Explanation: A previously initiated shadowing copy operation, targeted at the named member drive, finished. User Action: None. MOUNTVER 'member-unit' shadow copy has been started Facility: SYSTEM, VMS System Services Explanation: A shadowing copy operation started with the named member drive as its target. User Action: None. MOUNTVER 'shadow-unit' shadow set has been reduced Facility: SYSTEM, VMS System Services Explanation: The named shadow set virtual unit has had one or more members removed, as described in previous "member has been removed" messages. User Action: Correct the problem that caused the member's removal and return the member to the shadow set using a MOUNT command. MOUNTVER 'shadow-unit' shadow set has changed state. Mount verification in progress. Facility: SYSTEM, VMS System Services Explanation: The named shadow set virtual unit has signaled a possible change of membership or accessibility status. Mount verification recovery procedures have been initiated. User Action: No action is necessary unless indicated by additional mount verification messages.
MOUSEINV
mouse location information is invalid Facility: VAXTPU, VAX Text Processing Utility Explanation: The mouse information is only valid after a mouse key has been received. You are attempting to use a mouse function before a mouse key is pressed. User Action: Mouse functions should only be called by procedures bound to the mouse keys.
MOUVOL
MOUNT relative volume 'nn' on 'device-name' Facility: MOUNT, Mount Utility Explanation: During a read operation, the operator is requested to mount the next reel in a multivolume set. User Action: Mount the indicated reel on the device specified.
MOVEFILES
files will now be moved to their target directories. Facility: VMSINSTAL, Install Procedures Explanation: If sufficient disk space is available at the beginning of an installation, VMSINSTAL builds new files in a working directory for the optional product or update. After all the files are built, they are moved to their target directories. This message is informational. User Action: None.
MOVETOCOPY
move from unmodifiable buffer 'string' changed to copy Facility: VAXTPU, VAX Text Processing Utility Explanation: You cannot change the source buffer, so the MOVE_TEXT request has been changed to a COPY_TEXT. User Action: Use the SET (MODIFIABLE, . . . ) built-in to allow modifications.
MQS
missing or improperly delimited quoted strings: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A beginning or ending apostrophe or quotation mark is missing from the quoted text value. User Action: Insert the missing apostrophe or quotation mark.
MRC
another n crossed margin or bad right indent attempts detected and accumulated. Now being reported Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A specific number (n) of similar horizontal spacing errors have been detected and are now being reported. These errors are triggered by DSR commands .CHAPTER or .APPENDIX or by the end- of-file. The count of errors is cleared after each DSR command .CHAPTER and .APPENDIX or after the end-of-file. User Action: Check the margin and indent settings.
MRG
margins crossed, or attempted indent too far right Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The right margin has crossed the left margin or the left margin has crossed the right margin, or an invalid indent has been specified. User Action: Check the margin and indent settings.
MRGGTMTCH
value of 'x' for /MERGE is greater than /MATCH value of 'y' /MERGE set to 'y' Facility: DIFF, DIFFERENCES Command Explanation: You specified a /MERGE value greater than the /MATCH value. User Action: Decrease the /MERGE value. The /MERGE value must always be less than or equal to the /MATCH value.
MRN
invalid maximum record number or record number exceeds MRN
Facility: RMS, VMS Record Management Services
Explanation: An incorrect record number is specified in one of the
following ways:
o The maximum record number field contains a negative value for
the creation of a relative file.
o The relative record number (pointed to by KBF) for a random
operation to a relative file exceeds the maximum record number
specified when the file is created.
User Action: Verify that the call to the VMS RMS service is coded
correctly. Modify the program, if necessary, to detect and respond
to the condition.
MRS
invalid maximum record size Facility: RMS, VMS Record Management Services Explanation: The maximum record size (MRS) field contains zero for a $CREATE operation with fixed length records or a relative file. Or the maximum record size specified for a magnetic tape file is less than 18. User Action: Verify that the call to the VMS RMS service is coded correctly.
MRS
missing one or more .RESTORE commands at end of file Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You have specified fewer .RESTORE commands than .SAVE commands. User Action: Specify the correct number of .RESTORE commands.
MSCPNOTLD
MSCP-Server code not loaded Facility: SET, SET Facility and SHOW, SHOW Command Explanation: The code for the MSCP Server is not loaded at system generation. User Action: Make sure the MSCP Server code is loaded before trying to enter the SET DEVICE command or the SHOW DEVICE command.
MSCPSERV
encountered unrecoverable error Facility: MSCP, MSCP Server Explanation: The MSCP server encountered an unrecoverable error. User Action: Submit a Software Performance Report (SPR). Include a copy of the crash dump with the Report (SPR).
MSGBUFSET
attempt to change modifiable setting of message buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: The message buffer cannot be set to be either modifiable or unmodifiable. User Action: Do not attempt to change the modifiable setting of the message buffer.
MSGCMAIIF
missing comma in .IIF statement Facility: MACRO, VAX MACRO Assembler Explanation: The condition is not separated from the statement in an .IIF directive. User Action: Insert a comma in the directive.
MSGNOTFND
message not in system message file Facility: SYSTEM, VMS System Services Explanation: A message identification number specified in a system service call or a lexical function does not have a message associated with it. User Action: Check for a programming error.
MSGNOTFND
message was not found, the default message has been returned Facility: VAXTPU, VAX Text Processing Utility Explanation: The message identification code that you specified was not found. The default message is returned. User Action: None.
MSGQUEEMPTY
free message queue empty; requestor PID: 'pid' Facility: AUDSRV, Audit Server Explanation: The audit server encountered an unexpected internal error. User Action: Please submit a Software Performance Report (SPR) and include the process dump file SYS$SYSROOT:[SYSEXE]AUDIT_ SERVER.DMP, if one exists.
MSNGENDS
missing or misspelled ENDSUBROUTINE statement detected while scanning for label Facility: CLI, Command Language Interpreter (DCL) Explanation: A SUBROUTINE command with no ending ENDSUBROUTINE command or with a misspelled ENDSUBROUTINE command was detected while executing a CALL command. This condition can prevent the CALL command from locating an existing destination label. User Action: Check the command procedure for one or more missing or misspelled ENDSUBROUTINE commands; correct as necessary.
MSTINTERR
error initializing master process Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
MTLBLLONG
label specified for 'device-name' is longer than 6 characters Facility: INIT, INITIALIZE Command Explanation: The label the operator specified for the device is longer than six characters. User Action: Respecify the label with 6 or fewer characters.
MTLBLLONG
magnetic tape volume label can be no more than six characters Facility: SYSTEM, VMS System Services Explanation: The label specified for a magnetic tape volume has more than six characters.
MTLBLNONA
label specified for 'device-name' contains non-ANSI "a" characters Facility: INIT, INITIALIZE Command Explanation: The operator used invalid ANSI "a" characters in the volume label. The set of valid ANSI "a" characters includes: digits 0-9, uppercase A-Z, space, and ! " % & ' () * + , - . / : ; < = > ? User Action: Reenter the command with valid ANSI "a" characters.
MTXCNTNONZ
mutex count nonzero at system service exit Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system automatically reboots if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
MULCLUOPT
cluster 'cluster-name' multiply defined in options file 'filename' Facility: LINK, Linker Utility Explanation: A cluster is defined more than once in an options file. User Action: Delete one of the definitions and relink.
MULDEF
symbol 'symbol-name' multiply defined in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A global symbol is defined with different values. User Action: Delete one of the definitions and relink.
MULDEFLBL
multiple definition of label Facility: MACRO, VAX MACRO Assembler Explanation: The same label is defined twice in the module. User Action: Delete the second label definition or change one of the labels to a different symbol name.
MULDEFPSC
psect 'psect-name' multiply defined in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A psect is defined more than once in a single object module. User Action: Correct the source, recompile, and relink.
MULPRI
multiple primary definition in statement 'number' Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility Explanation: The same primary attribute was specified in more than one place in the FDL file. The line number given is where the second definition appears. User Action: Delete one of the definitions.
MULPSC
conflicting attributes for psect 'psect-name' in module 'module- name' file 'filename' Facility: LINK, Linker Utility Explanation: The attributes for a psect were found to be different in subsequent modules of the link. User Action: Correct the source so that all instances of the same psect have the same attributes.
MULSEC
multiple secondary definition in statement 'number' Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility Explanation: The same secondary attribute was specified in more than one place in a primary. The line number is where the second definition appears. User Action: Delete one of the definitions.
MULSHRPCS
psect 'string' defined in shareable image 'image name' is multiply defined in shareable image 'image name' Facility: LINK, Linker Utility Explanation: A program section defining COMMON area (such as those used in VAX BASIC, VAX PL/I, VAX FORTRAN, and VAX C) is defined in two shareable images. The linker is not able to properly resolve references to it. User Action: For further information on Sharable Images, refer to the the Linker Utility in the VMS Linker Utility Manualwhich explains how to link COMMON areas.
MULTALLOC
file ('file-id') 'filename' multiply allocated blocks VBN 'n' to 'n'
LBN 'n' to 'n', RVN 'n'
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified logical blocks on the specified
relative volume were allocated to more than one file. These blocks
are the specified virtual blocks of the specified file.
User Action: Examine all the multiply allocated blocks messages
to determine the files involved in each instance of multiple
allocation. Then, without allowing other file activity, perform
the following functions:
o Copy all but one file involved in each instance to a new
version.
o Delete the version of each file that is copied that contains
the multiple allocation. This action marks blocks free in the
storage bit map that are not, in fact, free blocks.
o Reenter the ANALYZE/DISK_STRUCTURE command using the /REPAIR
qualifier to correct the storage bit map.
o Examine each file for corruption and reconstruct from backup
media as necessary.
MULTCHNG
attribute cannot be specified twice Facility: CDU, Command Definition Utility Explanation: You specified multiple syntax for a single qualifier. User Action: Include one syntax reference for each qualifier.
MULTECO
multiple eco levels ('nn' and 'nn') set for one patch
Facility: PATCH, Patch Utility
Explanation: You attempted to define a second ECO level before
setting the first ECO level.
User Action: To set the first ECO level, enter the PATCH Utility
command UPDATE.
MULTEXTHDR
file ('file-id') 'filename' multiply allocated extension file header
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The specified extension file header is in the
extension header chain of more than one file.
User Action: The damage can be repaired by copying the volume to
fresh media or by copying all the files to new versions and then
deleting the original versions. Examine each file for corruption
and reconstruct from backup media as necessary.
MULTFR
multiply defined transfer address in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: More than one object module contains a strong transfer address. User Action: Delete all but one of the transfer addresses.
MULTIDEF
parameter/local/constant 'name' multiply defined Facility: VAXTPU, VAX Text Processing Utility Explanation: The parameter, local, or constant is defined more than once. User Action: Rename the parameter, local, or constant so that it has a unique name.
MULTIPLENAMES
there is more than one name matching, all are returned Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure EXPAND_NAME has found more than one name matching the given string and has returned a string of concatenated names that match. User Action: None.
MULTISELECT
multiple identical CASE selectors Facility: VAXTPU, VAX Text Processing Utility Explanation: Multiple identical selectors were specified in a single CASE statement or error condition handler. User Action: Specify a selector only once.
MULTOPR
multiple successive operators in expression Facility: PATCH, Patch Utility Explanation: You entered an expression containing adjacent operators. User Action: Use angle brackets or parentheses, depending on the current language, to separate the operators or enter a valid expression.
MULTRMS
multiple RMS vectors specified Facility: SYSTEM, VMS System Services Explanation: This severe error message is associated with a status code returned from a system service request. Multiple VMS RMS vectors have been specified for privileged shareable images. User Action: Only one VMS RMS vector can be specified for an executable image. Remove the vector associated with the problem and relink.
MUSTBECONST
expression must be a compile-time constant Facility: VAXTPU, VAX Text Processing Utility Explanation: The compiler requires a compile-time-constant- expression, and the expression used does not meet these criteria. User Action: Evaluate and correct the expression.
MUSTBEONE
string must be 1 character long Facility: VAXTPU, VAX Text Processing Utility Explanation: A keyname must be 1 character only. User Action: Enter the string again using a 1-character keyname.
MUSTCLOSEFL
must close file Facility: SYSTEM, VMS System Services Explanation: No more operations can be performed on a file, for example, because the position on a magnetic tape is lost. The file must be closed before processing can continue. User Action: Retry the operation; take corrective action based on previously reported errors.
MVABORTED
'date-time', Mount verification aborted for device 'device-name' Facility: OPCOM, Operator Communication Process Explanation: The mount verification was aborted for some reason, possibly because the volume was compromised. User Action: Dismount and remount the volume.
MVCOMPLETE
'date-time', Mount verification completed for device 'device-name' Facility: OPCOM, Operator Communication Process Explanation: Mount verification has successfully completed. User Action: None.
NAFADDERR
unable to add record to NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The record you specified could not be added to the network user authorization file (NETPROXY.DAT). This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. For example, this error occurs if you try to add a record authorizing a remote user to access more than one local account. Each user at a remote node is allowed to access the files of only one user on the local node. User Action: If possible, correct the condition identified by the VMS RMS message and reenter your command. Otherwise, examine the network user authorization file to determine why the record could not be added. You can display the contents of the file by using the AUTHORIZE command SHOW/PROXY. You can write the contents of NETPROXY.DAT to a listing file by using the AUTHORIZE command LIST /PROXY. If you want to delete a current record from NETPROXY.DAT in order to add a new record, use the AUTHORIZE command REMOVE /PROXY.
NAFAEX
NETPROXY.DAT already exists Facility: AUTHORIZE, Authorize Utility Explanation: A network user authorization file (NETPROXY.DAT) already exists for the local node. User Action: If you want to create a new network user authorization file, either delete or rename the current one (if you have sufficient privilege to do so). Once the current file has been deleted or renamed, reenter the AUTHORIZE command CREATE /PROXY. Note that you must have sufficient privilege to create a new file.
NAFCONERR
connect error on NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: Connect error on to network user authorization file (NETPROXY.DAT). User Action: Take corrective action based on the accompanying messages.
NAFCREERR
unable to create NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: A network user authorization file (NETPROXY.DAT) could not be created. This message should be accompanied by a VMS RMS message that identifies the specific reason why the file could not be created. For example, this error occurs if you do not have sufficient privilege to create the file. User Action: Correct the condition identified by the RMS message and reenter your command.
NAFDNE
NETPROXY.DAT does not exist Facility: AUTHORIZE, Authorize Utility Explanation: A network user authorization file (NETPROXY.DAT) does not exist on the local node. User Action: If you have sufficient privilege, use the AUTHORIZE command CREATE/PROXY to create a network user authorization file. Then you can add records to the file by using the AUTHORIZE command ADD/PROXY.
NAFDONEMSG
network authorization file modified Facility: AUTHORIZE, Authorize Utility Explanation: The network user authorization file (NETPROXY.DAT) has been modified to reflect the change directed by your command. User Action: None.
NAFNOMODS
no modifications made to network authorization file Facility: AUTHORIZE, Authorize Utility Explanation: No modifications have been made to the network user authorization file (NETPROXY.DAT). User Action: None.
NAFUAEERR
entry already exists in NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The record you have tried to add to the network user authorization file is already in the file; it has not been duplicated. User Action: None.
NAM
invalid NAM block or NAM block not accessible Facility: RMS, VMS Record Management Services Explanation: The VMS RMS NAM block is not in the correct format, or it is not in an area of memory that can be written by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly and that the NAM block was not modified during execution of the program.
NAMETOOBIG
user name too long Facility: AUTHORIZE, Authorize Utility Explanation: The user name you specified is longer than 12 characters. User Action: Enter a user name no longer than 12 characters.
NAMETOOLONG
link name is too long Facility: LAT, LAT Facility Explanation: You attempted to create or set a link with a name longer than 16 characters. User Action: Use link names of 16 or fewer characters.
NAOFIL
unable to open SYSUAF.DAF Facility: AUTHORIZE, Authorize Utility Explanation: The system user authorization file cannot be opened. This error can occur if the file is not located in the current default directory, or if you do not have sufficient privilege to access the file. This message should be accompanied by a VMS RMS message specifying the reason why the file cannot be opened. User Action: If the file could not be found, set your default directory to SYS$SYSTEM and then reenter your command. If you do not have sufficient privilege to access the file, there is nothing you can do unless your system manager can grant you the necessary privilege.
NAONAF
unable to open NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The network user authorization file (NETPROXY.DAT) could not be opened. This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. Possible reasons are insufficient privilege, file protection violation, or location of the file in the wrong directory. User Action: If you do not have sufficient privilege to open NETPROXY.DAT, there is nothing you can do except to ask a privileged user, such as your system manager, to access the file for you. If you do have sufficient privilege, make sure the file is located in the proper directory and is not protected against read or write access. Then reenter your command.
NARG
wrong number of arguments Facility: CONVERT, Convert Utility Explanation: You specified an incorrect number of arguments in a call to CONV$PASS_FILES, CONV$PASS_OPTIONS, or CONV$CONVERT. User Action: Refer to the VMS System Services Reference Manual for details about calling these routines.
NCBFAIL
undefined object on local node Facility: MOM, Maintenance Operation Module Explanation: An error has been detected in a Network Control Block. This is a program logic error and should be reported. User Action: Submit a Software Performance Report (SPR).
NCS
no corresponding SAVE for attempted RESTORE Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You have specified more .RESTORE commands than .SAVE commands. User Action: Specify the correct number of .RESTORE commands.
NEEDBOTH
no authorization file - need both a password and a group number Facility: CAF, Cluster Authorization File Service Explanation: You specified an invalid group number with the CONFIGURATION SET CLUSTER_AUTHORIZATION command. User Action: Reenter the command with a numeric group number between 1 and 65535.
NEEDFILENAME
type file name or just RETURN to delete buffer 'buffer-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You modified a writable buffer, but there is no file name associated with the buffer. User Action: Enter a file name if you want the contents of the buffer written to a file. Otherwise, press the Return key.
NEEDTERMS
you must specify some word terminators for FILL Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure FILL requires you to supply characters that determine where to break the lines being filled. User Action: Specify a string that contains at least one word terminator that you want the built-in procedure FILL to use.
NEEDTOASSIGN
built-in call must return a value Facility: VAXTPU, VAX Text Processing Utility Explanation: This built-in procedure may only be used in situations where its return value is used. The built-in procedure must be on the right-hand side of an assignment statement. User Action: You must use this built-in procedure as part of an assignment statement or as part of an expression.
NEF
not positioned to EOF on $PUT (sequential organization only) Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $PUT request is attempted for a sequential file that is not currently positioned at the end of the file. User Action: Verify that the call to the VMS RMS service is programmed correctly. Modify your program, if necessary, to detect and respond to the condition.
NEGATED
entity explicitly negated in command string Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified qualifier or keyword is present in its negated form (with NO). User Action: None.
NEGSHBREF
shared memory control block negative refcnt Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NEGSTRLEN
negative string length Facility: STR, String Manipulation Facility Explanation: Successful completion except that a length parameter to a string routine had a negative value. Lengths of strings must always be positive or zero; zero is used. User Action: Verify that all parameters containing string lengths do not contain negative numbers.
NEGTIM
a negative time is computed Facility: LIB, Library Facility Explanation: The computed time is less than the system zero date (17-NOV-1858). User Action: Examine each argument and the order which they are passed. Debug and correct the problem.
NESTERROR
nesting level exceeded Facility: VAXTPU, VAX Text Processing Utility Explanation: A nested CASE, LOOP, or IF statement exceeds the maximum nesting level of 20. User Action: Do not nest CASE, LOOP, or IF statements more than 20 levels deep.
NESTLEVEL
nesting level exceeded in macro 'macro-name' file 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The specified macro exceeded the nesting limit of 63. User Action: Change the macro before inserting it into the library.
NET
network operation failed at remote node; DAP code = 'xxxxxxxx' Facility: RMS, VMS Record Management Services Explanation: The file system of the target node could not perform the requested operation, and VMS RMS is unable to map the Data Access Protocol status code into a more specific VMS RMS completion code. The status value (STV) field of the FAB or RAB contains the DAP status code. User Action: Consult the appropriate DECnet manual for the remote node to interpret the status code and take corrective action.
NETASN
failed to declare name to network Facility: CNF, NI Configurator Explanation: An error occurred when NICONFIG attempted to declare itself to the network as a known object. User Action: See the accompanying message to determine the appropriate action.
NETASN
unable to assign a channel to NET Facility: EVL, Event Logger Explanation: An EVL $ASSIGN system service failed to assign a channel to the network. User Action: Refer to the VMS System Services Reference Manual for the meaning of this system service error, and correct the problem.
NETDAS
error deassigning a channel to the device NET Facility: EVL, Event Logger Explanation: An error occurred when EVL attempted to deassign a channel to break a link with the event receiver. User Action: Refer to the VMS System Services Reference Manual for the meaning of this system service error, and correct the problem.
NETDIS
disconnect on remote terminal DECnet link Facility: REM, Set Host Facility Explanation: The remote terminal facility received a disconnect status from DECnet. User Action: Try again.
NETERR
DECnet channel error on remote terminal link Facility: REM, Set Host Facility Explanation: A DECnet-VAX error on the remote terminal link caused the connection to be broken. This message may be accompanied by another message identifying the specific reason why the connection is broken. One possible cause is an incorrect local node name or address. For instance, the address of the local node (the node from which you entered your command) may conflict with an address for another node in the remote node's network configuration database. User Action: Use the Network Control Program (NCP) to examine the status of the remote node's database. The NCP command SHOW displays network data, and the NCP command LOOP NODE tests data transmission to a specified node.
NETFAIL
network operation failed at remote node Facility: RMS, VMS Record Management Services Explanation: The requested operation could not be performed by the file system at the remote node. The status value (STV) field contains a FAL status code that describes the failure in the context of the remote system. User Action: Take corrective action based on the accompanying message.
NETIO
network communication error Facility: NCP, Network Control Program Explanation: A network error occurred. Information accompanying this message explains the reason for this error. User Action: The action required depends upon the accompanying error message. When you enter the next command, NCP automatically creates a new link to NML.
NETIOERR
network I/O error Facility: MAIL, Mail Utility Explanation: An I/O error occurred while transmitting a MAIL message with DECnet-VAX. User Action: Take corrective action based on the accompanying message.
NETLSTMSG
listing file NETPROXY.LIS complete Facility: AUTHORIZE, Authorize Utility Explanation: The contents of the network user authorization file (NETPROXY.DAT) have been written to the listing file named NETPROXY.LIS. User Action: None.
NETMBX
link mailbox code Facility: REM, Set Host Facility Explanation: A remote terminal network link is broken for unexpected reasons. User Action: Refer to DECnet-VAX documentation for more information.
NETMBX
NICONFIG requires NETMBX privilege Facility: CNF, NI Configurator Explanation: NICONFIG must run with NETMBX privilege. User Action: Install NICONFIG with NETMBX privilege or run it from an account with NETMBX privilege.
NETNOBUF
NETACP - buffer allocation failure Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NETNOSTATE
NETACP - no state transition Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NETRCVPKT
NETACP - no receive I/O packet Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NETSYSSRV
NETACP - unexpected system service failure Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NETTRANCNT
NETACP - transaction count zero Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NETWORK
network Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "NETWORK" class operations. User Action: None.
NEWCOMPFIL
current component file Facility: SYSMAN, Cluster System Management Utility Explanation: The name of the current startup component database has been changed to the file specification named. This is output when the /LOG qualifier is specified with the STARTUP command SET DATABASE. User Action: Verify that the named database is correct.
NEW_FILE
now analyzing file 'filename' Facility: AUDSRV, Audit Server Explanation: A new security audit journal file has been accessed by the Audit Analysis Utility. This informational message is primarily useful if you have used a wildcard file specification to analyze multiple security audit journal files. User Action: None.
NEWFILES
'nnn' files created Facility: Shared by several facilities Explanation: This informational message displays the number of new files successfully created. User Action: None.
NEWIGNORE
security auditing resources ignored; new messages ignored Facility: AUDSRV, Audit Server Explanation: The audit server internal message buffer has been exhausted. As a result, the audit server has chosen to ignore a security alarm in an attempt to preserve the events which led up to this point. User Action: None. This event results from the server FINAL_ACTION setting of IGNORE_NEW.
NEWLINK
created link 'link-name' Facility: LAT, LAT Facility Explanation: The specified link has been created by LATCP. User Action: None.
NEWLOGNAME
created logical name 'logical-name' in table 'table-name' Facility: LAT, LAT Facility Explanation: The specified logical name has been created by LATCP in the specified table. User Action: None.
NEWPAGE
attempted to write into new page Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont format routine indicating the attempt to write into a new page. User Action: None.
NEWPORT
created port 'port-name' Facility: LAT, LAT Facility Explanation: The specified port has been created by LATCP. User Action: None.
NEWQUEUE
new system job queue file 'filespec' created Facility: JBC, Job Controller Explanation: This informational message indicates that the system created a new system job queue file. Note, however, that any jobs currently entered in the old queue file have been lost. They have not been transferred to the newly created queue file. User Action: None.
NEWSAVSET
now beginning save set 'save set' Facility: BACKUP, Backup Utility Explanation: This informational message indicates the beginning of a new save set during a wildcard list or restore operation. User Action: None.
NEWSERVERDB
new audit server database created Facility: AUDSRV, Audit Server Explanation: A new permanent audit server database (SYS$MANAGER:AUDIT_SERVER.DAT) has been created by the audit server process. This is an informational message. User Action: None.
NEWSERVICE
created service 'service-name' Facility: LAT, LAT Facility Explanation: The specified service has been created by LATCP. User Action: None.
NEWTAPE
place volume 'volume' on device 'device' Facility: BACKUP, Backup Utility Explanation: The volume should be placed on the specified device. User Action: If the /NOASSIST qualifier is entered, the user should place the volume in the drive. Otherwise, the user should wait for the operator to do so.
NEXNOTUBA
nexus is not a UNIBUS adapter Facility: SYSGEN, System Generation Utility Explanation: This message is returned from SHOW/UNIBUS when an adapter other than a UNIBUS adapter is specified. User Action: Reenter the command with a valid UNIBUS adapter.
NEXTVOL
volume 'volume' mounted - operation continues Facility: BACKUP, Backup Utility Explanation: This informational message indicates that the next volume required for the BACKUP operation has been mounted. User Action: None.
NIA
negative indent attempted Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to indent text to the left of the left margin limit of zero. User Action: Correct the indent or left margin setting.
NIC
another 'n' negative indents detected and accumulated. Now being reported. Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A specific number of negative indents (to the left of .LM0) are detected and reported. These errors are triggered by DSR commands .CHAPTER or .APPENDIX, or by the end-of-file. The count of errors is cleared after each DSR command .CHAPTER and .APPENDIX, or after the end-of-file. User Action: Correct the indent or left margin setting.
NMF
no more files found Facility: RMS, VMS Record Management Services Explanation: The directory or volume set does not contain any more files that meet the file specification (wildcard operation). This status code is returned on a VMS RMS $SEARCH or $REMOVE operation. User Action: Modify the source program, if necessary, to detect and respond to the condition.
NMLRSP
listener response - 'text' Facility: NCP, Network Control Program Explanation: The previous message line shows the format of response messages from the network management listener (NML). NML receives network management commands (from the Network Control Program, for instance) and performs local network management functions as well as control and information functions that are requested by remote nodes. An NML response message may be as many as three display lines. The first line of an NML message contains the reason for the error (this will be shown in the 'text' part of the line). The second line contains an entity code (if there is a code present in the response). The third line contains additional error text (if there is text in the response). User Action: Take corrective action based on the first line of the message. No definition Facility: EDT, EDT Editor Explanation: You have requested a SHOW KEY definition for an undefined key. User Action: Ensure that you specify a defined key when you request a SHOW KEY definition. No help available for that key Facility: EDT, EDT Editor Explanation: There is no information in the current EDT HELP file on the use of the key you have pressed. User Action: If you have another HELP file available on your system that contains the information, use the SET HELP command to gain access to that HELP file. No more than 65,535 lines can be processed in a single command Facility: EDT, EDT Editor Explanation: You specified a range that exceeds 65535 lines. User Action: Reenter the command specifying a smaller range.
NO
no Facility: VAXTPU, VAX Text Processing Utility Explanation: This is a prototype negative response. User Action: None. No output file name Facility: EDT, EDT Editor Explanation: You have used the EDT command EXIT without having specified a file name, either in the EDT command EXIT or in the command line. User Action: Reenter the command specifying a file name or enter QUIT. No output file written Facility: EDT, EDT Editor Explanation: You attempted to put text into an output file, but EDT cannot handle the record format of that text. User Action: You must change the record format of the file, if possible, before editing it. No Path - Block During Virtual Circuit Close Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Submit a Software Performance Report (SPR) including the error logs and the crash dumps from the local and remote systems. No select range active Facility: EDT, EDT Editor Explanation: You did not create a select range prior to entering the EDT command APPEND or CUT. User Action: Create a select range (using the select key) before you enter the command. No such line Facility: EDT, EDT Editor Explanation: There are no original line numbers for the specified range. User Action: Ensure that a specified range has line numbers.
NOACCMAN
account manipulation on alternate roots not supported. Facility: VMSINSTAL, Install Procedures Explanation: The product being installed to an alternate system root cannot update the user authorization file (SYSUAF). User Action: Do not attempt to update the user authorization file from an alternate system root.
NOACCPTMSG
remote node cannot accept this message format Facility: MAIL, Mail Utility Explanation: MAIL cannot send a message of this format to the specified remote node. User Action: Convert the message to text and send the message to the remote recipient again.
NOACESS
cannot access image section Facility: PATCH, Patch Utility Explanation: You specified an address contained in an image section that is not within this image file. User Action: Retry specifying an address contained in an image file.
NOACNT
operation requires ACNT privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires ACNT privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOACP
no LATACP to process request Facility: LAT, LAT Facility Explanation: You requested information from the local LAT software but LATACP is not currently running on the local node. User Action: Check to see whether LAT startup has executed correctly or if LAT shutdown has been performed on the local node.
NOACPCHAN
failure to assign ACP channel Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOACPDEV
device named by /PROCESSOR:SAME has no ACP Facility: MOUNT, Mount Utility Explanation: The /PROCESSOR qualifier requested that the ACP currently processing a specified device be used for another device, but the first device does not have an ACP. User Action: Reenter the command; select a different option for the /PROCESSOR qualifier.
NOACPMAIL
failure to create ACP mailbox Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOADAPTER
no adapter (nexus) number specified Facility: SYSGEN, System Generation Utility Explanation: The /ADAPTER qualifier must be specified in the SYSGEN command CONNECT. User Action: Reenter the command specifying the /ADAPTER qualifier.
NOALLOC
ignoring /ALLOCATION, not valid for output volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ignored an /ALLOCATION qualifier, which is not meaningful. User Action: Leave the allocation off; it is not needed.
NOALLSPOOL
operation requires ALLSPOOL privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires ALLSPOOL privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOALOCLASS
allocation class not allowed with shadowing phase II virtual unit name Facility: MOUNT, Mount Utility Explanation: An allocation class was specified in the name of the virtual unit. Allocation classes are not allowed in virtual unit names with volume shadowing phase II (VMS Volume Shadowing). User Action: Reenter the command without specifying an allocation class on the virtual unit. The virtual unit must be specified in the form DSA or DSAnnnn, where nnnn represents a unique number from 0 to 9999.
NOALTPRI
operation requires ALTPRI privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires ALTPRI privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOANGLE
unmatched angle brackets in expression Facility: PATCH, Patch Utility Explanation: You entered an expression that has an unequal number of right angle brackets to left angle brackets or the brackets are not correctly positioned. User Action: Make the number of right angle brackets equal to the number of left angle brackets and ensure that the brackets are in the correct position.
NOANSWER
no answer is detected on the phone line Facility: DTK, DECtalk Facility Explanation: The routine DTK$DIAL_PHONE was called to dial a phone number and no one answered the call. User Action: Try calling again later.
NOAQB
ACP queue header not found Facility: SYSTEM, VMS System Services Explanation: When an ACP started, it is unable to locate its queue header. This error is the result of running an ACP with the DCL command RUN. User Action: ACPs can be started only with the DCL command MOUNT. If this message results from a DCL command MOUNT, gather as much information as possible and submit a Software Performance Report (SPR).
NOAQBACP
no AQB for ACP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOARG
missing argument for option Facility: AUTHORIZE, Authorize Utility Explanation: You specified a qualifier without a required argument. User Action: Reenter your command and include the required argument.
NO_ARGS
missing arguments for substitution Facility: SMG, Screen Management Facility Explanation: You requested a capability that requires user arguments such as row and column numbers. You failed to provide those arguments. User Action: Check the number of arguments required by this capability and correct your call to SMG$GET_TERM_DATA.
NOASSIGNMENT
expression without assignment Facility: VAXTPU, VAX Text Processing Utility Explanation: You used an expression without a := to assign it to a variable. User Action: Add the appropriate assignment to the statement.
NOAUTOCNF
autoconfigure all is inhibited Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN parameter NOAUTOCONFG is set to one. User Action: Set NOAUTOCONFG to zero and reenter the command.
NOAUTOSTART
node does not have the autostart feature enabled Facility: JBC, Job Controller Explanation: You entered a DISABLE AUTOSTART [/QUEUES] command for a node on which the autostart feature is not currently enabled. User Action: None.
NOAVAIL
field 'field-name' not available in this report Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The field name entered does not apply to the currently selected report and therefore cannot be added to the Report (SPR). The name is, however, valid in a different Report (SPR). User Action: Select a different Report (SPR).
NOBACKUP
'string' data not copied, file marked NOBACKUP Facility: BACKUP, Backup Utility Explanation: A save operation is performed on a file marked NOBACKUP. Therefore, the file header only is saved, no data is transferred to the save set. User Action: Set file so that it can be backed up with SET FILE /BACKUP command or add the /IGNORE=NOBACKUP qualifier to the BACKUP command line.
NOBADDATA
bad block data not found on volume Facility: INIT, INITIALIZE Command Explanation: No bad block information is recorded in the Software or Manufacturer's Bad Block areas. You have a good disk. User Action: None.
NOBADDATA
bad data block not found on 'device-name' Facility: INIT, INITIALIZE Command and BACKUP, Backup Utility Explanation: This is a warning message generated by either the DCL command INITIALIZE or the Backup Utility; software bad block data is not present on the volume. The volume has been initialized with no bad blocks. User Action: Execute the Bad Block Locator Utility before using the volume.
NOBADINFO
no bad block information available for 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: A device that is not a last track device does not contain a bad block file. The utility will create a new SDBSF in nonlast track format. User Action: None.
NOBITMAP
no valid storage bit map found on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to search for the storage bit map file, [000000]BITMAP.SYS;1, on the specified volume. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
NOBRANCH
instruction requires branch-type operand Facility: PATCH, Patch Utility Explanation: You attempted to enter a branch-type instruction with an invalid operand for a destination field. For example, PATCH does not accept the following command: DEPOSIT/INSTRUCTION GO= 'BNEQ R0'. User Action: Reenter the command using a valid branch operand in the destination field.
NOBREAKPOINT
no breakpoint is active Facility: VAXTPU, VAX Text Processing Utility Explanation: The attempted call is valid only after a breakpoint. User Action: Only enter the call in response to a breakpoint.
NOBUFPCKT
required buffer packet not present Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOBUGCHK
CPU 'CPU-ID' failed to service bugcheck request Facility: SDA, System Dump Analyzer Explanation: The CPU identified by 'CPU-ID' did not save its state when the system failed. As a result, context information about this CPU is not available in the dump file. User Action: None.
NOBUGCHK
operation requires BUGCHK privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires BUGCHK privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service calls that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOBVPVCB
blocked volume virtual page not found in VCB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOBYPASS
operation requires BYPASS privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires BYPASS privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOCACHE
insufficient virtual memory to allocate a new cache Facility: VAXTPU, VAX Text Processing Utility Explanation: The system does not have enough memory available to allocate a new cache for your process. User Action: First, delete unneeded strings, ranges, markers, windows, and buffers, then reenter your command. If the error recurs, increase the value of the SYSGEN parameter VIRTUALPAGECNT. If the available memory is still insufficient for your editing environment, try to increase your account's page file quota. Finally, if the error persists, ask your system manager to increase available memory.
NOCALLS
no active call frames Facility: TRACE, Traceback Facility Explanation: There are no call frames on the stack for traceback to display. This informational message usually occurs when a user image issues a RET instruction that returns control to the command interpreter. User Action: None.
NOCALLUSER
could not find a routine for CALL_USER to invoke Facility: VAXTPU, VAX Text Processing Utility Explanation: You must specify a routine for this built-in procedure to invoke. User Action: Provide a routine for CALL_USER to use.
NOCARRIAGE
ignoring /CARRIAGE_CONTROL, not valid for output volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ignored a /CARRIAGE_CONTROL qualifier which could not be applied to the volume. User Action: Leave the qualifier off for that volume type.
NOCCAT
parameter concatenation not allowed - check use of plus (+) Facility: CLI, Command Language Interpreter (DCL) Explanation: A command that accepts either only a single-input value for a parameter or a list of input values separated by commas for a parameter containing multiple values separated by plus signs (+). User Action: Reenter the command with a single file specification. If necessary, enter the command once for each file.
NO_CHADIS
no change in virtual display Facility: SMG, Screen Management Facility Explanation: The requested number of columns to change is 0, so nothing in the virtual display is changed. User Action: None.
NOCHARREAD
no character was read by the READ_CHAR built-in Facility: VAXTPU, VAX Text Processing Utility Explanation: The READ_CHAR built-in procedure did not read a character due to the user pressing a keypad or function key. User Action: None.
NOCLASS
requested input file classes not found or are incompatible Facility: MONITOR, Monitor Utility Explanation: The MONITOR request has been terminated because none of the requested MONITOR classes were present in a valid form in the specified input recording file. This situation may result from having specified an incorrect input file. Also, this situation could result from an attempt to play back classes from a recording file generated by a newer version of MONITOR. User Action: Reenter the MONITOR request, specifying only classes that are contained in the input recording file. Specify the correct input file if it had been incorrectly specified. If the set of classes contained in the input file is unknown, request all classes; only those present in the input file will be used.
NOCLASSES
no classes specified Facility: MONITOR, Monitor Utility Explanation: A MONITOR request is executed with the Monitor Utility command, but no information is provided to identify which classes to monitor. User Action: Reenter the Monitor Utility command, specifying at least one class name parameter.
NOCLI
no CLI present to perform function Facility: LIB, Library Facility Explanation: The calling process did not have a CLI to perform the function or the CLI did not support the request type. User Action: Ensure that the calling process has a CLI and that the CLI supports the request type. (Note that an image run as a subprocess or detached process does not have a CLI.)
NOCLITABLE
image 'image-name' is not a CLI table Facility: CDU, Command Definition Utility Explanation: The input tables have an invalid format. Either an invalid file is entered or a valid file is entered but then became corrupted. User Action: Do not use this file again with the SET command.
NOCLUDEV
server not loaded, no cluster device Facility: STACONFIG, Standalone Configure Process Explanation: No port descriptor table was found on this node. Either there is no CI or NI adapter on this node, or the port drivers corresponding to either of the devices has not been loaded. User Action: Make sure the node you are loading the server on is configured so that it can participate in a VAXcluster. If it does not have either an Ethernet or a CI adapter, the MSCP server cannot be loaded (set MSCP_LOAD to a 0). If you have one of the above adapters, make sure the VAXCLUSTER parameter is set to a nonzero value. If the node participates in a Local Area VAXcluster, that NISCS_LOAD is set to 1.
NOCLUSTER
server not loaded, SCS not available Facility: STACONFIG, Standalone Configure Process Explanation: The SYSGEN parameters for this system request that the MSCP server be loaded, but none of the underlying SCS services are loaded. These SCS services are necessary for the operation of the MSCP server. User Action: Make sure that the VAXCLUSTER parameter is set to a nonzero value, or change the MSCP_LOAD parameter to 0, so the server is not loaded.
NOCMDMEM
no command memory has been allocated Facility: Shared by several facilities Explanation: If returned from a DR32 support routine call, either command memory is never allocated, or the DR32 transfer is complete and the memory has been deallocated. User Action: If the DR32 transfer has completed, this is an informational message. If command memory is never allocated, make sure the XF$SETUP support routine is called before trying to access command packets.
NOCMDPROC
error opening captive command procedure - access denied Facility: CLI, Command Language Interpreter (DCL) Explanation: When you attempted to log in, you were logged out because you have a captive account and DCL received an error during the login. For example, DCL could not find your LOGIN.COM file. You may also have incorrect protection on the system's SYLOGIN file (SYS$MANAGER:SYLOGIN.COM or /SYSTEM/EXEC logical). The system's SYLOGIN file must be protected with at least WORLD:E access to the file and the directory which contains it. User Action: See your system manager.
NOCMEXEC
operation requires CMEXEC privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires CMEXEC privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOCMK
operation requires CMKRNL privilege Facility: INSTALL, Install Utility Explanation: You must have CMKRNL privilege to perform the requested operation. User Action: Exit INSTALL and use SET/PROC/PRIV=CMKRNL.
NOCMKRNL
operation requires CMKRNL privilege Facility: SYSTEM, VMS System Services and JBC, Job Controller Explanation: A command or program requested a system function that required CMKRNL privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOCOMD
no command on line - reenter with alphabetic first character Facility: CLI, Command Language Interpreter (DCL) Explanation: A command begins with a nonalphabetic character. User Action: If you entered a symbol name, verify that the symbol is defined by using the DCL command SHOW SYMBOL, and reenter the command. If the error occurred in a command procedure, verify the syntax of the command lines and check for continued lines.
NOCOMMSTLEV
input files do not have a common file structure level Facility: MONITOR, Monitor Utility Explanation: A list of files is specified for the /INPUT qualifier, but the files had different MONITOR file structure levels, that is, they were created by different versions of the Monitor Utility. A multifile summary may be generated only when all the input files have the same file structure level. The file structure level is stored in the MONITOR file header record, and may be examined by using the DUMP utility. User Action: Reenter the MONITOR request specifying an input file list consisting of files that have the same file structure level.
NOCOMMUNICATION
unable to communicate with DNS server Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS clerk was unable to communicate with a clearinghouse. The error text includes VMS error information that may have caused the communication problem. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
NOCOMPLSTS
no component lists are defined
Facility: SYSTEM, VMS System Services
Explanation: No component lists were defined using calls to
SYS$LAVC_DEFINE_NET_PATH before calling SYS$LAVC_ENABLE_ANALYSIS.
As a result, no data is available to perform the local area
VAXcluster network failure analysis.
User Action: Perform the following steps to properly define the
network description before calling SYS$LAVC_ENABLE_ANALYSIS:
1. Call SYS$LAVC_DEFINE_NET_COMPONENT for each network component.
2. Describe each network path used by building a list from the
component identifications (IDs) returned by SYS$LAVC_DEFINE_
NET_COMPONENT.
3. Call SYS$LAVC_DEFINE_NET_PATH to define the network component
lists.
4. After all the network paths are defined, call SYS$LAVC_ENABLE_
ANALYSIS to enable the local area VAXcluster network failure
analysis.
NOCONNECT
unable to connect to remote node 'node-name' Facility: MONITOR, Monitor Utility Explanation: The network could not connect to a remote node. This error can occur if the specified node is unreachable when the CLUSTER class is requested. User Action: Determine whether the network is working properly on the remote node. When the node is accessible, reenter the MONITOR command.
NOCONSOLE
unknown CPU type number. Console volume cannot be remounted. Facility: VMSINSTAL, Install Procedures Explanation: While attempting to remount the console medium, VMSINSTAL could not determine your CPU type. User Action: Contact the Digital Services Group.
NOCONTIG
bootfile not contiguous Facility: VAXCLUSTER, VAXcluster Facility Explanation: The file SYSBOOT.EXE is noncontiguous on the system disk. The primitive bootstrap file system cannot read a noncontiguous file. User Action: Rebuild the system disk to obtain enough contiguous free space for SYSBOOT.
NOCONTIG
noncontiguous image file being written Facility: PATCH, Patch Utility Explanation: The output file is a noncontiguous image file. User Action: If you require a contiguous output file after you exit from PATCH, use the DCL command in the following format: COPY/CONTIGUOUS input-filespec output-filespec
NOCONVBOOT
not authorized to perform conversational bootstrap Facility: VAXCLUSTER, VAXcluster Facility Explanation: Conversational bootstrap operations are not authorized for the satellite node. User Action: Consult the cluster manager.
NOCOPBAD
cannot create .BAD file with wildcard names Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not create an RT-11 file with a file type of .BAD because the input or output file names contained a wildcard. User Action: Since the file type of .BAD is given special meaning by RT-11, you probably want to choose a different file type for your file.
NOCOPBADDEL
cannot delete existing .BAD file Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not copy an RT-11 file with a file type of .BAD because the same file already exists on the volume. User Action: Since the file type of .BAD is given special meaning by RT-11, you probably want to choose a different file type for your file.
NOCOPDUP
already copied file with same output name in this command Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not copy the listed file, because the current command had already copied a file with the same output name. User Action: Copy the file with another command, specifying an output name which does not conflict with other files.
NOCOPLOCK
cannot create files, volume 'volume' is write-locked Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not perform a COPY command because the output volume is write-locked. User Action: Remount the output volume with write access, then reenter the command.
NOCOPNODEL
file already exists and /NODELETE requested Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not perform a COPY command. The output file already existed and the /NODELETE qualifier is specified. User Action: This message means that the /NODELETE qualifier actually prevented a file from being deleted. It normally requires no response. If it is desired to delete the original file and perform the copy, then reenter the command without the /NODELETE qualifier.
NOCOPPROT
file with same name is protected against modification Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not perform a COPY command. The output file already existed and is protected from being deleted. User Action: If it is desired to perform the copy, use the RENAME /NOPROTECT command to remove the protection from the output file.
NOCOPSAMDEV
illegal wildcard copy to same device Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility refused to perform a copy operation, due to illegal use of wildcards or the /REPLACE qualifier. User Action: EXCHANGE will not perform a wildcard copy from a foreign volume back to the same foreign volume, since it can be difficult or impossible to prevent a loop with files being copied more than once. It also will not perform a /REPLACE copy of a file to itself, since that implies deleting the file before the copy.
NOCOPSYSDEL
cannot delete existing .SYS file without /SYSTEM Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility refused to copy a file with file type of .SYS because an existing file of the same name would have to be deleted. User Action: If you want to delete the old file and copy the new file, then reenter the copy command with the /SYSTEM qualifier.
NOCOPYBOOT
unable to copy boot information Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a problem while attempting a COPY /BOOT operation. User Action: This command will be followed by a second message giving the specific condition found. Take corrective action based on the contents of the second message.
NOCOPYBUF
cannot COPY a buffer to itself Facility: VAXTPU, VAX Text Processing Utility Explanation: You attempted to copy a buffer while you were working in the buffer. You cannot copy a buffer to itself; doing so would cause an infinite loop. User Action: Move to another buffer before starting the copy operation.
NOCPUS
requested cpu[s] are not active Facility: MONITOR, Monitor Utility Explanation: The CPUs specified with the /CPU qualifier are not active on the requested node. User Action: Correct the CPU specification and reenter the MONITOR command.
NOCSP
no SMI thread in remote Cluster Server Process
Facility: SMI, System Management Integrator/Server
Explanation: A remote SYSMAN command could not be delivered to the
SMISERVER process in the indicated node for one of the following
reasons:
o The remote system is running a version of VMS lower than
Version 5.0.
o The CLUSTER_SERVER process on the remote system stopped,
aborted, or is not yet started during system initialization.
User Action: Determine the reason for the failure and correct the
problem.
NOCURRENTBUF
no buffer has been selected as default Facility: VAXTPU, VAX Text Processing Utility Explanation: You tried to use a built-in procedure to modify the current buffer when you were not working in a buffer. This error occurs when no buffers have been created, because there is no buffer to serve as the default buffer. User Action: Establish a current buffer. To do this, either move to a buffer or associate a buffer with a window and map the window to the screen.
NOCURTID
no process default transaction currently defined Facility: SYSTEM, VMS System Services Explanation: The user program attempted to terminate a default transaction when none was defined. User Action: Correct the program so that it specifies a transaction identifier (TID).
NOD
error in node name Facility: RMS, VMS Record Management Services Explanation: The node name portion of a file specification is not in the correct syntax. User Action: Check the syntax of the node name specification and retry the operation. Verify that the call to the VMS RMS service is coded correctly.
NODECNTRSONLY
only counter information is available for this node Facility: LAT, LAT Facility Explanation: The specified node offers no services known to the local node. However, there is a connection from the node and counter information is maintained. User Action: None.
NODECODE
cannot decode instruction Facility: PATCH, Patch Utility Explanation: The Patch Utility encountered an undefined opcode or illegal addressing mode while attempting to decode the instruction. This can be caused by specifying an address that is in the middle of an instruction or is in a data area. User Action: Correct the location and reenter.
NODEDISABLED
node is not currently enabled for file Facility: SMI, System Management Integrator/Server Explanation: A STARTUP DISABLE action tried to disable a component file on a node that the component file is not enabled on. User Action: None.
NODEENABLED
node is already enabled for file Facility: SMI, System Management Integrator/Server Explanation: A STARTUP ENABLE action tried to enable a component file on a node that the component file is already enabled on. User Action: None.
NODEFINITION
key 'key-name' currently has no definition Facility: VAXTPU, VAX Text Processing Utility Explanation: The key you pressed is not defined. User Action: Use the built-in procedure DEFINE_KEY if you want to define a function for the key.
NODEFPWD
Warning: DEFAULT password change has no effect on added records Facility: AUTHORIZE, Authorize Utility Explanation: The DEFAULT password for added records is always USER, regardless of the DEFAULT record specified. User Action: None.
NODEINIERR
error during node initialization Facility: MONITOR, Monitor Utility Explanation: An error occurred during the initialization of a node. This error can occur if an attempted connection to a remote node fails. User Action: Determine whether the network is working properly on the remote node. When the node can be successfully initialized, reenter the MONITOR command.
NODELLOCK
file 'filename' not deleted, volume is write-locked Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not perform a DELETE command because the output volume is write-locked. User Action: Remount the output volume with write access, then reenter the command.
NODENOTAVAIL
requested nodes are not available Facility: MONITOR, Monitor Utility Explanation: The remote nodes specified in a MONITOR request are not currently accessible over the network. Therefore, they are not available for data collection from the local node. User Action: Determine why the remote nodes are not available. Reenter the MONITOR command when they do become accessible from the local node.
NODENOTCLU
node not currently in cluster Facility: SYSMAN, Cluster System Management Utility Explanation: During a STARTUP ENABLE action, a node that is not currently in the cluster was specified. User Action: Verify that node name is correct. If it is incorrect, reenter the command.
NODENOTMEM
node 'node-name' is not a member of this cluster Facility: MONITOR, Monitor Utility Explanation: The requested node is not a member of the VAXcluster specified in the request. MONITOR can only collect data from nodes within a VAXcluster. User Action: Select nodes that are members of the requested VAXcluster and reenter your command.
NODENOTPRES
one or more nodes requested do not exist in input file Facility: MONITOR, Monitor Utility Explanation: At least one of the nodes requested during a playback command does not exist in the input file. User Action: Enter the command without a node name specification to determine which nodes are contained within the file. Then select the correct nodes and reenter your command.
NODERR
error returned from node "nnnnnn" Facility: SYSMAN, Cluster System Management Utility Explanation: A command returned an error on node "nnnnnn". The error message follows. Execution will be attempted on the next node in the environment. User Action: Take action according to the accompanying error message.
NODESHUT
node shutdown in progress Facility: LAT, LAT Facility Explanation: A LAT connection attempt on an application port or dedicated port was rejected because the node state is Shut. User Action: Wait until the node is in the On state to make new connections. Refer to the VMS LAT Control Program (LATCP) Manual for a full description of the node states.
NODESTQUE
no such destination queue Facility: SYSTEM, VMS System Services Explanation: In a request to the symbiont manager, the specified destination queue does not exist. User Action: Reenter the command, specifying a valid destination queue.
NODETACH
operation requires DETACH privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires DETACH privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NODEVADAP
no devices on adapter 'n' Facility: SYSGEN, System Generation Utility Explanation: A SHOW/CONFIGURATION operation is tried on an adapter that has no devices. User Action: Reenter the command specifying an adapter that has devices.
NODEVAVL
device 'device-name' is not available for mounting. ['optional comment'] Facility: MOUNT, Mount Utility Explanation: Someone else has allocated the device you requested. User Action: Abort the MOUNT and retry specifying another device.
NODEVAVL
no device available Facility: SYSTEM, VMS System Services Explanation: You tried to allocate an unavailable device. User Action: Wait until a device is available and retry allocation.
NODEVICE
missing or incorrect device name in 'command-line' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not find device name in a command line. User Action: Check the command for a misspelling or other error, and reenter the command with a correct device name.
NODEVINFO
unable to retrieve device information on 'disk-name' Facility: QMAN, Queue Manager Explanation: The queue manager received a bad return value from a call to the $GETDVI system service. The accompanying message provides information about why the operation failed. User Action: Take corrective action based on the accompanying message.
NODEXIT
lost connection to node 'node-name'. Node removed! Facility: MONITOR, Monitor Utility Explanation: The connection to a remote node is broken. This error can occur if the remote node shuts down. User Action: Determine why the remote node is removed from the network. When the remote node is accessible again, reenter the MONITOR command.
NODIAGNOSE
operation requires DIAGNOSE privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires DIAGNOSE privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NODIATONE
no dial tone is detected on the phone line Facility: DTK, DECtalk Facility Explanation: The routine DTK$DIAL_PHONE is called to dial a phone number and no dial tone is detected on the phone line. User Action: Correct the telephone line problem and call again.
NODISKQUOTA
no disk quota entry for this UIC Facility: SYSTEM, VMS System Services Explanation: The specified quota file entry does not exist. User Action: Check the UIC given. Either add a quota file entry for it or use another UIC.
NODISKSPACE
disk space not available for queue manager to continue Facility: QMAN, Queue Manager Explanation: The queue manager cannot process any queuing requests because of a lack of disk space. The accompanying FREEDISK message provides details. User Action: Purge and delete files to make more space on the disk.
NODSTQUE
no such destination queue Facility: JBC, Job Controller Explanation: The specified destination queue does not exist. User Action: None.
NODTOOBIG
node name too long Facility: AUTHORIZE, Authorize Utility Explanation: VMS node names cannot exceed 6 characters. A node name may consist of 1 to 6 alphanumeric characters; at least one character must be alphabetic. User Action: Check the node name and reenter your command with the correct name.
NODUNAV
node 'node-name' not currently reachable Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a specified service and node failed because the specified node is not currently reachable. User Action: Retry the connection or determine why the remote node is not currently reachable.
NODUPEXC
equal-key routine and no duplicates options cannot both be specified Facility: SORT, Sort/Merge Utility Explanation: You specified both an equal-key routine and the SOR$M_NODUPS option when only one or the other option is allowed. User Action: Specify either the equal-key routine or the no duplicates option.
NOELEM
no element found Facility: STR, String Manipulation Facility Explanation: The input string passed to STR$ELEMENT does not contain at least the number of delimiters specified in the ELEMENT_NO item code. User Action: Examine SRC_DESC and ELEMENT_NO and make corrections.
NOENCODE
cannot encode instruction 'instr' Facility: PATCH, Patch Utility Explanation: The instruction contained an illegal opcode or operand. The branch destination may not be reachable from the location for which it is destined. User Action: Retry specifying a legal opcode or operand.
NOENCODE
cannot encode instruction 'n' Facility: PATCH, Patch Utility Explanation: The instruction cannot be encoded. Possible causes include: invalid addressing modes, invalid syntax, not enough operands, or too many operands. User Action: Determine the cause of the problem.
NOENDOFLINE
returning a range of text with no end of line Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU is returning a range of text without an end- of-line indicator. User Action: None.
NOENTRYSYM
unable to set $ENTRY symbol to current entry number Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command Explanation: The print or submit command failed to set a global symbol $ENTRY. However, the actual print or submit request did succeed. User Action: Take corrective action based on the accompanying messages.
NOEOBSTR
cannot return a string at end of buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedures CURRENT_LINE and CURRENT_ CHARACTER return the null string if you are positioned at the end of the buffer (EOB). This warning distinguishes this case from that of end of line. User Action: Move back from the end of the buffer.
NOEOM
module 'module-name' does not contain end of module records Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
NOEOM
module 'module-name' is not terminated with EOM record in 'library- name' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. The module you attempted to insert into the library does not contain a legal EOM record. User Action: Recompile the object module.
NOEOM
no end of module record found in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A module did not contain an end-of-module record. User Action: Submit a Software Performance Report (SPR). Include the language compiler in the Report (SPR).
NOEPM
undefined entry mask of symbol 'symbol-name' referenced in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An entry mask of an undefined symbol is referenced with the MACRO .MASK directive. User Action: Either define the entry point or delete the reference to it.
NOEXQUOTA
operation requires EXQUOTA privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires EXQUOTA privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOFILE
no file found Facility: SEARCH, SEARCH Command Explanation: The DCL command SEARCH is unable to open any files in the input file list. Therefore, no files were searched. User Action: If files were incorrectly specified, reenter the command with correct file specifications.
NOFILE
[new] file 'filename' does not exist. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL cannot find an existing (or new) file with the given name. User Action: If you can determine and correct the problem, reinstall the product. Otherwise, contact the Digital Services Group.
NOFILEACCESS
unable to access file 'filename' Facility: VAXTPU, VAX Text Processing Utility Explanation: The file you tried to open could not be accessed. The accompanying VMS RMS error message explains why. User Action: Follow the recovery procedure for the specified VMS RMS message.
NOFILEID
no file identification is specified Facility: PSM, Print Symbiont Explanation: This status is returned indicating no file identification number is specified with this request. This error usually indicates a problem in the creation of a batch log file. User Action: Correct the problem in the batch command file and resubmit the job.
NOFILEROUTINE
no routine specified to perform FILE I/O Facility: VAXTPU, VAX Text Processing Utility Explanation: This message is returned from the callable interface by TPU$INITIALIZE. It indicates that a valid I/O routine is not specified. User Action: Specify an I/O routine.
NOFILES
no files selected from 'filespec' Facility: BACKUP, Backup Utility Explanation: No files matched the input file selection criteria. User Action: Reevaluate the operation to ensure that the correct results are obtained.
NOFILNAM
no file specification found Facility: LBR, Librarian Subroutine Package Explanation: In the LBR$OPEN routine, the FNS argument is invalid or not provided or the NAM block is not filled in. User Action: Correct the problem before calling the routine.
NOFILPURG
no files purged Facility: Shared by several facilities Explanation: No files were purged. User Action: None. The directory is already purged.
NOFORCMD
account restricted - foreign commands not valid Facility: CLI, Command Language Interpreter (DCL) Explanation: Foreign commands have been disabled for this account. (See the VMS DCL Concepts Manual for an explanation of foreign commands.) User Action: This account requires that all images are run by verbs defined in the CLI table (these are called DCLTABLES) specified for this account.
NOFORMLARG
no formal argument for .IRP/.IRPC Facility: MACRO, VAX MACRO Assembler Explanation: There were no formal arguments in an .IRP or .IRPC directive. User Action: Correct the syntax of the .IRP or .IRPC directive.
NOFREE
no free storage available Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report (SPR).
NOGBL
some or all global symbols not accessible Facility: PATCH, Patch Utility Explanation: When you initialized PATCH, either no global symbol information is available to PATCH or the symbol table is not large enough to incorporate all the global symbol information. User Action: To ensure that global symbol information is passed to the PATCH utility, reassemble or recompile and link your program including the Debugger or Traceback Facility.
NOGBLSEC
no global sections created for 'filespec' Facility: INSTALL, Install Utility Explanation: When creating a known file entry for a shareable image, INSTALL is not able to create global sections for that image. The image is not shareable.
NOGBLSELDATA
no global selection data Facility: VAXTPU, VAX Text Processing Utility Explanation: There is no data in the DECwindows global selection region. User Action: Select data before attempting to paste the global selection into VAXTPU.
NOGBLSELOWNER
there is no global selection owner Facility: VAXTPU, VAX Text Processing Utility Explanation: There is no global selection owner. User Action: Make sure that an application owns the global selection before requesting information about it.
NOGROUP
operation requires GROUP privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires GROUP privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOGRPNAM
operation requires GRPNAM privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires GRPNAM privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOGRPWILD
wildcard group numbers not allowed Facility: AUTHORIZE, Authorize Utility Explanation: Wildcard characters are not allowed in the UIC group number field for the command you entered. User Action: Reenter your command with a specific UIC group number instead of a wildcard character.
NOGSDREF
no GSD reference to shareable image symbol 'symbol' found in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A reference to a symbol in a shareable image is found in Pass 2 of the linking operation; yet, there is not a GSD reference to the symbol found in Pass 1. User Action: This is a compiler error. Submit a Software Performance Report (SPR). Include the appropriate compiler in the Report (SPR).
NOHANDLER
no condition handler found Facility: SYSTEM, VMS System Services Explanation: A request to delete an exit handler returned a warning code indicating that the specified handler does not exist. User Action: Check for a programming error.
NOHDJMT
no Head-JMT in JMT list (journaling) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOHDRRES
compatibility mode image, 'filespec', cannot be header resident Facility: INSTALL, Install Utility Explanation: The /HEADER qualifier is ignored. Resident headers are not used with compatibility mode images. User Action: None. The known file entry is successfully created.
NOHIDDEN
cannot modify hidden ACEs Facility: SET, SET Facility Explanation: The ACE currently being added or replaced has the HIDDEN option set. User Action: Remove the HIDDEN option before attempting to add the ACE.
NOHISTORY
library has no update history Facility: LBR, Librarian Subroutine Package Explanation: This library is created with the maximum number of history records equal to zero. User Action: None.
NOHLPLIBS
no default help libraries can be opened Facility: LBR, Librarian Subroutine Package Explanation: You called LBR$OUTPUT_HELP without passing the name of a help library, and you have no default libraries defined. User Action: Either pass in the name of the library or define HLP$LIBRARY to be a library name.
NOHLPTXT
help text not found Facility: LBR, Librarian Subroutine Package Explanation: There is no help text associated with the specified key path. User Action: Check that the help module is properly formatted.
NOHLPTXT
no level 1 help text found in 'input filespec' Facility: LIBRAR, LIBRARY Command Explanation: The specified input file does not contain a properly formatted help file. User Action: Reformat the help file before reentering the command line.
NOHOME
volume does not contain a valid home block Facility: SET, SET Facility Explanation: You attempted to perform a SET VOLUME on a disk that is not Files-11. User Action: None. You cannot perform a SET VOLUME on a disk that is not Files-11.
NOHOMEBLK
Files-11 home block not found on volume Facility: SYSTEM, VMS System Services Explanation: Either the volume is not a Files-11 volume or it is completely unreadable. User Action: Verify that the correct volume is mounted. Mount the volume as foreign.
NOHOMEBLK
no valid home block found on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to search for the Files-11 home block on the specified volume. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
NOIDBAVAIL
unable to allocate an IDB Facility: LAT, LAT Facility Explanation: LATCP cannot allocate enough virtual memory for an internal data structure needed to execute a command. An accompanying message explains why the virtual memory cannot be allocated. User Action: Correct the situation based on information in the accompanying message.
NOIDNAM
no ID name is specified Facility: AUTHORIZE, Authorize Utility Explanation: The command you entered requires that you include an identifier name. User Action: Check the VMS Authorize Utility Manual for the syntax rules regarding identifier names for the command you want to use. Then reenter the command including an identifier name.
NOIMGFIL
image file not created Facility: LINK, Linker Utility Explanation: This secondary message is issued when the linker encounters an error that prevents the generation of an image file. User Action: None.
NOINDEX
no index information in file 'filename' Facility: DSR, DIGITAL Standard Runoff Explanation: The indicated file does not contain any index entries. User Action: Check the corresponding input file to be sure there are index entries.
NOINDEXF
no valid index file header found on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to search for the index file, [000000]INDEXF.SYS;1, on the specified volume. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
NOINFO
no information in database Facility: NCP, Network Control Program Explanation: An NCP command (usually a SET command) was executed when there was no data to act upon in the database. This error commonly occurs during system startup when a SET KNOWN component ALL command is executed and there is no data to be copied into the volatile database from the permanent database. If the error occurs during system operation, a command has attempted to manipulate data that does not exist; for example, a command specifies a nonexistent component. User Action: Ignore this error if it occurs during system startup. If you receive this error during system operation, reissue the command specifying an existing system component.
NOINIT
PPL$INITIALIZE is not called Facility: PPL, Parallel Processing Facility Explanation: PPL$INITIALIZE must be called before this routine. User Action: Recode your program to ensure that calls are in the correct order. PPL$INITIALIZE is performed automatically for most calls, but not for those calls that require the prior creation of an element.
NOINPFILES
no usable input files Facility: MONITOR, Monitor Utility Explanation: A multifile summary is requested but none of the files specified in the /INPUT list could be used. User Action: Examine the IGNFIL error messages preceding this message. Each one identifies a file which is ignored, and provides an accompanying message explaining why the file could not be used. Reenter the MONITOR request specifying at least one input file which can be used. A typical situation where input files are ignored is one where the /BEGINNING and/or /ENDING qualifiers are specified, and the ignored files do not contain data in the range of the requested time.
NOINPTAB
new tables file cannot be written unless input tables supplied Facility: CDU, Command Definition Utility Explanation: You tried to write empty tables to your process. Either you did not provide input tables or you specified the /TABLES qualifier in the command string and there were no CLD files. User Action: Include the name of the input tables in the command string. Or if there are no CLD files, do not specify the /TABLES qualifier in the command string.
NOINSTRAN
cannot translate instruction Facility: SDA, System Dump Analyzer Explanation: SDA cannot translate the specified instruction into VAX MACRO instruction format. User Action: None.
NOINTABLE
an output table image must be created using an input table Facility: CDU, Command Definition Utility Explanation: You tried to write empty tables to your process. Either you did not provide input tables or you specified the /TABLES qualifier in the command string and there were no CLD files. User Action: Include the name of the input tables in the command string. Or, if there are no CLD files, do not specify the /TABLES qualifier in the command string.
NOIOCHAN
cannot piggyback I/O channel with PUTMSG Facility: TRACE, Traceback Facility Explanation: This message is associated with a traceback internal consistency check. User Action: Submit a Software Performance Report (SPR).
NOIOCHAN
no I/O channel available Facility: SYSTEM, VMS System Services Explanation: The process exceeds the number of I/O channels that can be assigned at one time. User Action: Deassign another channel, or close a file and retry the operation. Check for a program error that fails to deassign channels or close files. Also check the SYSGEN parameter CHANNELCNT to see if it is high enough.
NOITMLST
unable to allocate virtual memory for command itemlist Facility: LAT, LAT Facility Explanation: LATCP cannot allocate enough virtual memory for a LAT item list needed to execute a command. An accompanying message explains why the virtual memory cannot be allocated. User Action: Correct the situation based on information in the accompanying message.
NOJOBCTX
no job context Facility: JBC, Job Controller Explanation: A call was made to the $GETQUI system service requesting the $QUI_DISPLAY_FILE function without first establishing a job context for this call. User Action: Modify the application to first establish a job context by calling the $GETQUI system service in wildcard mode using either the QUI$_DISPLAY_JOB or the QUI$_DISPLAY_ENTRY function codes.
NOJOBID
job 'nnn' not found in 'queue-name' queue Facility: Shared by several facilities Explanation: A request to modify or delete a job failed because the job does not exist. The message identifies the job by job name or job identification number, depending on the command specification. User Action: Verify that the job identification number or job name is entered correctly. If it is not, reenter the command with the correct job identification number or job name. If the job identification number or job name is correct, this message indicates that the job is no longer in the queue; that is, the job has already been processed or is currently being processed.
NOJOBNAME
job 'job-name' not found in 'queue-name' queue Facility: Shared by several facilities Explanation: A request to modify or delete a job failed because the job does not exist. The message identifies the job by job name or job identification number, depending on the command specification. User Action: Verify that the job identification number or job name is entered correctly. If it is not, reenter the command with the correct job identification number or job name. If the job identification number or job name is correct, this message indicates that the job is no longer in the queue; that is, the job has already been processed or is currently being processed.
NOJOURNAL
editing session is not being journaled Facility: VAXTPU, VAX Text Processing Utility Explanation: VAXTPU is invoked without opening a journal file. User Action: If you want to open a journal file, use the built-in procedure JOURNAL_OPEN.
NOKEY
no such key Facility: CONVERT, Convert Utility Explanation: You have specified a legal but nonexistent value with /KEY. For example, if the file has two keys, 0 and 1, and you specify /KEY=2, you will receive this error message. User Action: Specify a valid number with /KEY.
NOKEYMAP
attempt to access an undefined key map 'key-map-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You are referring to a key map that has not yet been created. User Action: Enter the built-in procedure SHOW (KEY_MAPS) on the command line to obtain the names of valid key maps.
NOKEYMAPLIST
attempt to access an undefined key-map list 'key-map-list-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You are referring to a key-map list that has not yet been created. User Action: Enter the built-in procedure SHOW (KEY_MAPS_LISTS) on the command line for a list of valid key-map list names.
NOKEYW
qualifier name is missing - append the name to the slash Facility: CLI, Command Language Interpreter (DCL) Explanation: A slash character (/) is present on a command but is not followed by a qualifier keyword name. User Action: Reenter the command specifying the qualifier or removing the slash.
NOKFEFND
known file entry not found Facility: INSTALL, Install Utility Explanation: There is no known file entry in the known file list for the file you want to create, replace, or list. User Action: Use /LIST to find out what entries are in the file list.
NOLBLS
label ignored - use only within command procedures Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is output if you try to put a label on a command line that is supplied to DCL interactively. Labels are not appropriate in this context and are ignored. Any command that follows the label will be executed. User Action: None.
NOLCL
image does not contain local symbols Facility: PATCH, Patch Utility Explanation: When you initialized PATCH, no local symbol information is available to PATCH. User Action: To ensure that local symbol information is passed to PATCH, reassemble or recompile and link your program including the Debugger or Traceback Facility.
NOLICENSE
operation requires software license Facility: SYSTEM, VMS System Services Explanation: You are requesting a function that requires a software license. This function cannot be done until the license kit is installed. (DECnet-VAX is the only software license that is currently associated with this message.) User Action: Buy the license and install the license kit.
NOLINKS
no slots in logical link vector Facility: SYSTEM, VMS System Services Explanation: The maximum number of allowable logical network links exists and no more slots are available to establish another link. User Action: Wait and retry the request later. If the problem persists, ask the system manager to increase the allowed number of logical links. Or, if you have SYSPRV, you could run the Network Control Program (NCP) and change the number of maximum allowable links yourself. To increase the number of allowable links, use the NCP command SET EXECUTOR MAXIMUM LINKS n, where the valid range for n is between 1 and 960, unless the ALIAS MAXIMUM LINKS parameter is also specified, in which case the valid range is between 1 and 512. A reasonable range for maximum links on most networks is between 25 and 50.
NOLIST
list of parameter values not allowed - check use of comma (,) Facility: CLI, Command Language Interpreter (DCL) Explanation: A command that accepts only a single input value for a parameter contains multiple values separated by commas (,). User Action: Reenter the command; specify only one file. If necessary, enter the command once for each file specified.
NOLIST
parameter list not allowed Facility: DSR, DIGITAL Standard Runoff Explanation: The command does not accept a list of parameters. User Action: Eliminate the parameter list.
NOLIST
there is no known file entry List Facility: INSTALL, Install Utility Explanation: The known file entry list is not created. Therefore, LIST, DELETE, REMOVE, and PURGE will have no effect. User Action: None. The list is created automatically when the first known file is created with the ADD, CREATE, or REPLACE commands.
NOLISTENER
specified remote system process not listening Facility: SYSTEM, VMS System Services Explanation: A system facility attempted to connect to a remote process that is not enabled for connections. User Action: Ensure that the remote process is receiving connections.
NOLITERAL
no LITERAL translation exists for 'xx' Facility: PATCH, Patch Utility Explanation: The value represented as 'xx' does not have a symbolic equivalent associated with it. Either there is no name for 'xx' or the symbolic names were not included at compile or link time. User Action: Ensure that local symbol information is passed to PATCH by reassembling or recompiling and linking your program including the Debugger or Traceback Facility.
NOLOAD
network and sequentially loaded files are not installable Facility: INSTALL, Install Utility Explanation: Known file entries cannot be created for files that are stored on magnetic tape or that are accessible through a network. User Action: Transfer the file to a disk and then install it.
NOLOCKID
no lock id, available Facility: SYSTEM, VMS System Services Explanation: The system's lock identification table is full when an $ENQ system service request is attempted. User Action: Either retry the program or increase the size of the lock id table by increasing the value of the SYSGEN parameter LOCKIDTBL.
NOLOGNAM
no logical name match Facility: SYSTEM, VMS System Services Explanation: A specified logical name does not exist or cannot be deleted by the current access mode. User Action: Check for a programming error. Verify the spelling of the logical name.
NOLOGTAB
no logical name table match Facility: SYSTEM, VMS System Services Explanation: The specified logical name does not exist. User Action: Check for a programming error. Verify the spelling of the logical name table.
NOLOWVER
no lower version of file 'filespec' found Facility: DIFF, DIFFERENCES Command Explanation: The Differences Utility cannot default the revision file specification because no lower version of the master file exists. User Action: Check that the file exists. Reenter the command, explicitly specifying the revision file specification.
NOMACFOUND
no .MACRO found in 'input-filespec' Facility: LIBRAR, LIBRARY Command Explanation: The specified input file does not contain a properly formatted macro. User Action: Reformat the macro source file.
NOMALFUN1
no malfunctions detected since power up Facility: DTK, DECtalk Facility Explanation: This informational message indicates that no malfunctions occurred since the DECtalk device was turned on. This is the first reply. User Action: None.
NOMALFUN2
no malfunctions detected since power up Facility: DTK, DECtalk Facility Explanation: This informational message indicates that no malfunctions occurred since the DECtalk device was turned on. This is the second or later reply. User Action: None.
NOMATCH
'filespec' - 'xxx' records Facility: SEARCH, SEARCH Command Explanation: This informational message displays the name of the file and the number of records searched. The search strings were not found in the file. User Action: None.
NOMATCH
no match found against input string Facility: STR, String Manipulation Facility Explanation: There is no match found for the input string that is passed to the routine. User Action: None.
NOMATCHES
no strings matched Facility: SEARCH, SEARCH Command Explanation: The search operation was able to open and search one or more files, but the files did not contain the search strings. This message is informational. User Action: None.
NOMATCHFOU
no match found Facility: LBR, Librarian Subroutine Package Explanation: The specified module does not appear in the module name table. User Action: Ensure that the module exists in the current library.
NOMBX
no associated mailbox for inbound connects Facility: SYSTEM, VMS System Services Explanation: A channel specified for network operations does not have a mailbox associated with it. User Action: Correct the source program to create a mailbox, and associate the mailbox with the channel on the assign request.
NOMCHKFRAME
no machine check frame for CPU nn Facility: SDA, System Dump Analyzer Explanation: The machine check frame for CPU nn does not contain any valid information. User Action: None.
NOMEANING
qualifiers 'qualifier-names' are no longer meaningful for the 'command-name' command Facility: Shared by several facilities Explanation: The command contains one or more DCL qualifiers that have been phased out in a new release of VMS. User Action: Check release notes or new documentation for updated information about the specified command.
NOMEMBER
specified node has left cluster Facility: SMI, System Management Integrator/Server Explanation: The cluster configuration changed while processing a SYSMAN command. The command continues on the next node in the environment. User Action: None.
NOMODNAM
no module name found for 'input filespec' Facility: LIBRAR, LIBRARY Command Explanation: An attempt is made to insert unnamed text modules into a text library. User Action: Use the /MODULE qualifier to name the text modules.
NOMODS
no input modules specified (or found) Facility: LINK, Linker Utility Explanation: The command line did not specify any input modules. User Action: Reenter the command, specifying some modules to link.
NOMODS
no modification made Facility: CDU, Command Definition Utility Explanation: The process tables were not modified because a CLD file is not entered in the command string. User Action: Add CLD file to the command string.
NOMODS
no modifications made to system authorization file Facility: AUTHORIZE, Authorize Utility Explanation: This is an informational message. User Action: None.
NOMORECHAR
no more characteristics found Facility: JBC, Job Controller Explanation: No more characteristics exist that match a wildcard name specified for the QUI$_DISPLAY_CHARACTERISTICS function of the $GETQUI system service. This condition indicates that at least one match had been found in previous calls during the wildcard search for characteristics. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMOREENT
no more entries found Facility: JBC, Job Controller Explanation: No more job entries exist for the specified user name. This condition is returned for the QUI$_DISPLAY_ENTRY function of a call to the $GETQUI system service. It indicates that at least one entry had been found in previous calls during the wildcard search for entries. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMOREFILE
no more files found Facility: JBC, Job Controller Explanation: No more files for the specified batch or print job exist. This condition is returned for the QUI$_DISPLAY_FILE function of a call to the $GETQUI system service. It indicates that at least one file had been found in previous calls during the wildcard search for files. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMOREFILES
no more files Facility: SYSTEM, VMS System Services Explanation: No more files match a wildcard in a file specification string. At least one match is found. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
NOMOREFORM
no more forms found Facility: JBC, Job Controller Explanation: No more forms match a wildcard name specified for the QUI$_DISPLAY_FORM function of the $GETQUI system service. This condition indicates that at least one match had been found in previous calls during the wildcard search for forms. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMOREITEMS
no more items in message Facility: SMB, Symbiont Services Explanation: This value is returned by the SMB$READ_MESSAGE routine indicating no items remain on the list. User Action: Note the condition and, if necessary, modify the source code to detect the condition.
NOMOREITEMS
no more items to be returned Facility: SYSTEM, VMS System Services Explanation: A request dealing with a wildcard list was completed and there are no additional items to be returned. This is an informational message. User Action: None.
NOMOREJOB
no more jobs found Facility: JBC, Job Controller Explanation: No more jobs for the specified batch or print queue exist. This condition is returned for the QUI$_DISPLAY_JOB function of a call to the $GETQUI system service. It indicates that at least one job had been found in previous calls during the wildcard search for jobs. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMOREKEYS
no more keys defined Facility: SMG, Screen Management Facility Explanation: SMG$LIST_KEY_DEFS, when called repeatedly, returns all the key definitions in a key table. When there are no more definitions, this error is returned. User Action: Modify your program to expect this condition, if necessary.
NOMOREMSG
no more messages Facility: MAIL, Mail Utility Explanation: You have no more messages to read. User Action: If you want to read your messages again, enter the MAIL command READ; otherwise, no action is required.
NOMORENODS
no more nodes in database Facility: LAT, LAT Facility Explanation: This informational message is returned when a wildcard search of nodes in the database reaches the last node. User Action: None.
NOMOREPROC
no more processes Facility: SYSTEM, VMS System Services Explanation: The search for processes is complete. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
NOMOREQUE
no more queues found Facility: JBC, Job Controller Explanation: No more queues match a wildcard name specified for the QUI$_DISPLAY_QUEUE function of the $GETQUI system service. This condition indicates that at least one match had been found in previous calls during the wildcard search for queues. User Action: Note the condition and, if necessary, modify the source program to detect and respond to the condition.
NOMORESVCS
no more services in database Facility: LAT, LAT Facility Explanation: This informational message is returned when a wildcard search of services in the database reaches the last service. User Action: None.
NO_MORMSG
no more broadcast messages are available Facility: SMG, Screen Management Facility Explanation: A call to SMG$GET_BROADCAST_MESSAGE found that there are no more messages to be obtained. User Action: None.
NOMP
qualifier only valid for multiprocessor systems Facility: Shared by several facilities Explanation: This error is returned when the system is not running in a multiprocessor configuration. User Action: None.
NOMSGS
no messages Facility: MAIL, Mail Utility Explanation: There are no mail messages. User Action: None.
NOMSGS
no messages defined Facility: MESSAGE, Message Utility Explanation: No messages have been defined in the message source file. User Action: Ensure that at least one message definition appears in the message source file.
NOMTCHENDM
no matching .ENDM for macro 'macro-name' in library 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: The specified macro does not contain a matching .ENDM line. User Action: Reformat the macro source file.
NOMTCHENDR
'location' missing .ENDR for macro 'macro-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: The Librarian Utility found a matching .ENDM before the required .ENDR. User Action: Correct the macro source file.
NOMTCHFOU
no match found Facility: LBR, Librarian Subroutine Package Explanation: The specified module does not appear in the Module Name Table (MNT). User Action: Ensure that the module exists in the current library.
NOMTCHFOU
no matches found for 'module-name' Facility: LIBRAR, LIBRARY Command Explanation: The module specified with the /ONLY qualifier is not in the Module Name Table (MNT). User Action: Ensure that the specified module exists.
NOMULTBK
ACP multiple block buffering not supported yet Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NONAMES
there are no names matching the one requested Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure EXPAND_NAME cannot find any names matching the one you requested. User Action: None.
NONANSICRT
SYS$INPUT must be a supported CRT Facility: VAXTPU, VAX Text Processing Utility Explanation: You ran VAXTPU with SYS$INPUT associated with a terminal that does not have the appropriate characteristics, or you ran VAXTPU from a command procedure without assigning SYS$INPUT to SYS$COMMAND. User Action: Run VAXTPU from a supported device or use the /NODISPLAY command qualifier. In a command procedure, assign SYS$INPUT to SYS$COMMAND before invoking VAXTPU.
NONBRDMSG
nonbroadcast message returned Facility: SMG, Screen Management Facility Explanation: A call to SMG$GET_BROADCAST_MESSAGE found that a nonbroadcast message was returned. User Action: None.
NONCONTIG
'filename' is not contiguous due to insufficient contiguous space Facility: PATCH, Patch Utility, BACKUP, Backup Utility Explanation: The specified file is originally allocated contiguous blocks. However, because the output volume lacked enough space for contiguous blocks, the file has been allocated noncontiguous blocks. User Action: If necessary, reorganize the volume to free a sufficient number of contiguous blocks and reenter the command.
NONCONTIG
noncontiguous image file being written Facility: PATCH, Patch Utility Explanation: The image file being written by PATCH is not contiguous. This error may be relevant to device drivers. User Action: None.
NONEDEL
no files processed on deletion pass Facility: BACKUP, Backup Utility Explanation: BACKUP did not process any files in the deletion pass. That is, no files were deleted by the BACKUP operation. User Action: None.
NONEFOUND
no folders found in file 'filename' with a folder name greater than 'filename' Facility: MAIL, Mail Utility Explanation: User entered a DIR/FOLDER/START=string command, but there were no folders found alphabetically higher than the specified string. User Action: None.
NONEREC
no files processed on recording pass Facility: BACKUP, Backup Utility Explanation: BACKUP did not process any files in the recording pass. That is, no files had their backup date updated by the BACKUP operation. User Action: None.
NONET
network unavailable Facility: SHOW, SHOW Command Explanation: The network is unavailable. User Action: None.
NONETMBX
operation requires NETMBX privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires NETMBX privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NONEWMAIL
no new messages Facility: MAIL, Mail Utility Explanation: User has requested a READ/NEW, DIR/NEW, or SELECT/NEW command and there is no new (unread) mail. User Action: None.
NONEXDRV
nonexistent drive Facility: SYSTEM, VMS System Services Explanation: The drive specified in an I/O request either does not exist or the drive select plug is removed. User Action: Verify the availability and status of the device. Also, check the source program for errors.
NONEXIST
authorization file does not exist Facility: CAF, Cluster Authorization File Service Explanation: A SYSMAN CONFIGURATION SHOW CLUSTER_AUTHORIZATION command has been entered and SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT does not exist. User Action: Create the file on all the cluster members with a CONFIGURATION SET CLUSTER_AUTHORIZATION command at the SYSMAN> prompt.
NONEXISTBUF
buffer 'buffer-name' does not exist Facility: VAXTPU, VAX Text Processing Utility Explanation: The buffer that you are trying to use has not been created. User Action: Use a current buffer or create a new one.
NONEXPR
nonexistent process Facility: SYSTEM, VMS System Services Explanation: A process name or process identification specified in a command or system service request is not valid. User Action: Verify that the process name or identification is correct and that the process is not already deleted. If a process name is entered, the process must be in the same group.
NONEXSTACP
Nonexistent ACP process Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NONLOCAL
device is not a local device Facility: SYSTEM, VMS System Services, MOUNT, Mount Utility and INIT, INITIALIZE Command Explanation: The device name specified in a command or program request is not a local device; that is, the device name contains a network node name. User Action: Verify the device name (or logical name, if a logical name is specified), and reenter the command specifying a device in the host system.
NONODE
node name has not been initialized Facility: LAT, LAT Facility Explanation: The local LAT node has not been initialized. User Action: Use the LATCP command SET NODE to initialize the local LAT node.
NONPHYSET
nonphysical save set supplied to physical operation Facility: BACKUP, Backup Utility Explanation: A save set created without the /PHYSICAL qualifier is used as input to an operation with the /PHYSICAL qualifier. User Action: Use the BACKUP/LIST command to determine how the save set is created. Reevaluate the operation and reenter the command.
NONPIC
cannot map section AS to same addresses as others mapped it Facility: PPL, Parallel Processing Facility Explanation: PPL cannot map requested address space to the same addresses in all processes. User Action: If it is critical to the application that the requested space appear at the same addresses in all processes, the user must take steps to ensure that enough space is made available. This may require increasing system quotas or reserving the required addresses through link time operations.
NONPICDAT
'number' relocatable address references in 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: This message informs you of the number of .ADDRESS fixups to be done in each module by the image activator at run time. It is issued only if a full map is requested. User Action: None.
NONPICIMG
shareable image 'image-name' is non-position-independent Facility: LINK, Linker Utility Explanation: While building a position-independent shareable image, a shareable image is input that is not position- independent. The shareable image being created is also built non-position-independent. User Action: None. If possible, rebuild the non-position- independent shareable image so that it is position-independent.
NONPICREF
failure to use .ADDRESS for relocatable data in psect 'psect-name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A reference is made to relocatable data using other than the MACRO .ADDRESS directive in a shareable image. User Action: Use the MACRO .ADDRESS directive in reference to relocatable data; otherwise, the image will be position-dependent.
NONSMPDRV
non SMP driver cannot be loaded Facility: SYSGEN, System Generation Utility Explanation: SYSGEN cannot load this driver because the driver has not been modified to support symmetric multiprocessing (SMP). User Action: Modify the driver to conform to symmetric multiprocessing requirements, or turn off SMP.
NONSTDUNI
unibus/qbus 'device-name' in nonstandard configuration Facility: SYSGEN, System Generation Utility Explanation: The vector on the device specified in the message needs to be reconfigured. User Action: Call the Digital Services Group.
NOONE_ENABLED
no one presently enabled for event notification Facility: PPL, Parallel Processing Facility Explanation: Event trigger is successfully queued, and no one is presently enabled to receive it. The first caller to enable the trigger will receive it. User Action: Continue normally.
NOOPCOM
OPCOM not running at 'time'; security alarms may be lost Facility: AUDSRV, Audit Server Explanation: The audit server detects that the Operator Communications Process (OPCOM) is not running. User Action: From the SYSTEM account, start OPCOM using the DCL command @SYS$SYSTEM:STARTUP OPCOM.
NOOPENJOB
no open job for requesting process Facility: JBC, Job Controller Explanation: The requesting process did not open a job with the SJC$_CREATE_JOB function prior to making the current $SNDJBC request, or did not open a job with the SMR$K_CREJOB function prior to making the current $SNDSMB request. User Action: Modify the program to open a job first.
NOOPER
no operator is available to handle the request Facility: BACKUP, Backup Utility Explanation: There are no operator terminals enabled to handle this request. User Action: Either service the request yourself or abort the request. To ensure that no operator intervention is required in a BACKUP operation, specify the /NOASSIST qualifier on the command line.
NOOPER
OPER privilege required on all nodes, access rejected Facility: SMI, System Management Integrator/Server Explanation: OPER privilege is required to run SYSMAN. If any nonlocal environment is used, OPER privilege must also be authorized in the UAF on each remote node. User Action: Correct the authorized privileges in the associated UAF files.
NOOPER
operation requires OPER privilege Facility: SYSTEM, VMS System Services and JBC, Job Controller Explanation: A command or program requested a system function that requires OPER privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOOPER
SYSMAN requires OPER privilege Facility: SYSMAN, Cluster System Management Utility Explanation: You are required to have OPER privilege. User Action: Enter a SET PROCESS/PRIVILEGE=OPER command from the DCL level before entering SYSMAN commands.
NOOPR
no operator available to service request Facility: MOUNT, Mount Utility Explanation: There is no operator present to service the request. User Action: You can either service the request yourself or abort the request.
NOOPRND
missing operand in expression Facility: PATCH, Patch Utility Explanation: One or more operands were omitted from the expression. User Action: Add the correct number of operands and retry.
NOOUTPUT
no output selected . . . specify /DISPLAY, /RECORD, or /SUMMARY Facility: MONITOR, Monitor Utility Explanation: The MONITOR request selected (explicitly or implicitly) none of the three possible output types (DISPLAY, RECORD, SUMMARY). User Action: Reenter the MONITOR request, specifying any combination of the qualifiers: /DISPLAY, /RECORD, or /SUMMARY.
NOOUTQUAL
the /SHOW qualifier is invalid without specifing the /OUTPUT qualifier Facility: BAD, Bad Block Locator Utility Explanation: The /SHOW qualifier is specified without specifying the /OUTPUT qualifier. User Action: Specify the /OUTPUT qualifier with the /SHOW qualifier in the command.
NOP1VA
P1 space not supported in shareable images Facility: SYSTEM, VMS System Services Explanation: P1 space is not supported in shareable images. User Action: Relink the image, positioning all binary data in P0 space.
NOPAGEDYN
unable to allocate enough paged dynamic memory Facility: INSTALL, Install Utility Explanation: INSTALL cannot complete the operation because paged dynamic memory is not accessible. User Action: Contact your system manager.
NOPARAM
no such parameter Facility: SYSGEN, System Generation Utility and SYSBOOT, System Bootstrap Facility Explanation: The parameter name specified in a SET or SHOW command is not valid. User Action: Reenter the command specifying a valid parameter name.
NOPAREN
value improperly delimited - supply parenthesis Facility: CLI, Command Language Interpreter (DCL) Explanation: A value supplied as part of a parenthesized value list for a parameter, qualifier, or keyword is missing a delimiting parenthesis. User Action: Reenter the command with the missing parenthesis.
NOPARENT
there is no parent process to attach Facility: VAXTPU, VAX Text Processing Utility Explanation: The current process is the top-level process. There is no parent process. User Action: None. Without a parent process there is nothing to attach to.
NOPARENT
there is no parent to which to attach Facility: MAIL, Mail Utility Explanation: User specified an ATTACH/PARENT command, and the current process is not a subprocess. The ATTACH/PARENT command is only legal in a subprocess. User Action: None.
NOPARM
either a parameter name or group qualifier is required Facility: SYSMAN, Cluster System Management Utility Explanation: A PARAMETERS SHOW command must include either a parameter name to be displayed or a qualifier specifying a parameter group. User Action: Respecify the command with a parameter name or group qualifier.
NOPARM
no parameters Facility: NCP, Network Control Program Explanation: No parameters were specified for a command. User Action: Reenter the command with parameters.
NOPASS
need remote password and SYS$COMMAND not a terminal Facility: SYSMAN, Cluster System Management Utility Explanation: An environment that requires an access-control password and SYSMAN is not being run interactively. A password can only be read when SYS$COMMAND is a terminal device. User Action: Rerun SYSMAN interactively.
NOPASSWORD
password must be supplied Facility: MOM, Maintenance Operation Module Explanation: In this LOOP NODE or LOOP EXECUTOR command, a password must be supplied. User Action: Supply a password with the LOOP command.
NOPATAREA
insufficient patch area at 'addr', size = 'nn' Facility: PATCH, Patch Utility Explanation: The current user-defined patch area is not large enough to store the given code. User Action: Use the default patch area or an alternate user- defined patch area of a larger size.
NOPE
permanent qualifier not specified Facility: Shared by several facilities Explanation: You tried to set a terminal characteristic for a terminal that is not allocated to a user process. The default action of the DCL command SET TERMINAL is to set a specified terminal characteristic for the duration of the current terminal session for the user to whom the terminal is allocated. Therefore, if the terminal is not allocated, the /PERMANENT qualifier must be used with the SET TERMINAL command. You must have the LOG_IO or PHY_IO user privilege to use the /PERMANENT qualifier.
NOPERATOR
no operator coverage Facility: OPCOM, Operator Communication Process Explanation: A DCL command REQUEST specified a nonexistent operator. No terminals are currently enabled for that operator name. User Action: Reenter the DCL command REQUEST specifying an alternative operator.
NOPFNMAP
operation requires PFNMAP privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires PFNMAP privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you did not use a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOPREV
no previous entry exists - new entry created for 'image' Facility: INSTALL, Install Utility Explanation: A Known File Entry is created via the REPLACE command, and there is no previous entry that had to be deleted first. User Action: None. The use of REPLACE implies that an old entry is expected to exist, but didn't.
NOPRINT
file 'filename' cannot be printed. Facility: VMSINSTAL, Install Procedures Explanation: The product installation required the printing of one or more files. The files could not be queued for printing. User Action: An undefined SYS$PRINT queue at your site probably caused this error. If you do not care that the files could not be printed, ignore this message. Otherwise, define a SYS$PRINT queue and reinstall the product.
NOPRIV
insufficient privilege or queue protection violation Facility: JBC, Job Controller Explanation: The queue protection denies access to the queue for the specified operation. User Action: None.
NOPRIV
no privilege for attempted operation Facility: SYSTEM, VMS System Services and JBC, Job Controllerand PTD, Pseudo Terminal Explanation: A command or program requested a system function that requires a specific user privilege or privileges; the current process does not have the requisite privilege or privileges. Or a program image attempted to access, modify, or delete a control area created and owned by a more privileged access mode; such areas include pages in memory, I/O channels, or timer queue entries. Or a command or program requested file or volume access which is denied. Or the requesting process does not have the privilege to read or write to this mailbox. (The protection mask is defined when the Mailbox is created.) User Action: If the message is in response to a command entered interactively, verify that the particular command, or qualifier, does not require a specific user privilege or privileges. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. Or verify that you are not attempting to modify a VMS RMS or system- owned data area or memory page. If this message is associated with a vector disabled (VECDIS) status code, an ACL on the system's vector capability has prevented the process from executing vector instructions. In each case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege. Verify the file or volume name. Have the owner of the file or volume change the protection value.
NOPRIV
operation requires SYSPRV privilege Facility: CAF, Cluster Authorization File Service Explanation: Any access to the cluster authorization file requires SYSPRV privilege. User Action: Enter a SET PROFILE/PRIVILEGE=SYSPRV command, then reenter your original command.
NOPRIV
user denied privilege to write to volume on 'device-name' Facility: MOUNT, Mount Utility Explanation: The user has requested initialization of a volume and does not have the privilege to write to it. User Action: Mount either a tape that the user has write privilege to or a blank tape. Request initialization of this tape when replying to the next mount request.
NOPRIVDIRSUM
some directories protected against access Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: During the directory scan the utility was prevented from reading a directory because of a privilege error (for example, the user running the utility lacked sufficient privileges). Since the utility's method of determining whether a file is lost is to scan all directories for the file, the utility's list of lost files is incorrect. Therefore, no attempt will be made to retrieve lost files. User Action: Assign yourself BYPASS privilege and rerun the utility.
NOPRMCEB
operation requires PRMCEB privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires PRMCEB privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOPRMGBL
operation requires PRMGBL privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires PRMGBL privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOPRMMBX
operation requires PRMMBX privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires PRMMBX privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOPROC
the kit installation procedure is missing. Facility: VMSINSTAL, Install Procedures Explanation: The main installation procedure for the product is not located on the distribution media. User Action: Contact the Digital Services Group.
NOPROCESS
no subprocess to interact with Facility: VAXTPU, VAX Text Processing Utility Explanation: The subprocess you tried to send data to or receive data from does not exist. User Action: Re-create the subprocess.
NOPROCTPS
no transaction structures for this process Facility: SDA, System Dump Analyzer Explanation: The selected process is not a participant in any active transactions. User Action: None.
NOPRODS
None of the specified products were found. Facility: VMSINSTAL, Install Procedures Explanation: None of the products you specified for installation exist on the distribution media. User Action: Specify products that exist on the media.
NOPROT
protocol not supported on remote node Facility: REM, Set Host Facility Explanation: A DCL command SET HOST has been entered on a node that does not support the remote terminal protocol. User Action: None.
NOPSCTS
no psects defined in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The specified module did not define any psects. At least one psect must be defined in each object module. User Action: Define a psect in the specified module.
NOPSWAPM
operation requires PSWAPM privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires PSWAPM privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOQFILE
no disk quota file available Facility: SYSTEM, VMS System Services Explanation: The quota file does not exist. User Action: Verify that you are using the correct device. Create the quota file.
NOQUAL
no qualifier in statement 'number' Facility: FDL, Create/FDL Utility Explanation: You have left off a qualifier from the attribute keyword. User Action: Edit the FDL file and add the qualifier.
NOQUAL
no qualifier in statement 'number' Facility: FDL, Edit/FDL Utility Explanation: You specified a secondary that requires a qualifier, but none is given. User Action: Specify a qualifier for a secondary.
NOQUAL
qualifiers not allowed - supply only verb and parameters Facility: CLI, Command Language Interpreter (DCL) Explanation: A command that has no qualifiers is specified with a qualifier. User Action: Reenter the command; do not specify any qualifiers.
NOQUECTX
no queue context Facility: JBC, Job Controller Explanation: A call was made to the $GETQUI system service requesting the $QUI_DISPLAY_JOB function without first establishing a queue context for this call. User Action: Modify the application to first establish a queue context by calling the $GETQUI system service in wildcard mode using the QUI$_DISPLAY_QUEUE function code.
NOQUESPACE
no space in system job queue file Facility: JBC, Job Controller Explanation: The system job queue file is full and cannot be extended. User Action: Notify the system manager, as this condition indicates a lack of space on the disk that contains the system job queue file. In the meantime, wait for existing jobs to complete and reenter your request.
NOQUEUE
'queue-name' queue does not exist Facility: Shared by several facilities Explanation: A request to enter or change a queued file failed because the queue does not exist. User Action: Verify the queue name in the command and reenter the command. To determine the names and status of currently available queues, use the DCL command SHOW QUEUE/DEVICES/BATCH. Note that the DCL commands SET QUEUE and SHOW QUEUE do not translate logical names. If you specified a logical name, reenter the command with the physical queue name.
NOQUOTE
quoted string missing end quote
Facility: AUTHORIZE, Authorize Utility
Explanation: Your command line is missing a quotation mark (").
User Action: Reenter the command line with both quotation marks.
NORCP
RCP not active Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NORCVBUF
NETACP - no receive buffer available Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOREAD
unable to access location Facility: SDA, System Dump Analyzer Explanation: SDA is unable to read a certain location. The inaccessible location may be an implied reference to memory made during the execution of an SDA command. User Action: None.
NOREADCP
no read access to interrupted command procedure Facility: CLI, Command Language Interpreter (DCL) Explanation: An executing command procedure was interrupted by a Ctrl/Y and is still active. The READ command is trying to read data from this interrupted command procedure which has no read access. User Action: To read data from the terminal, repeat the READ command using SYS$COMMAND as the input file. You can also use the STOP command to deactivate the interrupted command procedure, and repeat the READ command as originally specified.
NOREADER
no read channel is assigned to the device
Facility: SYSTEM, VMS System Services
Explanation: This message can be returned under either of the
following conditions:
o A sensemode readercheck $QIO request or a write readercheck
$QIO request was issued to a mailbox that has no reader
assigned to it.
o A write readercheck $QIO request was issued to a mailbox when
no read channels were assigned to the mailbox.
User Action: The mailbox driver allows channels to be assigned
to the mailbox as read-only, write-only, or read/write (the
default). Applications using read-only or write-only channels
should anticipate this error and count on it for synchronization.
If necessary, recode your application to expect this error or
consider using the older mailbox driver features; that is, use
read/write channels and do not use readercheck on a write request.
Refer to the VMS I/O User's Reference Manual: Part I for more
information about the mailbox driver.
NO_RECORD
unable to locate record for this transaction state Facility: LMCP, Log Manager Control Program Explanation: The transaction identifier's record could not be found when scanning for active transactions; however, the transaction is considered still active. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP and the DCL DUMP commands for the given log file.
NOREDEFINE
built-in procedure 'procedure-name' cannot be redefined Facility: VAXTPU, VAX Text Processing Utility Explanation: Your program uses a VAXTPU built-in procedure name as the name of a user-written procedure. Built-in procedures cannot be superseded by user-defined procedures. User Action: Give your procedure a name that does not conflict with any of the names of the VAXTPU built-in procedures.
NOREF
page reference not found Facility: DSR, DIGITAL Standard Runoff Explanation: An internal error has occurred. User Action: Submit a Software Performance Report (SPR). If possible, include the file that caused the error in the Report (SPR).
NORELNOTE
unable to locate release notes Facility: VMSINSTAL, Install Procedures Explanation: You specified the Release Notes option during a layered product installation. The product does not include online release notes. User Action: None.
NORELOC
relocation of CASE instructions not supported Facility: PATCH, Patch Utility Explanation: The PATCH Utility does not automatically move CASE instructions to the patch area. User Action: CASE instructions may be moved to the patch area by using PATCH commands DELETE/INSTRUCTION and DEPOSIT/INSTRUCTION /PATCH_AREA and the MACRO assembler directive .WORD.
NOREMBROAD
no VAXcluster terminals were notified because OPCOM is not available Facility: OPCOM, Operator Communication Process Explanation: A REPLY command attempting to send a message to terminals on other nodes within a VAXcluster has failed because OPCOM is not available to satisfy the request. The message is sent only to terminals on the local node. User Action: Restart OPCOM with the following command: $ @SYS$SYSTEM:STARTUP OPCOM
NOREMOTE
remote node name not permitted in 'string' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility found a network node name in a context where network access is not permitted. User Action: Reenter the command specifying a local device name, or log in to the desired node and reenter the EXCHANGE command on that node.
NOREMWAIT
the /WAIT qualifier requested, therefore no VAXcluster terminals notified Facility: OPCOM, Operator Communication Process Explanation: A REPLY command attempted to send a message to terminals on other nodes within a VAXcluster, but the /WAIT qualifier was specified, which requests that the message be sent synchronously. User Action: If the message must be delivered to terminals on other VAXcluster nodes, reissue the command without the /WAIT qualifier.
NORENDEV
cannot RENAME to a different device Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a RENAME command which attempted to rename a file from one device to another. User Action: Use the COPY command to move a file to another device, or check the RENAME command for a misspelled device name.
NORENEXISTS
file 'filename' not renamed, 'filename' already exists Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility cannot rename a file because a file with the same name already exists. User Action: Choose a file name that does not already exist, or delete the existing file and redo the RENAME command.
NORENLOCK
file 'filename' not renamed, volume is write locked Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not perform a RENAME command because the output volume is write locked. User Action: Remount the output volume with write access, then reenter the command.
NOREPAIR
one or more volumes write locked - /REPAIR canceled Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: One or more volumes of the volume set are write locked, and therefore a /REPAIR operation cannot be executed. User Action: Write enable all volumes of the volume set and reenter the command.
NOREQ
symbol 'symbol-name' not found in SDA symbol table Facility: SDA, System Dump Analyzer Explanation: SDA cannot find a symbol in the SYS.STB file that is vital to its initialization. User Action: None.
NOREQSYM
symbol 'name' not found in system symbol table Facility: SDA, System Dump Analyzer Explanation: SDA cannot find a symbol in the SYS.STB file that is required for proper initialization of SDA. User Action: Check the integrity of the symbol table file.
NORESTART
error 'status' attempting to restart server Facility: AUDSRV, Audit Server Explanation: The audit server process encountered an error when attempting to restart itself as a result of a previous error. The displayed status code reflects an error from the $CREPRC system service. User Action: Correct the indicated error and restart the audit server manually using the command SET AUDIT/SERVER=START.
NORESTART
job is not restartable Facility: JBC, Job Controller Explanation: The specified job cannot be requeued because it is not defined to be restartable. User Action: None.
NORETURNVALUE
built-in does not return a value Facility: VAXTPU, VAX Text Processing Utility Explanation: This built-in does not return a value and cannot be used in situations in which a return value will be used. User Action: Do not use this built-in as part of an assignment statement or as part of an expression.
NORIGHTSDB
rights data base file not found Facility: AUTHORIZE, Authorize Utility and SYSTEM, VMS System Services Explanation: An attempt to access the rights database failed because the file does not exist or could not be found (if redirected with a logical name). User Action: Create a rights database using the AUTHORIZE command CREATE/RIGHTS, or contact the system manager to determine why the rights database file does not exist or is not available.
NORMAL
normal successful completion Facility: Shared by several facilities Explanation: This success message indicates that the operation completed normally. User Action: None.
NORMAL
success Facility: LIBRAR, LIBRARY Command and LBR, Librarian Subroutine Package Explanation: This success message is associated with a code returned by the librarian, or generated by the DCL command LIBRARY. The operating system does not normally display this message. This is a success status code. User Action: None.
NORMAL_EXIT
normal exit - ppl index Facility: PPL, Parallel Processing Facility Explanation: This message indicates the occurrence of the normal participant termination event. User Action: Since the application requested this notification, response is application-dependent.
NOROOM
no room for new entry Facility: NCP, Network Control Program Explanation: Insufficient space for new table entry. For example, there is not enough paged pool to allocate room for a new node to be defined. User Action: Increase the resources DECnet is allocated.
NOROOM
no room in dictionary for definition Facility: DTK, DECtalk Facility Explanation: There is no room left in the dictionary for this definition. User Action: Correct your program so that it requests fewer dictionary entries or so that each entry is smaller.
NORSTBLD
cannot build symbol table Facility: PATCH, Patch Utility Explanation: When PATCH is initialized, it could not allocate space to build a symbol table. User Action: Check with your System Manager to ensure that the system is bootstrapped with enough virtual address space.
NORTTB
internal error - No routine table for object Facility: SMI, System Management Integrator/Server Explanation: An object is defined in server tables, but the entry point is 0. User Action: Submit a Software Performance Report showing all SYSMAN commands leading to this error.
NORUNMCR
account restricted - RUN and MCR commands not valid Facility: CLI, Command Language Interpreter (DCL) Explanation: The RUN and MCR commands are foreign commands and have been disabled for this account. (See the VMS DCL Concepts Manual for an explanation of foreign commands.) User Action: This account requires that all images are run using verbs defined in the CLI table (called DCLTABLES) specified for this account.
NOSAVESET
Required save set 'letter' does not exist. Facility: VMSINSTAL, Install Procedures Explanation: The product save set with the specified letter, which is required for the installation, does not exist on the distribution media. User Action: Contact the Digital Services Group.
NOSAVPEXC
no saved vector exception for the exception-id Facility: SYSTEM, VMS System Services Explanation: A call was made SYS$RESTORE_VP_EXCEPTION that specified a value for an exception ID that does not correspond to that of any saved vector exception state. User Action: Correct the program call so that it uses an exception ID that corresponds to one used by a previous call to SYS$SAVE_VP_ EXCEPTION.
NOSCS
error loading SCS code Facility: SYSGEN, System Generation Utility Explanation: You were unable to load SCSLOA.EXE. User Action: Do not attempt to load SCSLOA.EXE.
NOSECEX
no such section exists Facility: PPL, Parallel Processing Facility Explanation: The section specified to flush or delete does not exist. User Action: Recode your program to ensure that the section to flush or delete has been created.
NOSELECT
no select active Facility: VAXTPU, VAX Text Processing Utility Explanation: You tried to select a range of text with only the built-in procedure SELECT_RANGE (and not with the built-in procedure SELECT as well). User Action: Begin a selection by using the built-in procedure SELECT.
NOSELF
connecting to the local node is not allowed Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a service offered by the local node was targeted to the local node. User Action: Retry the connection and specify another node that offers the service.
NOSENDBUF
cannot SEND a buffer to a process using the buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: You tried to send a buffer to a process using the buffer for its output. This can result in an infinite loop. User Action: Move or copy the data to a different buffer and send the new one.
NOSERVER
SMI Server not running in target node
Facility: SMI, System Management Integrator/Server
Explanation: Process SMISERVER is not running in the indicated
node
o It may have been stopped with the STOP command.
o It may have been aborted.
o The remote system has not progressed far enough in the system
startup procedure to have started SMISERVER.
User Action: Determine why SMISERVER is not running. Restart it if
necessary with the following command run from the SYSTEM account
on the target system:
$ @SYS$SYSTEM:STARTUP SMISERVER
NOSETPRV
operation requires SETPRV privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires SETPRV privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOSETPRV
You are not running on an account with SETPRV privilege. Facility: VMSINSTAL, Install Procedures Explanation: When VMSINSTAL begins an installation, it makes sure that your account has the SETPRV privilege. This check failed. User Action: You are asked if you want to continue the installation. Digital recommends that you correct this situation before continuing.
NOSEVER
severity unspecified, ERROR used Facility: MESSAGE, Message Utility Explanation: The severity of a facility's messages has not been defined. The Message Utility has assigned the level ERROR to the messages. User Action: Add the appropriate severity levels to the message source file, either with severity definitions or with severity qualifiers on message definitions.
NOSHDWMEM
no eligible shadow set members to mount the shadow set Facility: MOUNT, Mount Utility Explanation: There are no valid volumes to create the shadow set. This error message is followed by the failed status code for each proposed member. User Action: Examine the status codes, correct the situation, and reenter the command.
NOSHMBLOCK
no free shared memory block available for creation Facility: SYSTEM, VMS System Services Explanation: No free shared memory control block (mailbox, common event flag cluster, or global section descriptor) is available for creation. User Action: Wait for the resource to become available, or reboot the system and reinitialize shared memory, specifying more of the needed resource.
NOSHMEM
operation requires SHMEM privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires SHMEM privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOSHMGSD
No shared memory global section dsc found for page Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOSHOWBUF
variable SHOW_BUFFER does not exist or is not a buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure SHOW depends on SHOW_BUFFER existing as a variable that references a buffer. User Action: Create the variable SHOW_BUFFER and have it reference a buffer before retrying SHOW.
NOSHRD
file cannot be made SHARED Facility: INSTALL, Install Utility Explanation: Only native-mode images and compatibility-mode images supported by the AME provided by VAX RSX are supported as shareable known files. User Action: Reinstall without the /SHAR qualifier.
NOSHRIMG
image activator message Facility: SYSTEM, VMS System Services Explanation: Privileged shareable images, also known as user- written system services or protected images, cannot reference other shareable images. This check is made when the privileged shareable image is activated. If a reference to another image is detected, the entire activation is aborted and this error message is issued. User Action: Rewrite the privileged shareable image so that it does not reference other shareable images.
NOSIGNAL
no signal currently active Facility: SYSTEM, VMS System Services Explanation: A call to the Unwind Call Stack ($UNWIND) system service is made when there is no exception condition. The procedure that is calling $UNWIND is not called by the exception dispatcher. User Action: Check for a programming error.
NOSLOT
no pcb available Facility: SYSTEM, VMS System Services Explanation: The maximum number of processes that can be created at one time has been exceeded. User Action: Wait for another process to be deleted, or increase the MAXPROCESSCNT system parameter.
NOSOLICIT
interrupt message not solicited Facility: SYSTEM, VMS System Services Explanation: The program attempted to send an interrupt message to a partner on a remote node, but the DECnet-VAX implementation on that node has not solicited a message. User Action: Wait and retry the request.
NOSPACE
failure to map symbol table, EXPREG status = 'xxxxxxxx' Facility: TRACE, Traceback Facility Explanation: The traceback facility cannot perform a symbolic traceback because the symbol table cannot be mapped. The hexadecimal status code from the Expand Program/Control Region ($EXPREG) system service indicates the reason for the failure. User Action: Submit a Software Performance Report (SPR).
NOSPACE
There are not enough blocks to restore the system disk. Facility: VMSINSTAL, Install Procedures Explanation: After installation on a dual-RL02 system, VMSINSTAL attempts to restore your system disk to its original tailoring configuration. However, there are not enough free blocks left on the system disk. User Action: VMSINSTAL tells you how many additional free blocks are required. Do the following: 1. Purge and delete files to make more space on the system disk. 2. Restore the original tailoring configuration.
NOSRVC
service 'service-name' not known Facility: LAT, LAT Facility Explanation: A LAT connection attempt was issued for a specified service that is unknown to the local node. User Action: Retry the connection until the service becomes known or see if there is something wrong with a node offering the specified service. Possibly the service group codes on the local node do not intersect with the group codes for the specified service.
NOSTACKMEM
no space is currently available to create a new stack Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A call to cma_create_thread or another DECthreads routine requires a new stack to be created, but there is insufficient space to create it. User Action: Reduce the value of the stack size attribute so that it does not exceed the stack cluster size.
NOSTATS
run-time statistics not available Facility: ERF, Error Log Utility Explanation: An internal consistency error was encountered. User Action: Submit a Software Performance Report (SPR).
NOSTRING
no search string specified Facility: SEARCH, SEARCH Command Explanation: You did not specify a search string. User Action: Specify a search string.
NOSTRMEM
string allocation failure Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
NOSUBEXI
a subprocess does not exist for this virtual display Facility: SMG, Screen Management Facility Explanation: A subprocess does not exist for the specified virtual display. User Action: Call SMG$CREATE_SUBPROCESS to create a subprocess for this virtual display.
NOSUCHACE
ACE for object 'filename' does not exist Facility: SET, SET Facility Explanation: The specified ACE to be deleted or replaced does not exist. User Action: Verify the existence of the ACEs being replaced or deleted with the DIRECTORY/ACL command or the DCL SHOW ACL command.
NOSUCHCHAR
no such characteristic Facility: JBC, Job Controller Explanation: The specified characteristic does not exist. In a wildcard $GETQUI operation, no more characteristics matching the specified selector exist. User Action: None.
NOSUCHCPU
CPU does not exist, system is not a multiprocessor, or
multiprocessing disabled
Facility: SMP, Symmetric Multiprocessing
Explanation: This message is output by the $START/CPU, $STOP/CPU,
or $SHOW CPU command in one of the following cases:
Case 1: A $START/CPU, $STOP/CPU, or $SHOW CPU command was
entered which specified one or more CPU IDs not present in
the configuration.
Case 2: The command was entered on a single CPU configuration
or on a CPU type that does not support multiprocessing
operation.
Case 3: A $START/CPU or $STOP/CPU command was entered on a
multiprocessor configuration in which multiprocessing has been
disabled through the MULTIPROCESSING SYSGEN parameter.
User Action: The action to take for each case follows:
Case 1: Enter the $SHOW CPU command to determine what CPU
IDs are present in the configuration, and reenter the failed
command specifying the correct CPUs and omitting the CPUs not
present.
Case 2: None. This command is not useful on such CPUs.
Case 3: Reset this parameter and reboot the system to enable
multiprocessor operation.
NOSUCHCTX
context parameter invalid or no previous SMI$INIT Facility: SMI, System Management Integrator/Server Explanation: This message indicates an internal error. SMI call specifies an invalid context handle. User Action: Submit a Software Performance Report showing the SYSMAN commands leading to the error.
NOSUCHDEV
no such device available Facility: SYSTEM, VMS System Services Explanation: A device name specified for a command or program does not exist, or a system volume is not ready and available for use. User Action: Verify that the device name is specified correctly, and that the device is available in your system configuration. Use the DCL command SHOW DEVICES to determine whether such a device exists. If the device is coded as a logical name, verify that it is assigned a valid equivalence name.
NOSUCHDEV
nonexistent drive Facility: VAXCLUSTER, VAXcluster Facility Explanation: A nonexistent drive was specified for the satellite system disk. User Action: Check the load assist parameter specification in the DECnet MOP database using NCP. Ensure that the correct system disk is specified and make sure it is served using the SHOW DEVICE /SERVED command.
NOSUCHELE
no element with the specified ID exists Facility: PPL, Parallel Processing Facility Explanation: No element is specified by the input identification. User Action: Recode your program to ensure that the input identification is for a created element.
NOSUCHENT
no such entry Facility: JBC, Job Controller Explanation: The specified job entry in the system queue file does not exist. User Action: None.
NOSUCHFILE
no such file Facility: SYSTEM, VMS System Services Explanation: The message indicates that no file with the given file specification identifier exists, or that the directory entry points to a file that is deleted. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
NOSUCHFILE
no such file Facility: JBC, Job Controller Explanation: The specified file does not exist. In a wildcard $GETQUI operation, no more files matching the specified selector exist. User Action: None.
NOSUCHFILE
startup file does not exist Facility: STDRV, System Startup Driver Explanation: A startup component file specified in the startup database does not exist during system startup. User Action: Verify that the entry in the startup database is correct. If it is correct, verify that the component file is located in the SYS$STARTUP directory.
NOSUCHFORM
no such form Facility: JBC, Job Controller Explanation: The specified form does not exist. In a wildcard $GETQUI operation, no more forms matching the specified selector exist. User Action: None.
NOSUCHID
no such identifier Facility: SYSTEM, VMS System Services or AUTHORIZE, Authorize Utility Explanation: Either the translation failed or the rights database has no record of the identifier. You must add an identifier to the rights database before you can use the VMS Authorize Utility or you must add an identifier to one of the security system services to grant the identifier to or revoke it from a user. The message occurs if the identifier or the user to whom you are granting the identifier does not exist. User Action: Check the spelling of the identifier. Use the AUTHORIZE command SHOW/IDENTIFIER to determine whether the identifiers exist. Add any missing identifier using the AUTHORIZE command ADD/IDENTIFIER.
NOSUCHJOB
no such job Facility: JBC, Job Controller Explanation: The specified job does not exist. In a wildcard $GETQUI operation, no more jobs matching the specified selector exist. User Action: None.
NOSUCHLOC
no lock with the specified ID exists Facility: PPL, Parallel Processing Facility Explanation: No lock element is specified by the input identification. User Action: Recode your program to ensure that the input identification is for a created lock element.
NOSUCHMEM
no shared memory found at specified NEXUS Facility: SYSGEN, System Generation Utility Explanation: The desired shared memory unit number is not found in a search of the backplane interconnect adapter list. User Action: Reenter the command with the correct device unit number.
NOSUCHMOD
module 'module-name' not found in library 'library-name' Facility: LINK, Linker Utility Explanation: A module requested from a library with the /INCLUDE qualifier could not be found. User Action: Correct the command line and relink.
NOSUCHMODU
no such module name 'module-name' Facility: PATCH, Patch Utility Explanation: The specified module name is not contained in the image file. User Action: Retry the operation specifying a module name that is contained in the image file.
NOSUCHNAM
no element with the specified name exists Facility: PPL, Parallel Processing Facility Explanation: The name you input does not specify an existing element. User Action: Recode your program to ensure that the name matches a created element.
NOSUCHNODE
no such node while stopping queue 'queue-name' continuing to stop other queues Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: This error occurred during a $SNDJBC system service call attempting to reset the queue. The specified queue is on a node other than the node on which the upgrade procedure is being executed. User Action: Be aware that queue is in an inconsistent state.
NOSUCHNODE
node 'node-name' not known Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a specified service and node failed because the target node name is unknown. User Action: Retry the connection until the specified node is known or see if a problem with the specified node is preventing its network visibility. Possibly the local node's service group codes do not intersect with the specified remote node's group codes.
NOSUCHNODE
remote node is unknown or not reachable Facility: JBC, Job Controller Explanation: A DCL command such as START/QUEUE was executed, or a call to the $SNDJBC system service was made that requires the job controller on one node of a cluster to communicate with the job controller on another node to perform the requested operation. This condition indicates that the remote job controller could not be reached because an invalid node name was specified, the remote node is not reachable, or the job controller on the remote node is not running. User Action: Check the node name specified and verify that the remote node is currently in the cluster, then retry the operation.
NOSUCHNODE
remote node 'node-name' not known or unavailable. Facility: VMSINSTAL, Install Procedures Explanation: You are trying to install a product on a remote node that is either unknown or unavailable. User Action: Specify an existing node name or try the installation again when the node becomes available.
NOSUCHNODE
specified node does not exist Facility: SYSTEM, VMS System Services Explanation: The node name portion of a file or task specification refers to a node that is unknown to the network ACP. User Action: Check the node name specification. Verify the status of the network and available nodes with the DCL command SHOW NETWORK.
NOSUCHOBJ
network object is unknown at remote node Facility: SYSTEM, VMS System Services Explanation: An attempt is made to initiate a DECnet-VAX logical link connection. The target object of the connect could not be found on the specified node. The object name or object number is unknown, or the command file used to start the object could not be found. User Action: Notify the system manager of the remote node. Refer to the VMS Networking Manual for additional information.
NO_SUCH_PARTY
no such party in this application Facility: PPL, Parallel Processing Facility Explanation: The specified participant does not exist in this application. User Action: Recode your program to ensure that the correct participant is specified in the call to this routine.
NOSUCHQUE
no such queue Facility: JBC, Job Controller Explanation: The specified queue does not exist. In a wildcard $GETQUI operation, no more queues matching the specified selector exist. User Action: None.
NOSUCHRQST
no such request Facility: OPCOM, Operator Communication Process Explanation: A DCL command REPLY specified a nonexistent message identification number. User Action: Verify the message identification number displayed in the message; reenter the command with the correct message number. If the request is canceled by the user who issued it, no action is necessary.
NOSUCHRTN
unknown CLI routine 'routine-name' Facility: CDU, Command Definition Utility Explanation: You specified a routine name instead of an object module in your CLD file when generating CLI tables. User Action: Remove the routine name from the CLD file.
NOSUCHRVN
the /VOLUME = 'number' qualifier is invalid, volume set contains 'number' volumes Facility: BACKUP, Backup Utility Explanation: The value specified for the /VOLUME qualifier is larger than the number of volumes in the volume set. User Action: Reenter the command using a smaller value.
NOSUCHSEC
no such (global) section Facility: SYSTEM, VMS System Services Explanation: The global section name specified in a request to map a global section does not exist. User Action: Check for a programming error. Verify that the program that creates the global section successfully created the section, and that the section has not been deleted. Also, check that the logical name strings specifying the global section name match.
NOSUCHSYM
no such symbol Facility: LIB, Library Facility Explanation: You specified an undefined symbol. User Action: Retry the operation specifying a defined symbol.
NOSUCHSYM
no such symbol Facility: PATCH, Patch Utility Explanation: A symbol is specified that is not contained in the PATCH symbol table. User Action: Use the PATCH Utility command SET MODULE to bring local symbols into the PATCH symbol table.
NOSUCHTID
specified transaction not found Facility: SYSTEM, VMS System Services Explanation: The transaction identifier (TID) specified in the user program was not found. User Action: Check the user program and correct the error.
NOSUCHUSER
login information not recognized at remote node Facility: SYSTEM, VMS System Services Explanation: An attempt is made to initiate a DECnet-VAX logical link connection. The supplied access control string is not recognized at the remote node. In particular, the username, password, or account field is not recognized. User Action: The access control string specified is incorrect. If default access control is specified, notify the system manager that the DECnet configuration database needs to be updated. This error can be returned if the specified access control string is not recognized (for example, no record in the UAF), is too long, or contained illegal characters. Refer to the VMS Networking Manual for additional information.
NOSUCHUSER
user 'username' not currently logged in Facility: SHOW, SHOW Command Explanation: When using the SHOW USER command, you specified a user who is not currently logged in. User Action: None.
NOSUCHUSR
no such user 'username' Facility: MAIL, Mail Utility Explanation: You attempted to send a message to a user that does not exist as an authorized user of the computer system. If you attempted to send the message to mutiple users and at least one is authorized, this message appears for each unauthorized user, followed by the question: "Do you want to send it anyway (Y/N)?" User Action: Reenter the command and specify a valid username. If you are asked if you want to send the message anyway, respond Y (yes) or N (no).
NOSUCHVERB
the CLI table does not contain verb name 'verb-name' Facility: CDU, Command Definition Utility Explanation: The verb you tried to delete is not defined in the current CLI table. User Action: Make sure that the syntax is correct and try to delete the verb again.
NOSUMM
an input file may be specified only when /SUMMARY is present Facility: MONITOR, Monitor Utility Explanation: A list of files is specified on the /INPUT qualifier, indicating a multifile summary request, but the /NOSUMMARY qualifier is also present, explicitly or implicitly. A list of files may be specified only for a multifile summary request. User Action: If a multifile summary is desired, reenter the MONITOR request, specifying the /SUMMARY qualifier. If a multifile summary is not desired, reenter the MONITOR request specifying the /INPUT qualifier with a single file.
NOSYMBOL
symbol 'xxx' is not in the symbol table Facility: PATCH, Patch Utility Explanation: The symbol 'xxx' cannot be located in the utility's symbol table. This can be caused when the module that defines the symbol has not been added to the utility's symbol table, or when a symbol name that is not in the image has been entered. User Action: Add the required module to the utility's symbol table with the SET MODULE command or specify the correct symbol name.
NOSYMBOLS
no 'block-type' symbols found to format this block Facility: SDA, System Dump Analyzer Explanation: SDA cannot locate the symbols needed to format a block as a particular block type. User Action: Use the SDA command READ to include the specific block type symbols in the SDA symbol table.
NOSYMBOLS
no global symbol table found in 'image-name' Facility: LIBRAR, LIBRARY Command Explanation: There is no symbol table in the shareable image. User Action: The linker always produces a symbol table, even if it is empty. If this error persists after relinking, submit a Software Performance Report with the relevant files.
NOSYSACT
no action on .SYS files Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not perform the requested action on files with the file type SYS. User Action: Normally no action is required, since SYS files get special treatment. If it is desired to modify SYS files, reenter the command with the /SYSTEM qualifier.
NOSYSCLF
no common logging structures Facility: SDA, System Dump Analyzer Explanation: There are no transaction logs currently open on this node. User Action: None.
NOSYSDISK
no access to system disk Facility: BACKUP, Backup Utility Explanation: The system disk is not accessible. User Action: Determine why the system disk is inaccessible. If possible, make the system disk operational and retry the BACKUP command.
NOSYSGBL
operation requires SYSGBL privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires SYSGBL privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOSYSIPC
no IPC structures Facility: SDA, System Dump Analyzer Explanation: There is no IPC activity currently on this node. User Action: None.
NOSYSLCK
operation requires SYSLCK privilege Facility: SYSTEM, VMS System Services Explanation: You tried to lock a systemwide resource when you did not have SYSLCK privilege. User Action: Ask the system manager for SYSLCK privilege; or remove the LCK$M_SYSTEM flag.
NOSYSNAM
operation requires SYSNAM privilege Facility: SYSTEM, VMS System Services and JBC, Job Controller Explanation: A command or program requested a system function that requires SYSNAM privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOSYSPRV
operation requires SYSPRV privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires SYSPRV privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privilege function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOSYSTPS
no transaction structures Facility: SDA, System Dump Analyzer Explanation: There are no active transactions currently on this node. User Action: None. Not enough SPTEs to take selective system dump - switching to complete memory dump Facility: BUGCHECK, System Bugcheck Explanation: When writing a selective dump (SYSGEN parameter DUMPSTYLE set to 1), the VMS operating system needs to remap portions of memory for easy access and for efficient writing of the dump file. The VMS operating system requests 127 System Page Table Entries (SPTEs) during the bootstrap sequence so that the SPTEs are ready when needed. If the system is configured so that there are not sufficient SPTEs to create a selective dump, the system attempts to write a complete dump. User Action: When the system comes back up, run AUTOGEN and reboot with a larger SYSGEN parameter SPTREQ.
NOT1STVOL
'save-set-spec' is not the start of a save set Facility: BACKUP, Backup Utility Explanation: The volume mounted as the first volume of the specified save set is a continuation volume. This is valid if the operation is not a restore with the /IMAGE qualifier. User Action: Reevaluate the operation to ensure that the correct results are obtained.
NOT1STVOL
tape 'tape-name' is not the start of a save set Facility: BACKUP, Backup Utility Explanation: A restore or compare operation did not begin with the first volume in the save set. User Action: None. The Backup Utility allows you to begin restore and compare operations without mounting the first volume.
NOTACLU
'device-name' is not a cluster-wide device Facility: MOUNT, Mount Utility Explanation: An attempt was made to mount a device on all nodes in the cluster by specifying the /CLUSTER qualifier, however, the device specified is not available, nor can it be made available, cluster-wide. User Action: Reenter the command without the /CLUSTER qualifier.
NOTALLPRIV
not all requested privileges authorized Facility: SYSTEM, VMS System Services Explanation: You requested unauthorized privileges from $SETPRV. Only authorized privileges will be granted. User Action: If necessary, ask the system manager to grant you the appropriate privileges.
NOTALLREQUE
all jobs in source queue could not be requeued to target queue Facility: JBC, Job Controller Explanation: Some of the jobs specified in an ASSIGN/MERGE command were not suitable for execution on the specified target queue. User Action: Enter a SET ENTRY/REQUEUE=queue-name command to requeue the jobs remaining in the source queue to a queue that has the necessary settings to execute those jobs.
NOTALLSYM
unable to initialize symbols for default modules Facility: PATCH, Patch Utility Explanation: The PATCH symbol table did not have enough room to include symbols for all the modules normally inserted into the table upon execution of PATCH. User Action: To make room for the new modules, enter the PATCH command SHOW MODULE to determine which modules are in the symbol table, then enter the PATCH command CANCEL MODULE specifying the module names whose symbols are no longer required. Then reenter the PATCH command SET MODULE.
NOTANSI
not ANSI volume on 'device-name' Facility: MOUNT, Mount Utility Explanation: The volume on the specified device is not an ANSI- formatted magnetic tape. User Action: Initialize the tape and reenter the mount request or mount the tape foreign.
NOTANSI
tape is not valid ANSI format Facility: BACKUP, Backup Utility Explanation: The volume does not have ANSI standard labels. User Action: Locate and mount the correct volume.
NOTAPEOP
no tape operator Facility: SYSTEM, VMS System Services Explanation: An operation failed because no system operator is available to satisfy a requirement for manual assistance; for example, to mount the next volume in a multivolume tape file. User Action: Ensure that the tapes were mounted on the original mount request or run the job when an operator is present.
NOTARRAY
indexed variable is not an array Facility: VAXTPU, VAX Text Processing Utility Explanation: The variable being indexed is not an array. User Action: Use indexing with array variables only.
NOTASCII
parameter 'name' is not ASCII type Facility: SYSBOOT, System Bootstrap Facility and SYSGEN, System Generation Utility Explanation: An ASCII value is specified in a SET command for a non-ASCII parameter. User Action: Reenter the command specifying a correct parameter value.
NOTASSIGN
queue not assigned Facility: JBC, Job Controller Explanation: The specified queue cannot be deassigned because it is not assigned. User Action: None.
NOTATERM
command device is not a terminal Facility: LAT, LAT Facility Explanation: You attempted to use SET HOST/LAT from a device that is not a terminal. User Action: Use SET HOST/LAT from a terminal device only.
NOT_A_TERM
pasteboard attached to a device that is not a terminal Facility: SMG, Screen Management Facility Explanation: This informational message indicates that the pasteboard has been created, but that the output device is not a terminal. User Action: None.
NOT_A_TRM
device is not a terminal Facility: DTK, DECtalk Facility Explanation: This informational message indicates that the output device is not a terminal. User Action: None.
NOT_AVAILABLE
requested resource not available now Facility: PPL, Parallel Processing Facility Explanation: Success status returned when the user requests immediate nonblocking access to a resource that is not available. User Action: Continue normally.
NOTBKBLOCK
invalid subsystem code in save set Facility: BACKUP, Backup Utility Explanation: An incorrect value occurred in the subsystem code field of a save set block. Data in the save set is corrupted. The save set data is lost. User Action: None.
NOTBOOCAP
not a Boolean capability Facility: SMG, Screen Management Facility Explanation: The Termtable compiler expected a Boolean capability name but encountered something else. User Action: Check your terminal definiton. Perhaps you misspelled the Boolean capability name or omitted another statement such as STRING or NUMERIC which would have terminated Boolean capabilities.
NOTCLASS
'device-name' not a 'type' device, type is 'type' Facility: SHOW, SHOW Command Explanation: The specified device is not the type of device that you specified in the command line. User Action: None.
NOTCMASTACK
the current stack was not allocated by DECthreads Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The program attempted to call a DECthreads routine while the thread stack pointer register held an address in a stack that was not allocated by DECthreads. Because DECthreads uses the value in the thread stack pointer register to determine which thread is currently running, all calls to DECthreads routines must be performed on a stack that was allocated by DECthreads. User Action: Modify the program so that it does not switch stacks, or call DECthreads to create an additional stack and assign it to the thread.
NOTCMPLT
'input-filespec' not completely copied Facility: Shared by several facilities Explanation: A copy operation began but did not finish. This message is accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the accompanying message. Use the DCL command TYPE or DUMP to verify the contents of the output file, and delete the output file before reentering the command.
NOTCOM
BATCH mode can only be used for .COM files Facility: STDRV, System Startup Driver Explanation: An entry in the STARTUP component file specifies a component file to be run with the BATCH command whose file type is not COM. User Action: Use the STARTUP MODIFY FILE command at the SYSMAN> prompt to correct either the file name or the execution mode.
NOTCOPIED
'input-filespec' not copied Facility: Shared by several facilities Explanation: A requested input file could not be copied. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the accompanying message.
NOTCOPIED
file 'filename' not copied to 'filespec' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not copy a file. User Action: This message will be followed by a message describing the actual reason the copy could not be done. Take corrective action based on the following message.
NOTCOP_RETRY
error copying 'filename', will retry Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while copying the file, but after taking corrective action EXCHANGE will retry the copy. User Action: This is most likely due to EXCHANGE discovering a bad block on a volume, and EXCHANGE will try again to copy the file to a good space on the volume.
NOTCREATOR
request denied, user is not on creator port Facility: SYSTEM, VMS System Services Explanation: A shared memory global section may be deleted or updated only by a process running on the same processor as the creator of the section. If the processor becomes inoperative, no one owns the section. User Action: Enter the request from the creator's processor. After a processor becomes inoperative, it will be necessary to reboot and reinitialize the shared memory in order to delete those sections without owners.
NOTCTX
symbol specified is not a valid context symbol Facility: CLI, Command Language Interpreter (DCL) Explanation: You are trying to use a symbol that has a type other than a context type such as PROCESS_CONTEXT. User Action: Refer to the documentation of the lexical function you are trying to use for more information.
NOTDDBDDB
corrupted DDB list Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTDECSTRG
illegal character in decimal string Facility: MACRO, VAX MACRO Assembler Explanation: A decimal string contained a character other than the digits 0 through 9 and a leading plus or minus sign. User Action: Correct the syntax of the decimal string.
NOTDEFINABLE
that key is not definable Facility: VAXTPU, VAX Text Processing Utility Explanation: The key that you tried to define using the built-in procedure DEFINE_KEY is not a definable key. User Action: Use a definable key as outlined in the description of the DEFINE_KEY built-in procedure in the VAX Text Processing Utility Manual.
NOTDELETED
file 'filename' not deleted Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility did not delete the specified file. User Action: This message will be followed by another message giving the reason why the file could not be deleted. Take corrective action based on the second message.
NOTDELETED
purging a record not marked as deleted Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
NOTDIR
file is not a directory Facility: SET, SET Facility Explanation: The specified file is not a directory file. User Action: Reenter specifying an existing directory file.
NOTDISCON
terminal is not disconnectable - explicitly specify LOGOUT Facility: CLI, Command Language Interpreter (DCL) Explanation: An attempt has been made to disconnect a terminal that has not been set as disconnectable from the current process. A disconnect under these circumstances would log out the user and, therefore, is not permitted. User Action: Either explicitly log out or set the terminal as disconnectable by using the SET TERMINAL/PERMANENT/DISCONNECT command and try again.
NOTDISK
device must be a Files-11 format disk Facility: SET, SET Facility Explanation: The operation that you are trying to perform requires a Files-11 format disk. The device that is specified does not meet these requirements. For example, this message is produced when you enter the SET VOLUME command to a tape or terminal. The SET VOLUME command only accepts Files-11 devices. User Action: Make sure that the device meets the requirements of a Files-11 format disk before performing the operation.
NOTDISM
unable to dismount 'device-id' Facility: BACKUP, Backup Utility Explanation: The Backup Utility cannot dismount a tape drive specified by the command line qualifier /RELEASE_TAPE. User Action: An accompanying message indicates the type of user action required, if any.
NOTDONE
'feature-name' not yet a supported feature Facility: PATCH, Patch Utility Explanation: The feature you attempted to use is recognized but not implemented by PATCH. The name of the feature is indicated in the error message. User Action: None.
NOTDONE
command not complete Facility: NCP, Network Control Program Explanation: Not enough command information has been supplied to determine the intent of the command. Prompting does not occur because the command is included in a command procedure. User Action: Modify the command in the command procedure to make it a valid command.
NOTENABOPT
not a legal ENABLE option Facility: MACRO, VAX MACRO Assembler Explanation: An argument to an .ENABLE or .DISABLE directive is not a legal option. User Action: Delete the option or replace it with a legal option.
NOTENUFOPR
not enough operands supplied Facility: MACRO, VAX MACRO Assembler Explanation: The instruction requires more operands than were specified in the statement. User Action: Either add the operands or change the instruction.
NOTERM
command device is not a terminal Facility: REM, Set Host Facility Explanation: SET HOST is invoked from a batch job. (SYS$COMMAND is not a terminal.) You can invoke SET HOST only from interactive terminal sessions. User Action: None.
NOTERRORKEYWORD
error handler selector is not an error keyword Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified error handler selector is not an error keyword. User Action: Specify only error keywords as error selectors.
NOTEXIST
folder 'folder-name' does not exist Facility: MAIL, Mail Utility Explanation: The command cannot be executed because it specifies a folder that does not exist. User Action: Use the MAIL command DIRECTORY/FOLDER to display a list of existing folders. Then retry the command using an existing folder name.
NOTFCBFCB
FCB linkage broken Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTFCBWCB
Bad FCB pointer in window Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTFCPWCB
Not FCP window in IRP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTFILEDEV
device is not file structured Facility: Shared by several facilities Explanation: A file specification containing a directory, or file name and/or file type is used for an I/O operation for a device that does not support random access, for example, a line printer. User Action: Verify the device name and the file specification; if a logical name is specified, ensure that the correct equivalence name is assigned. Correct the source program or reenter the command, as applicable.
NOTFOU
not found Facility: LIB, Library Facility Explanation: LIB$FIND_VM_ZONE could not locate another VM zone. This message is a success status. User Action: None.
NOTFOUND
no messages containing 'text' found Facility: MAIL, Mail Utility Explanation: You entered a DCL command SEARCH specifying text to be found in a message. This text is not found. User Action: Attempt to search for different text.
NOTFOUND
specified entry not found Facility: ERF, Error Log Utility Explanation: No entries matching the specified selection criteria were found. User Action: None.
NOTFR
no transfer address Facility: CLI, Command Language Interpreter (DCL) Explanation: The image file does not have a transfer address. User Action: Check that the source program has specified a transfer address and, if necessary, reassemble and relink the program.
NOTGENDEV
not a generic device Facility: MOUNT, Mount Utility Explanation: You specified an invalid generic device. User Action: Retry the operation specifying a valid generic device.
NOTHEN
IF or ON statement syntax error - check placement of THEN keyword Facility: CLI, Command Language Interpreter (DCL) Explanation: The syntax of an IF or an ON statement is incorrect. User Action: Correct the syntax of the statement by including the THEN statement in the proper place.
NOTHLPLIB
not a HELP library Facility: LBR, Librarian Subroutine Package Explanation: The library specified in LBR$GET_HELP is not a help library. User Action: Determine that the library is a help library before calling the routine; specify the correct library name.
NOTIDFMT
ID name parameter does not translate to ID format Facility: AUTHORIZE, Authorize Utility Explanation: The identifier name that you specified does not translate to a corresponding value in general identifier format. Identifier name values translate to either general identifier format or UIC format. General identifier names may be 1 through 31 alphanumeric characters and are stored with an integer value in the range of 32,768 to 268,435,455. General identifiers are created by the AUTHORIZE command ADD/IDENTIFIER. When you use the AUTHORIZE command GRANT/IDENTIFIER, the first identifier you specify must be in general identifier format. In other words, you cannot grant a UIC-format identifier to another UIC-format identifier. User Action: Determine why the identifier name is not a general ID. You can display an identifier name and its corresponding value with the AUTHORIZE command SHOW/IDENTIFIER. To change the value of an identifier name, use the AUTHORIZE command MODIFY/IDENTIFIER.
NOTIDX
output file is not an indexed file Facility: CONVERT, Convert Utility and CONVERT, Convert/Reclaim Utility Explanation: You specified the /MERGE qualifier and the output file is not an indexed file. User Action: Specify /NOMERGE and try again.
NOTIFY
the /NOTIFY qualifier is not allowed - do not use with /WAIT or in batch jobs Facility: CLI, Command Language Interpreter (DCL) Explanation: /NOTIFY should only be used when you specify the /WAIT qualifier and when the SPAWN command is executed from within a noninteractive process. User Action: Do not use /NOTIFY.
NOTIMGLIB
file 'filename' is not a shareable image symbol table library Facility: LINK, Linker Utility Explanation: The system library IMAGELIB is found, but is not a shareable image library. User Action: Correct the file name and relink.
NOTIMP
not implemented Facility: Shared by several facilities Explanation: You tried to use a call, routine, or feature that is not implemented in this version. User Action: Use a higher version of the routine or feature, or code your program to eliminate this call.
NOT_IMPL
function not implemented for this object Facility: SMI, System Management Integrator/Server Explanation: Internal error. The function you requested of an SMI object is not defined. User Action: Submit a Software Performance Report showing the exact sequence of SYSMAN commands leading to the error.
NOTIMPLEMENTED
built-in compiled by 'name' is not implemented by 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The section file contains a reference to a built-in procedure implemented in another version of VAXTPU, but which is not implemented in this version of VAXTPU. User Action: You must use the version of VAXTPU that compiled the section file.
NOTIMPOPCODE
opcode in delayed work queue not implemented Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
NOTINANIF
statement outside condition body Facility: MACRO, VAX MACRO Assembler Explanation: A .IF_FALSE, .IF_TRUE, .IF_TRUE_FALSE, .IFF, .IFT, or .IFTF subconditional directive is not in a conditional assembly block. User Action: Replace the subconditional directive with a conditional directive or delete the subconditional directive.
NOTINMACRO
statement not in MACRO body Facility: MACRO, VAX MACRO Assembler Explanation: A .NARG, .ENDM, or .ENDR directive is used outside the context of a macro. User Action: Correct the code.
NOTINPHYS
'location' not in physical memory Facility: SDA, System Dump Analyzer Explanation: The memory location you requested as a parameter to the SDA command EXAMINE is not in physical memory when the system failed. User Action: Reenter the command, specifying another address.
NOTINSTALL
writeable shareable images must be installed Facility: SYSTEM, VMS System Services Explanation: Writable shareable images must be installed. User Action: Install the shareable image specifying /SHARE/WRITE.
NOTINTBLSZ
block size is greater than 2048 Facility: SYSTEM, VMS System Services Explanation: Your block size is greater than 2048 bytes (the default). User Action: For a block size greater than 2048 bytes, you must specify the number of blocks required with the /BLOCK qualifier as shown below: MOUNT/BLOCK=n
NOTIRPAQB
Not IRP pointer in AQB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTJOURNAL
'filespec' is not a BACKUP journal Facility: BACKUP, Backup Utility Explanation: The specified file does not have the appropriate file attributes. It is not a Backup Utility journal file. User Action: Locate the correct file and reenter the command.
NOTLABEL
'volume-label' not on 'device-name' Facility: MOUNT, Mount Utility Explanation: The operator responded to a message from the magnetic tape ACP with a successful completion, but the volume is not correct. The volume label specified by the original DCL command MOUNT, or the reply to an operator mount request, does not match the volume label on the specified device. User Action: Include the correct label in the next reply to an operator mount request or mount the correct volume on the device. If you do not want to check the label, use the OVERRIDE:ID qualifier in the original DCL command MOUNT. Verify that the device is on line.
NOTLABELMT
tape is not labeled Facility: SYSTEM, VMS System Services Explanation: A request to read a tape failed because the tape does not have standard labels. User Action: Verify the tape volume. Mount the tape as a foreign tape, if necessary, to read it. If the tape is to be rewritten, initialize it before retrying the program.
NOTLEARNING
you have not begun a learn sequence Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure LEARN_END executed without the built-in procedure LEARN_BEGIN preceding it. User Action: You must start a learn sequence before you can save keystrokes.
NOTLGLISOP
not a legal listing option Facility: MACRO, VAX MACRO Assembler Explanation: The argument to a .SHOW, .NOSHOW, .LIST, or .NLIST directive is not a legal option. User Action: Delete the illegal option or replace it with a legal option.
NOTLKB
Structure is not an LKB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTLOADED
LAT terminal port driver (LTDRIVER) is not loaded Facility: LAT, LAT Facility Explanation: You attempted to execute LATACP when LTDRIVER was not loaded. User Action: Check to see whether the LAT software is properly configured.
NOTLOCKED
'filename' not locked Facility: SET, SET Facility Explanation: The file that you want to lock is already locked. User Action: None.
NOTLOCKED
'filespec' was not locked Facility: Shared by several facilities Explanation: The file specified by a DCL command UNLOCK is not locked. This message is informational. User Action: None.
NOTMEANINGFUL
specified item code is no longer meaningful Facility: JBC, Job Controller Explanation: The specified item code once affected the results of the command, but it no longer does so. User Action: Discontinue using this item code with this command.
NOTMOD
volume 'volume-name' not modified Facility: SET, SET Facility Explanation: The volume is not modified. This message is accompanied by another message. User Action: Take corrective action based on the accompanying message.
NOTMODEM
VAX/VMS host system modem not wired correctly - contact your system
manager
Facility: LOGIN, Login Processor
Explanation: The terminal line is set to /MODEM and TTDRIVER did
not detect all the necessary modem signals within 30 seconds of a
login attempt.
User Action: For information on how the TTDRIVER identifies
a valid modem line, refer to the section on modem control of
terminal drivers in the VMS I/O User's Reference Manual: Part
I. Make sure that the following conditions are met:
o The modem cable connecting the modem provides the correct
signal.
o The terminal port supports modem use.
o The modem provides the correct signals in the correct order.
NOTMODIFIABLE
attempt to change unmodifiable buffer 'string' Facility: VAXTPU, VAX Text Processing Utility Explanation: You cannot change the specified buffer. User Action: Use the SET (MODIFIABLE, . . . ) built-in to allow modifications.
NOTMODIFIED
no pages in the section were modified Facility: SYSTEM, VMS System Services Explanation: The update request completed successfully without queueing any I/O requests because no pages in the input address range had been modified. User Action: The operating system does not normally display this message; the user program should be able to detect and respond to the condition.
NOTMOUNTED
volume 'volume-name' has not been mounted on EXCHANGE Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received a DISMOUNT command for a volume which is not mounted. User Action: Check the command for a misspelled device name.
NOTMPMBX
operation requires TMPMBX privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires TMPMBX privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOTMTLMTL
Corrupted mounted volume list Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTNEG
qualifier or keyword not negatable - remove "NO" or omit Facility: CLI, Command Language Interpreter (DCL) Explanation: The word "NO" preceded a qualifier or keyword, but the qualifier or keyword cannot be specified as a negative. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for a list of negatable qualifiers and keywords.
NOTNETDEV
not a network communication device Facility: SYSTEM, VMS System Services Explanation: The device specified is not a network communications device, and the control function cannot be performed. User Action: Check for a programming error. Verify that the device specified in the queue I/O request is a valid communications device.
NOTNUMBER
parameter 'name' is not numeric type Facility: SYSBOOT, System Bootstrap Facility and SYSGEN, System Generation Utility Explanation: A numeric value is specified in a SET command for a non-numeric parameter. User Action: Reenter the command specifying a correct parameter value.
NOTNUMCAP
not a numeric capability Facility: SMG, Screen Management Facility Explanation: The Termtable compiler expected a numeric capability name but encountered something else. User Action: Check your terminal definition. Perhaps you have misspelled the numeric capability name or omitted another statement, such as STRING or BOOLEAN which would have terminated numeric capabilities.
NOTOBJLIB
file 'filename' is not an object library Facility: LINK, Linker Utility Explanation: The specified file is not an object library. The linker processes only object and shareable image libraries. User Action: Specify only object or shareable image libraries.
NOTOBJLIB
library 'library-name' is not an object library Facility: LIBRAR, LIBRARY Command Explanation: An attempt is made to cross-reference a library or to use the /REMOVE qualifier in a macro, help, or text library. User Action: Reenter the command line, specifying an object library that contains the requested symbol.
NOTODS2
'qualifier' qualifier invalid on Files-11 Structure Level 1 disk Facility: SET, SET Facility Explanation: The specified qualifier is not valid for a Files-11 Structure Level 1 volume, file, or directory. User Action: Reenter the command specifying a valid qualifier.
NOTOFFERED
service not offered by requested node Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a specified service for a specified node failed because the node does not offer the selected service. User Action: Retry the connection and specify a node that offers the desired service.
NOTONSCREEN
text cannot be scrolled unless window is on screen Facility: VAXTPU, VAX Text Processing Utility Explanation: You are trying to use the built-in procedure SCROLL on a window that is either not mapped to the screen, or is totally occluded by other windows. User Action: Map the window to the screen before using the built- in procedure SCROLL.
NOTPARAM
not a parameter file Facility: SYSGEN, System Generation Utility Explanation: The file specified in the SYSGEN command USE is not a valid parameter file. User Action: Use a valid parameter file that is either provided by VMS or created by the SYSGEN command WRITE in SYSGEN.
NOTPASTED
given display is not pasted to given pasteboard Facility: SMG, Screen Management Facility Explanation: An attempt is made to unpaste or move a display that is not pasted to the specified pasteboard. User Action: Check that you are referencing the correct virtual display. Verify that the display has not been unpasted or that you forgot to paste it.
NOTPATADR
patch address is 'addr1' not 'addr2' Facility: PATCH, Patch Utility Explanation: You typed the incorrect starting address of the patch area. User Action: To determine the correct starting address, enter either the PATCH command SHOW PATCH_AREA or the PATCH command ALIGN/BYTE. When you enter the PATCH command ALIGN/BYTE, PATCH defines a symbol as the current starting address.
NOTPCB
Structure not PCB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTPRINTED
failed to queue spool file for print Facility: SYSTEM, VMS System Services Explanation: An error occurred while an implicitly spooled file is queued for print. The file has not been printed and the data is lost. User Action: The system manager should ensure that the job controller works correctly and that the printer or terminal is spooled to the correct queue.
NOTPSECOPT
not a valid PSECT option Facility: MACRO, VAX MACRO Assembler Explanation: The attribute specified in the .PSECT directive is invalid. User Action: Delete the invalid attribute or replace it with a valid one.
NOTPSECT
relocation base set to other than psect base in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An object module specified other than a psect base in a set relocation base command. User Action: Submit a Software Performance Report (SPR). Include the appropriate language compiler in the Report (SPR).
NOTPSHARE
shareable image for DECdtm Services SDA support unavailable Facility: SDA, System Dump Analyzer Explanation: The shareable image for DECdtm services is not installed on this node. User Action: Ensure that shareable image SYS$SHARE:SDATP$SHARE.EXE is installed before executing any SDA commands.
NOTQUEUED
request not queued Facility: SYSTEM, VMS System Services Explanation: The $ENQ system services request, specifying the flag bit LCK$M_NOQUEUE, could not be granted. User Action: Wait and retry the operation.
NOTQUO
unquoted argument not allowed in ASCII or INSTRUCTION modes Facility: PATCH, Patch Utility Explanation: While in ASCII or INSTRUCTION mode, you entered an argument not enclosed within matching apostrophes or quotation marks. User Action: Add matching apostrophes or quotation marks to your argument and reenter.
NOTRAN
logical name cannot be translated Facility: INIT, INITIALIZE Command and MOUNT, Mount Utility Explanation: The DCL command MOUNT or INITIALIZE attempted logical name translation on a device name or logical name and failed to translate the logical name. This error is most likely to occur when logical names are nested too deeply or if a logical name is assigned to itself. User Action: Use the DCL command SHOW LOGICAL to verify the translation of the device name or logical name. If necessary, reassign the logical name before reentering the DCL command MOUNT or INITIALIZE.
NOTRAN
no string translation performed Facility: SYSTEM, VMS System Services Explanation: A request to translate a logical name returned with no translation performed. The system returns the input logical name string as the equivalence name string. (Because this is a success message, it is not normally displayed.) User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
NOTRAN
no translation for logical name 'name' Facility: SHOW, SHOW Command Explanation: There is no translation for the specified logical name. User Action: None.
NOTREADIN
you are not reading a message Facility: MAIL, Mail Utility Explanation: The MAIL command you typed (DELETE, FILE, FORWARD, PRINT, or REPLY) is appropriate only when you are reading a message. User Action: Read the desired message using the MAIL command READ and then enter the appropriate command in response to the MAIL> prompt.
NOTRELVOL
relative volume 'nnn' not on device Facility: MOUNT, Mount Utility Explanation: Each volume in a volume set has a relative number beginning with one. The volume mounted on the device is not the relative volume requested in the previous mount request. User Action: Mount the correct volume on the device, or abort the mount request if you do not have the correct volume.
NOTRENAMED
'filename' not renamed Facility: RENAME, RENAME Command Explanation: The specified file is not renamed. User Action: Correct the error according to the accompanying message.
NOTRES
process swapped out Facility: SDA, System Dump Analyzer Explanation: This message occurs if the process name specified in a SHOW PROCESS or SET PROCESS command represents a process that is swapped out of the balance set when the system failed. User Action: None.
NOTRMSOUT
RMS is not being used to perform output Facility: SMG, Screen Management Facility Explanation: SMG$SNAPSHOT is used with files and unknown devices to capture the contents of the pasteboard at various times. If SMG$SNAPSHOT is called for a pasteboard associated with a video terminal, then it takes no action and returns this informational message. User Action: None.
NOTRULUCB
Bad RUL pointer in UCB (journaling) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTRVTVCB
Not RVT pointer in VCB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTSAMEBUF
the markers are not in the same buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: You passed markers to the built-in procedure CREATE_ RANGE that are not in the same buffer. A range cannot span buffers. User Action: Create the range with markers in the same buffer.
NOTSAMEDEV
cannot RENAME to a different device Facility: RENAME, RENAME Command Explanation: An attempt is made to rename a file name from one device to another. User Action: Use the DCL command COPY instead of the DCL command RENAME.
NOTSAMEDEV
input and output must be same device for boot copy Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an attempt to COPY /BOOT between devices. User Action: Reenter the command, specifying the same device for input and output. You can also omit the name of the output device, since EXCHANGE will assume you mean the same as the input device.
NOTSAVED
'LMB-name' not saved in the dump file Facility: SDA, System Dump Analyzer Explanation: Information corresponding to a Logical Memory Block (LMB) has not been saved in this subsetted dump file. The dump file may or may not be useful for analysis depending on which LMB was not saved. If the SDA image retains control after the error, then some analysis is possible, but some information might not be available in the dump file. User Action: None. The dump file may not be useful for analysis.
NOTSAVESET
'save set spec' is not a BACKUP save set Facility: BACKUP, Backup Utility Explanation: The specified file does not have the appropriate file attributes. It is not a save set. User Action: Locate the correct file and reenter the command.
NOTSEQ
output file is not a sequential file Facility: CONVERT, Convert Utility Explanation: You specified the /APPEND qualifier and the output file is not sequential. User Action: Specify /NOAPPEND and try again.
NOTSET
process not set to /CPU=[NO]ATTACHED Facility: Shared by several facilities Explanation: The process is already in the requested state. User Action: None.
NOTSHDWDEV
not a shadowing device Facility: MOUNT, Mount Utility Explanation: There are two possible causes for this error message: (1) The form DSA was not used to specify the virtual unit name in the mount command, causing the mount command to fail, or (2) An attempt was made to mount a volume that does not support volume shadowing in a shadow set (for example, a magnetic tape cannot become a shadow set member). User Action: Correct the command syntax and enter the command again.
NOTSHRIMG
file 'filename' is not a shareable image Facility: LIBRAR, LIBRARY Command Explanation: The file given as input to a shareable image library is not a shareable image. User Action: Relink the image using the LINK/SHARE option.
NOTSPLADDR
memory at 'address' does not begin a spin lock structure Facility: SDA, System Dump Analyzer Explanation: The memory at the specified address to the SDA command SHOW spin locks does not contain the type field corresponding to a spin lock structure. User Action: Reenter the command; specify a different address.
NOTSQDEV
not a sequential device Facility: SYSTEM, VMS System Services Explanation: You tried sequential access with a random access device. User Action: Use random access with this device.
NOTSTRCAP
not a string capability Facility: SMG, Screen Management Facility Explanation: The Termtable compiler expected a string capability name but encountered something else. User Action: Check your terminal definition. Perhaps, you have misspelled the string capability name or omitted another statement such as BOOLEAN or NUMERIC which would have terminated string capabilities.
NOTSTRUCT1
qualifiers not available with structure level 1 Facility: INIT, INITIALIZE Command Explanation: This message is generated by the DCL command INITIALIZE. Qualifiers were used requesting features not available with Files-11 Structure Level 1, for example, /CLUSTER and /DATACHECK. User Action: Use structure level 2 or omit the qualifiers.
NOTSUPPORTED
specified item code or function code is not supported Facility: JBC, Job Controller Explanation: You attempted to use a new feature on a node that has not been upgraded. User Action: Upgrade the node before attempting to specify the new item code or function code.
NOTSYSTEM
you are not logged in to the SYSTEM account. Facility: VMSINSTAL, Install Procedures Explanation: When VMSINSTAL begins an installation, it makes sure that you are logged in to the SYSTEM account. This check has failed. User Action: You will be asked if you want to continue the installation. Digital recommends that you correct this situation before continuing.
NOTUCBIRP
not UCB pointer in IRP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTUCBRVT
not UCB pointer in RVT Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTUCBUCB
corrupted UCB list Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTUCBWCB
bad UCB pointer in window Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTUICFMT
user id parameter does not translate to UIC format Facility: AUTHORIZE, Authorize Utility Explanation: The user specification in your command does not translate to a UIC identifier (an identifier in UIC format). User Action: Determine why the user specification is not a UIC- format ID. You can display user names and their corresponding UIC values by using the AUTHORIZE command SHOW.
NOTUQPORT
device not connected to a UNIBUS/Q-bus port Facility: SET, SET Facility Explanation: You entered the DCL command SET DEVICE/DFAG for a device other than a UDA50 controlled disk, a RC25, or a TU81. This command is valid only for these devices. User Action: Check the device number. Make sure it is one of the devices listed above.
NOT_USABLE
this log will not be used as it is currently named Facility: LMCP, Log Manager Control Program Explanation: A log file that has not been created in directory SYS$JOURNAL or is not named SYSTEM$node-name cannot be used as a log file. User Action: Consult your system manager about naming and locating log files.
NOTVALID
information not in physical memory Facility: SDA, System Dump Analyzer Explanation: The virtual address you specified is not currently in physical memory or is not in physical memory at the time of the dump. You are not able to examine the address. User Action: None.
NOTVALLEN
fixed record length of 'numeric-string' is too large Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility discovered a value on a /RECORD_ FORMAT=(FIXED=n) command which is too large. User Action: Reenter the command with a smaller record length.
NOTVCBUCB
not VCB pointer in UCB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTVOLSET
volume is not part of a volume set Facility: SYSTEM, VMS System Services Explanation: An attempt is made to reference a specific volume in a volume set, through the file ID or placement control, when the specified volume is not part of a volume set. User Action: Verify that the correct device name is specified or remove the volume-specific reference.
NOTVOLSET
volume on 'device-name' not in volume set 'volume-label' Facility: MOUNT, Mount Utility Explanation: The file set identifier of the first file in a volume set identifies the volume set. The volume mounted on the device is not part of the specified volume set. User Action: Mount the correct volume on the device, or abort the mount request if you do not have the correct volume.
NOTVVPVCB
not volume virtual page pointer in VCB Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTWCBIRP
not WCB Pointer in IRP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTWCBWCB
corrupted WCB list Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOTWITHCONN
parameter cannot be modified with connections active or pending Facility: LAT, LAT Facility Explanation: An attempt to modify a LAT parameter failed because that parameter cannot be modified while active connections exist or while a connection request is pending. For a list of parameters that cannot be changed with connections active or pending, refer to the VMS LAT Control Program (LATCP) Manual. User Action: Wait until there are no outstanding connection requests before modifying the parameter.
NOTYET
not yet implemented Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in being used has not yet been implemented. User Action: You must use a different built-in that has been implemented.
NOUNLOAD
driver is not unloadable Facility: SYSGEN, System Generation Utility Explanation: Either an attempt is made to reload a driver that is marked unloadable (DPT$M_NOUNLOAD) in the driver prologue table, or the unload routine of the driver indicates that the driver should not be unloaded. User Action: None.
NOUPDATE
no patch for update qualifier ECO level 'nn' Facility: PATCH, Patch Utility Explanation: When a command procedure is submitted for interactive or batch execution (by typing PATCH/UPDATE = (eco-level, . . . )), an ECO level is specified that is not included in the command procedure. User Action: Check your command procedure for correct ECO levels and retry.
NOUSERNAME
missing user name Facility: AUTHORIZE, Authorize Utility Explanation: The command you are using requires a user name. A user name is the member name from the alphanumeric form of a user's UIC (user identification code). User Action: Reenter your command including a user name.
NOUSERNAME
username must be supplied Facility: MOM, Maintenance Operation Module Explanation: In this LOOP NODE or LOOP EXECUTOR command, a user name must be supplied. User Action: Supply a user name with the LOOP command.
NOUSERPASS
username and password must be supplied Facility: MOM, Maintenance Operation Module Explanation: In this LOOP NODE or LOOP EXECUTOR command, both a user name and a password must be supplied. User Action: Supply a user name and a password with the LOOP command.
NOUSERSPEC
missing user specification Facility: AUTHORIZE, Authorize Utility Explanation: The command you are using requires a user specification. A user specification may be a user name (for example, CAESAR), or a user identification code (for example, [100,44]). User Action: Reenter your command including a user specification.
NOUSRWCS
no user WCS halt restart Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
NOVALPRS
$SEARCH operation not preceded by valid $PARSE Facility: RMS, VMS Record Management Services Explanation: A VMS RMS wildcard $SEARCH operation was attempted with no preceding valid $PARSE operation. User Action: Verify that the sequence of VMS RMS service calls is coded correctly and that the NAM block is not inadvertently modified during execution of the program.
NOVALU
value not allowed - remove value specification Facility: CLI, Command Language Interpreter (DCL) Explanation: A qualifier or keyword that does not accept a value is specified with a value. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for the correct syntax and reenter the command.
NOVALUE
'keyword' keyword requires a value Facility: Shared by several facilities Explanation: The keyword indicated must be specified with a value. User Action: Reenter the command; specify a value for the indicated keyword.
NOVALUE
qualifier 'qualifier' requires value Facility: BACKUP, Backup Utility Explanation: No value was given for the specified qualifier. User Action: Specify a value for the qualifier and reenter the BACKUP command.
NOVECTOR
no vector processor(s) available to test Facility: UETP, User Environment Test Package Explanation: The vector processor device test failed to detect any presence of vector processors or the vector emulator facility installed on the host system. Either a VAX vector processor(s) or vector emulator facility has not been properly installed or is not available. User Action: Refer to the vector emulator facility installation reference manual, or run diagnostics for VAX Vectors, or contact the Digital Services Group.
NOVER
no file version obtained for 'filespec' Facility: INSTALL, Install Utility Explanation: INSTALL could not obtain the file version number of the image file for the known file entry being listed. User Action: Ensure that the image file exists, and check the file protection.
NOVIRMEM
error allocating virtual memory Facility: DUMP, File Dump Utility Explanation: The File Dump Utility encountered an error during an attempt to allocate dynamic virtual memory. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command. The account's page file quota or the SYSGEN parameter VIRTUALPAGECNT may need to be increased.
NOVOLDATA
volume summary data for 'device-name' not found - /IMAGE cannot be used Facility: BACKUP, Backup Utility Explanation: In a restore operation with the /IMAGE qualifier, no volume initialization data exists. Either the save set is created without the /IMAGE qualifier, or save set data has been lost. User Action: Attempt to recover data without the /IMAGE qualifier. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility; in this case, submit a Software Performance Report (SPR).
NOVOLPRO
operation requires VOLPRO privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires VOLPRO privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOVOLUMES
no volumes are currently mounted Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not show mounted volumes, because none were mounted. User Action: Only use the EXCHANGE SHOW command if there is something to show.
NOWILD
no wildcard permitted Facility: Shared by several facilities Explanation: Wildcards are not permitted in this context. User Action: Respecify using exact file specifications.
NO_WINASSOC
no viewport has been associated with the display Facility: SMG, Screen Management Facility Explanation: A viewport window is not associated with the virtual display. User Action: Create a viewport on the virtual display.
NOWINDOW
attempt to position the cursor outside all of the mapped windows Facility: VAXTPU, VAX Text Processing Utility Explanation: You can move the cursor only to a position inside a mapped window. User Action: Move the mouse inside a window, and attempt position to the mouse again.
NOWORLD
operation requires WORLD privilege Facility: SYSTEM, VMS System Services Explanation: A command or program requested a system function that requires WORLD privilege; the current process does not have this privilege. User Action: If the message is in response to a command entered interactively, verify that you have not used a command or a qualifier for a particular command that requires a specific user privilege. If the message occurs during the execution of a program, determine the system service call that resulted in the error. Verify that you have not used a service or an argument for a particular service that requires a user privilege that you do not have. In either case, correct the command or program so that you do not request the privileged function. If you determine that you need the privilege for an application, contact your system manager to obtain the necessary privilege.
NOWRITER
no write channel is assigned to the device
Facility: SYSTEM, VMS System Services
Explanation: This message can be returned under either of the
following conditions:
o A sensemode writercheck $QIO request or a read writercheck $QIO
request was issued to a mailbox that has no writer assigned to
it.
o A read writercheck $QIO request was issued to a mailbox when no
write channels were assigned to the mailbox.
User Action: The mailbox driver allows channels to be assigned
to the mailbox as read-only, write-only, or read/write (the
default). Applications using read-only or write-only channels
should anticipate this error and count on it for synchronization.
If necessary, recode your application to expect this error or
consider using the older mailbox driver features; that is, use
read/write channels and do not use writercheck on a read request.
Refer to the VMS I/O User's Reference Manual: Part I for more
information about the mailbox driver.
NO_WRK
work files required, cannot do sort in memory as requested Facility: SORT, Sort/Merge Utility Explanation: The /WORK-FILES=0 qualifier is specified indicating the data would fit in memory, but the data is too large. User Action: Either increase the working set quota, or allow the Sort Utility to use two or more work files.
NOWRT
cannot create writeable section to read-only file Facility: SYSTEM, VMS System Services Explanation: An image file that is read-only opened contains a writable section. You cannot create a writable section to a read- only file. User Action: Close and open the file correctly. If the Install Utility returns this error, reenter the command but use the /WRITE qualifier in addition to /SHARE qualifier.
NPK
no primary key defined for indexed file Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $CREATE service is executed for an indexed file and no primary key XAB definition is provided. User Action: Verify that the VMS RMS service is coded correctly.
NSADDR
address 'addr' is not within image Facility: PATCH, Patch Utility Explanation: You specified an address outside the address range of the image file. User Action: Retry the operation specifying the correct address.
NSF
.END LIST/.END NOTE not in same file as .LIST/.NOTE: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You made an illegal attempt to start a list or note in one file and end it in another. User Action: End the list or note in the same file where you started it.
NTD
files nested too deep: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to nest .REQUIRE files more than 10 deep. User Action: Reduce the number of nested .REQUIRE files.
NUDFENVS
'number' undefined environments: Facility: LINK, Linker Utility Explanation: Undefined environments were encountered by the linker at the end of Pass 1. User Action: Ensure that all referenced environments are defined.
NUDFLSYMS
'number' undefined module-local symbols: Facility: LINK, Linker Utility Explanation: Undefined module-local symbols were encountered by the linker at the end of Pass 1. User Action: Ensure that all referenced module-local symbols are defined.
NUDFSYMS
'number' undefined symbols: Facility: LINK, Linker Utility Explanation: Undefined symbols were encountered by the linker. This message is issued at the end of Pass 1 of the link. User Action: Ensure that all symbols referenced are defined.
NULFIL
missing or invalid file specification - respecify Facility: CLI, Command Language Interpreter (DCL) Explanation: The command interpreter expected a file specification following an execute procedure symbol (@), a prompting message, a plus sign (+), or a comma (,), but no file specification is entered. User Action: Reenter the command; put the file specification in the proper position.
NULIDX
index is empty Facility: LBR, Librarian Subroutine Package Explanation: The specified index is found empty on a call to LBR$GET_INDEX. Processing continues. User Action: None.
NULLFILE
file 'filespec' contains no records Facility: SEARCH, SEARCH Command Explanation: This informational message indicates that the specified file is empty. This condition can occur when the file is currently being written by another process. User Action: None.
NULLPRI
null primary block Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility Explanation: You specified a primary that requires secondaries, but none were given. User Action: Specify secondaries for the primary.
NULLPRIV
no privileges specified - no action taken Facility: SYSMAN, Cluster System Management Utility Explanation: A SET PROFILE command specified neither a change in privileges nor a change in the default device or directory. User Action: Reenter the command with the appropriate qualifiers.
NULLSTRING
null string used Facility: VAXTPU, VAX Text Processing Utility Explanation: A null string was used where a non-null string is required. User Action: Enter a non-null string.
NULSAVESET
null save set name specified to RESTORE_SAVESET. Facility: VMSINSTAL, Install Procedures Explanation: A product installation procedure contained an incorrect call to RESTORE_SAVESET. User Action: Contact the Digital Services Group.
NUMBER
invalid numeric value - supply an integer Facility: CLI, Command Language Interpreter (DCL) Explanation: A numeric value is specified for a DCL command that expects values in certain radices, or interprets values within a particular context. For example, the number 999 is entered when an octal value is required. Or an alphabetic value is specified in a context that requires a numeric value, for example, a file version number. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for the legal values and reenter the command.
NUMELEMENTS
number of elements incorrect for component Facility: LIB, Library Facility Explanation: You specified an incorrect number of elements for the component. User Action: Examine the arguments to LIB$INIT_DATE_TIME_CONTEXT. Begin debugging procedures to verify and correct the problem. Numeric value illegal Facility: EDT, EDT Editor Explanation: You specified a number that is too large for the command specifier. User Action: Reenter the command specifying a valid value. Numeric value required Facility: EDT, EDT Editor Explanation: The command did not have a numeric value at the point of the ^ in the command. User Action: Reenter the command specifying a numeric value at the point of the ^.
NUM_KEY
too many keys specified Facility: SORT, Sort/Merge Utility Explanation: Up to 255 key definitions are allowed. Either too many key definitions have been specified or the NUMBER value is wrong. User Action: Check your command string key field specifications.
NUMOPRNDS
'xx' instructions must have 'nn' operands Facility: PATCH, Patch Utility Explanation: An operand is omitted from the MACRO-11 instruction. This instruction requires 'nn' operands. User Action: Reenter the command with the correct number of operands.
NUMTRUNC
number truncated Facility: PATCH, Patch Utility Explanation: The PATCH Utility truncated a numeric data entry because it exceeded the length of the data type. User Action: None.
NUMVAL
error code of 'xx' requesting update value Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed due to the error code represented as 'xx'. User Action: Retry the request using the correct error code (represented as 'xx').
NVROPRFAI
the last NVR operation has failed Facility: DTK, DECtalk Facility Explanation: A NVR operation failure occurred since the DECtalk device was turned on. User Action: Check the DECtalk hardware.
OBJ
invalid object identification Facility: NCP, Network Control Program Explanation: The identification of the object is not a valid object name. User Action: Check the syntax rules for object identifiers, and reenter your command with the correct object identifier.
OBJLOCKED
object currently locked by another user Facility: SYSTEM, VMS System Services Explanation: An attempt is to modify the access control list (ACL) of an object while another user is modifying the object's ACL. User Action: Repeat the operation at a later time.
OBSSERVERDB
obsolete audit server database 'n.n' encountered; new database created Facility: AUDSRV, Audit Server Explanation: An obsolete audit server database file was encountered by the audit server process during its initialization processing. A new database was created. The displayed numbers indicate the major and minor database version numbers. User Action: The site security administrator should ensure that the permanent audit server characteristics are correctly set in the new server database.
OBTEVT
error when reading raw events Facility: EVL, Event Logger Explanation: NETACP returned an error while EVL is reading unprocessed events. This message may be accompanied by a secondary message indicating a system configuration or process quota problem with the EVL process. User Action: Ensure that EVL has adequate quota and that the VMS system is configured properly. The account under which EVL runs is specified in the network Configuration Data Base.
OCCLUDED
built-in/keyword 'name' occluded by declaration Facility: VAXTPU, VAX Text Processing Utility Explanation: You declared a parameter, local, or constant that has the same name as a built-in or keyword. Your declaration obstructs the built-in or keyword. User Action: None.
OCVNOTFND
output converter not found Facility: CDA, Compound Document Architecture Explanation: The specified output converter could not be found. User Action: Check the format specified for the output file for errors. See if the file SYS$LIBRARY:'domain'$WRITE'format'.EXE exists, where 'domain' is DDIF for document formats or DTIF for tabular formats and 'format' is the output format specified by the calling application or the CONVERT/DOCUMENT command line.
ODS2SAVE
save set disk on 'device-name' must be structure level 2 Facility: BACKUP, Backup Utility Explanation: The specified volume is not a Files-11 Structure Level 2 volume. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
OFFHOOK
telephone is offhook (active) Facility: DTK, DECtalk Facility Explanation: This informational message indicates that the phone is off the hook (a call is active). User Action: None.
OFFLINE
'device-name' : offline Facility: MOUNT, Mount Utility Explanation: The given device is off line. The requested action cannot be completed. User Action: Place the device on line and reenter the command.
OK_ALK
record is already locked Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to lock a record returns this success status code when the specified record is already locked. This is a success status. User Action: None.
OK_DEL
deleted record successfully accessed Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to access a deleted record returns this success status code when the specified record is accessed. This is a success status. User Action: None.
OK_DUP
record inserted had duplicate key Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $PUT or $UPDATE service completed successfully. The record inserted or updated had one or more key values that duplicated the values of other records. This is a success status. User Action: None.
OK_IDX
index update error occurred Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $PUT or $UPDATE service completed successfully. However, the index could not be completely updated. No access paths to the record have been lost; access to the record will take longer. User Action: The status value (STV) field of the RAB contains the VMS RMS error that occurred during index update. Take corrective action based on that value. File reorganization with the CONVERT command is recommended to improve performance.
OK_LIM
retrieved record exceeds specified key value Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $GET or $FIND request returns this success code if the retrieved record exceeds the specified key value and if the RAB$V_LIM option is specified. This is a success status. User Action: None.
OK_NOP
XAB not filled in for block I/O Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $OPEN or $DISPLAY service that specified block I/O access (BIO) completed successfully. However, one or more key definition or allocation XABs were not filled in. This is a success status. User Action: None.
OK_RLK
record locked but read anyway Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to read a locked record completed successfully. This is a success status. User Action: None.
OK_RNF
nonexistent record successfully accessed Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to access a nonexistent record completed successfully. This is a success status. User Action: None.
OK_RRL
record locked against read but read anyway Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to read a record locked against read is completed successfully. This is a success status. User Action: None.
OK_WAT
record locked after wait Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request to access a record locked after wait completed successfully. This is a success status. User Action: None.
OLDINSCHK
memory location 'addr' not equal to 'xx' Facility: PATCH, Patch Utility Explanation: The verification of the contents of the given address failed. User Action: Reenter the PATCH command specifying the correct value.
OLDLIBRARY
old format library opened Facility: LBR, Librarian Subroutine Package Explanation: This success message is generated by the Librarian routines when a library that is not in the current format is opened. User Action: None.
OLDMISMCH
old format library type mismatch Facility: LBR, Librarian Subroutine Package Explanation: The requested Version 1.0 library is a different type from the type expected. Processing continues based on the actual library type. User Action: None.
OLDPURGE
security auditing resources exhausted; oldest message purged Facility: AUDSRV, Audit Server Explanation: The audit server internal message buffer has been exhausted. As a result, the audit server has chosen to purge the oldest security alarm from its internal buffer in an attempt to preserve the newest alarms. User Action: None. This event results from the server FINAL_ACTION setting of PURGE_OLD.
OLDTAB
command tables have obsolete format - use SET COMMAND to recreate Facility: CLI, Command Language Interpreter (DCL) Explanation: CLI encountered a command table with an obsolete format while trying to automatically update it to the current format. The obsolete command table must be manually updated. User Action: Use Command Definition Utility command SET COMMAND to re-create the tables.
OLDVALCHK
memory location 'addr' not equal to 'xx' Facility: PATCH, Patch Utility Explanation: The verification of the contents of the given address failed. User Action: Reenter the PATCH command specifying the correct value. On output page 'pn'; on input line 'ln' of page 'pn' of file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This is a standard error message line that specifies the location of an error string. This message indicates the number of the page (pn) in the output file affected by the error and the name of the input file (filename), including the input page (pn) and the line number (ln) in which the error occurred. User Action: Find and correct the error string.
ONCOMD
ON command too large - decrease the length of the THEN clause Facility: CLI, Command Language Interpreter (DCL) Explanation: The command action for an ON command in a command procedure is too complex to be evaluated or too large to be stored. User Action: Correct the command procedure simplifying the ON command action.
ONDELRECLIST
attempt to access a record on the deleted list Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
ONEDELTIM
at least one delta time is required Facility: LIB, Library Facility Explanation: The LIB$DATE_TIME routine requires at least one of the inputs to be a delta time. User Action: Examine each argument. Determine which argument is incorrect and replace it with a delta time.
ONEENTQUE
one entry in queue Facility: LIB, Library Facility Explanation: The procedure successfully completed. An entry is added to the front of the queue. As a result, the queue contains one entry. User Action: None.
ONEF11DEV
both input and output must not be save sets Facility: BACKUP, Backup Utility Explanation: When you executed the BACKUP command, you specified that both input and output files reference a save set. Either the input or the output specification, not both, can reference a save set. User Action: Reenter the command.
ONEF11OUT
file-structured output must not be a list Facility: BACKUP, Backup Utility Explanation: The output specification for a copy, restore, or compare operation without the /IMAGE qualifier is a list of file specifications. (BACKUP does not accept this.) User Action: Modify your output specification and reenter the command.
ONEIMGDEV
the /IMAGE input specification must not be a list Facility: BACKUP, Backup Utility Explanation: The specification for an input volume set to be processed with the /IMAGE qualifier is a list of file specifications. (BACKUP does not accept this.) User Action: Modify your input specification and reenter the command.
ONELEARN
cannot start a learn sequence while one is active Facility: VAXTPU, VAX Text Processing Utility Explanation: You can create only one learn sequence at a time. User Action: Terminate the current learn sequence before starting a new one.
ONEPHYDEV
the /PHYSICAL specification must not be a list Facility: BACKUP, Backup Utility Explanation: The specification for a physical volume is a list of file specifications. (BACKUP does not accept this.) User Action: Modify your specification and reenter the command.
ONERR
invalid ON condition - use WARNING, SEVERE, ERROR or CONTROL_Y Facility: CLI, Command Language Interpreter (DCL) Explanation: The keyword specified in the DCL command ON to indicate the condition is not recognized. User Action: Correct the DCL command ON, using one of the keywords-CONTROL_Y, WARNING, ERROR, or SEVERE_ERROR.
ONESELECT
select already active, maximum 1 per buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: You used the built-in procedure SELECT a second time within the same buffer. User Action: Set the previous select mark to 0 or delete the current select range with the DELETE built-in procedure.
ONEVAL
list of values not allowed - check use of comma (,) Facility: CLI, Command Language Interpreter (DCL) Explanation: A qualifier, keyword, or parameter that accepts only a single value is specified with multiple values. User Action: Reenter the command specifying only one value.
ONHOOK
telephone is onhook (inactive) Facility: DTK, DECtalk Facility Explanation: This informational message indicates that the phone is on the hook (no call is active). User Action: None.
ONLEVL
invalid ON context - use only within command procedures Facility: CLI, Command Language Interpreter (DCL) Explanation: An ON command is issued interactively. It can be issued only from within a command procedure. User Action: None.
ONOVF
no room for ON command - symbol overflow, delete some symbols Facility: CLI, Command Language Interpreter (DCL) Explanation: Symbol or keypad definitions have exhausted the command interpreter's space for storing values. User Action: If necessary, interrupt the command procedure with Ctrl/Y and stop its execution. Use the DCL commands SHOW SYMBOL and SHOW KEY to determine how many global symbols and keypad symbols are defined; delete unused symbols to recover symbol table space. If the error occurs frequently, simplify the command procedure or procedures. Use local symbols within procedures whenever possible.
OPCCUS
opcode reserved to customer fault at PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An operation code beginning with ^XFC is encountered during execution of an image. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine the instruction that caused the error.
OPCDEC
opcode reserved to DIGITAL fault at PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: The operation code at the indicated address is not known. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine the instruction that caused the error.
OPEFAI
operation failure 'error' Facility: NCP, Network Control Program Explanation: The requested operation failed for the reason identified in the 'error' part of the message. User Action: Take corrective action based on the system-specific error message.
OPEJBCMBX
error opening job controller mailbox Facility: JBC, Job Controller Explanation: The job controller encountered an error assigning a channel to its mailbox. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
OPENBITMAP
error opening BITMAP.SYS, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to open the storage bit map file, [000000]BITMAP.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
OPENDIR
error opening directory 'directory-name' Facility: BACKUP, Backup Utility and ANALDISK, Analyze/Disk_ Structure Utility Explanation: An error was encountered during an attempt to open the specified directory file. An accompanying message provides additional information. The Backup Utility cannot process files in this directory or its subdirectories. User Action: Correct the condition that caused the error and reenter the command line.
OPENDIR
error opening parent directory for 'directory-name' Facility: SET, SET Facility Explanation: A parent directory could not be opened. User Action: Take corrective action based on the accompanying message.
OPENERR
error opening 'filespec' Facility: Shared by several facilities Explanation: The specified file cannot be opened. Usually an accompanying RMS message indicates why the file cannot be opened. User Action: Take corrective action based on the accompanying message.
OPENEXC
error opening exception file 'filespec' Facility: CONVERT, Convert Utility Explanation: This message will be accompanied by an RMS message that explains the error. User Action: Correct the error described by the RMS message and try again.
OPENFAIL
failure opening component file 'file-number', 'file-name' Facility: STDRV, System Startup Driver Explanation: The startup driver failed to open one of the system files that describes the tasks that need to be performed at startup time. The startup operation attempts to continue, but may not properly perform all startup tasks. User Action: Make sure that the named file is available and can be read.
OPENFDL
error opening 'filename' Facility: FDL, Create/FDL Utility and FDL, Edit/FDL Utility Explanation: This message will be accompanied by an RMS message that explains the error. User Action: Correct the error described in the RMS error message and try again.
OPENFILE
error creating event file 'file-id' Facility: EVL, Event Logger Explanation: An error occurred while creating an event file. All events destined for that sink will be discarded. This message displays the name of the file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
OPENFILE
file ('file-id') 'filename' error opening file for read check
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to
open the specified file to execute the /READ_CHECK function. An
accompanying message provides additional information.
User Action: Correct the condition that caused the error and
reenter the command.
OPENFOREIGN
unable to open 'device-name' as a foreign volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encounted an RMS error while trying to $OPEN or $CONNECT to a foreign-mounted device. User Action: This message will be followed by one or two lines of RMS error messages. Please take corrective action based on the actual error condition that RMS discovered.
OPENIN
error opening 'input-filespec' as input Facility: Shared by several facilities Explanation: An input file cannot be opened. This message is usually accompanied by an RMS message indicating the reason for the failure. User Action: Follow the recovery procedure for the associated RMS message.
OPENIN
error opening 'filespec' as input Facility: MACRO, VAX MACRO Assembler Explanation: The assembler encountered an I/O error when opening an input source or macro library file; filespec is the file specification of the file being opened. This message is produced when the file cannot be found. User Action: Retry the assembly or make a new copy of the input file and try the assembly.
OPENIN
'input-filespec' open error
Facility: LIBRAR, LIBRARY Command
Explanation: One of the following conditions prevented the DCL
command LIBRARY from opening the input file:
o The user directory is protected against read operations.
o A physical device problem occurred; for example, the volume is
not mounted.
o The specified directory does not exist.
o The specified file does not exist.
o Create or compress operations do not allow enough room or quota
to allocate the new library file.
User Action: Correct the problem and reenter the command line.
OPENINDEX
error opening INDEXF.SYS, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to open the index file, [000000]INDEXF.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the the command.
OPENMON
error creating logical link to monitor process 'sink-name' Facility: EVL, Event Logger Explanation: An error occurred while establishing a logical link to a sink monitor program. The program image or command file may not be present. All events destined for that sink will be discarded. User Action: Take corrective action based on the accompanying message.
OPENOUT
error opening 'output-filespec' Facility: LIBRAR, LIBRARY Command Explanation: During a VMS RMS operation, an error is encountered while opening an output file. User Action: Determine that the file is open and that you have WRITE privilege to it.
OPENOUT
error opening 'output-filespec' as output Facility: Shared by several facilities Explanation: An output file cannot be opened. This message is usually accompanied by an RMS message indicating the reason for the failure. User Action: Follow the recovery procedure for the associated RMS message.
OPENOUT
error opening 'filespec' as output Facility: MACRO, VAX MACRO Assembler Explanation: The assembler encountered an I/O error when opening an output object module or listing file; filespec is the file specification of the file being opened. The message is produced when the device is write locked or is not mounted. User Action: Retry the assembly. If the error is reproducible, notify your system manager.
OPENOUT
unable to create, open, or connect to an output Facility: ACCOUNTING, Accounting Utility Explanation: An output file cannot be opened. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
OPENQUOTA
error opening QUOTA.SYS Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to open the quota file, [000000]QUOTA.SYS;1, on relative volume 1. The accompanying message provides additional information. This condition is normal if quotas are not enforced on the volume. User Action: If necessary, correct the condition that caused the error and reenter the command.
OPENUAF
error opening user authorization file Facility: INPSMB, Input Symbiont Explanation: The system encountered an error opening the user authorization file to validate a batch job entered from a card reader. The accompanying message provides additional information. User Action: Consult your system manager.
OPENVIRTUAL
unable to open 'filename' as a virtual volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an RMS error while trying to $OPEN or $CONNECT to a Files-11 file being used as a virtual device. User Action: This message will be followed by one or two lines of RMS error messages. Please take corrective action based on the actual error condition that RMS discovered.
OPER1
OPER1 Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "CARDS" class operations. User Action: None.
OPER10
OPER10 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER11
OPER11 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER12
OPER12 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER2
OPER2 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER3
OPER3 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER4
OPER4 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER5
OPER5 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER6
OPER6 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER7
OPER7 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER8
OPER8 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPER9
OPER9 Facility: OPCOM, Operator Communication Process Explanation: This message is issued optionally with the OPERSTS message. It describes the classes of operator requests that the current operator is enabled to act upon. User Action: None.
OPERABORT
operator has aborted request, reply is 'reply' Facility: BACKUP, Backup Utility Explanation: The operator has aborted or canceled the request. User Action: Determine the reason for the cancellation from the reply given in the message and proceed accordingly.
OPERASSIST
operator assistance has been requested Facility: BACKUP, Backup Utility Explanation: This message notifies you that operator assistance has been requested. User Action: None.
OPERFAIL
error requesting operator service Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to interact with the operator. The accompanying message provides additional information. The error may be caused because the operator replied to the request with REPLY/ABORT. User Action: Correct the condition that caused the error and reenter the command.
OPERREQ
OPER privilege required for /ACCESSED qualifier Facility: SET, SET Facility Explanation: OPER privilege is required for this qualifier. User Action: See your system manager about obtaining OPER privilege.
OPERSPEC
specify option ('options')
Facility: BACKUP, Backup Utility
Explanation: This message is returned to the operator. It
indicates that BACKUP has encountered a recoverable error. The
operator must select one of the options listed in the message.
The possible options are QUIT, CONTINUE, and RESTART. If the
QUIT option is selected, BACKUP will terminate. If the CONTINUE
option is selected, BACKUP will ignore the error and continue
processing. If the RESTART option is selected, BACKUP will restart
the operation at the beginning of the current volume.
User Action: The operator should evaluate the preceding errors and
select the appropriate option.
OPERSTS
operator status for operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: This message displays information in response to the DCL command REPLY/STATUS entered by an operator. User Action: None.
OPINCOMPL
operation is incomplete Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned from a DR11-W interface operation. A block mode transfer operation completed without transferring the requested number of bytes. The DR11-W generated an end-of-transfer interrupt without transferring all the data. This message results from a hardware error. Some disk devices can also return this message. On a WRITE request the XE unit has not completed restarting after a hardware failure. Some magnetic tape devices can also return this message if there is an attempt to read beyond the logical end of volume. User Action: Check for a hardware error. Wait a few seconds before entering another WRITE request.
OPINPROG
previously requested operation is incomplete Facility: SYSTEM, VMS System Services Explanation: A request could not be completed because of outstanding requests on the service. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the output of both the LMCP DUMP command and the DCL DUMP command for the log file.
OPNERR
open error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: A VMS RMS $OPEN request failed due to the error code represented as 'xx'. User Action: Correct the error code (representing as xx) and retry.
OPNOTPERDOS
operation not permitted on DOS-11 volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a command which could not be performed on a DOS-11 volume, such as a RENAME or DELETE command. User Action: Think of something else that you want to do, since EXCHANGE will not perform the operation.
OPNOTPERF11
operation not permitted on Files-11 volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a command which could not be performed on a Files-11 volume, such as a DELETE or DIRECTORY command. User Action: Think of something else that you want to do, since EXCHANGE will not perform the operation.
OPNOTSUP
operation not supported by RMS Extension Facility: RMS, VMS Record Management Services Explanation: An extended RMS component has been requested to perform a service it is incapable of performing. For example, attempting to do a $PUT to a file coded with DDIF semantics. User Action: Verify that the application program is not attempting to modify the data file.
OPNOTSUP
operation is not supported on this device Facility: SMG, Screen Management Facility Explanation: The requested operation cannot be performed, since the terminal hardware does not support this feature. User Action: Run the application on a terminal that supports this feature.
OPNSNK
unable to open link to event receiver Facility: EVL, Event Logger Explanation: An error occurred when EVL attempted to open a logical link to an event receiver on a sink node. The sink node may not be reachable in the network, or the VMS system or network may be misconfigured. User Action: Take correction action based on the accompanying message.
OPRABORT
mount aborted by operator Facility: MOUNT, Mount Utility Explanation: This is the final message in a series of messages issued from MOUNT to the operator. The operator has refused your request. User Action: None.
OPREPL
'reply' Facility: OPCOM, Operator Communication Process Explanation: This is the operator's reply to a user's request or question. User Action: Determined by the operator's reply.
OPREPLY
'message-text' Facility: MOUNT, Mount Utility Explanation: An operator's response to the DCL command REQUEST is displayed on the terminal. This message is informational. User Action: None.
OPREPLY
operator reply is 'string' Facility: BACKUP, Backup Utility Explanation: The operator replied to an operator request with the text string contained within quotes in the message. User Action: None.
OPRNDLNG
operand 'xx' too long for internal buffers Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report (SPR).
OPRNDSYNX
operand syntax error Facility: MACRO, VAX MACRO Assembler Explanation: An operand contained a syntax error. User Action: Correct the operand syntax.
OPRNOTIF
operator notified, waiting.. 'system time' Facility: OPCOM, Operator Communication Process Explanation: The DCL command REQUEST is entered with the /REPLY qualifier; the request has been sent and displayed on the operator's terminal. You cannot enter any commands until the operator responds to your request. User Action: If you want to interrupt the request, press Ctrl /C and enter another message to the operator or press Ctrl/Z to cancel the request.
OPRQST
operator request: 'request' Facility: MOUNT, Mount Utility Explanation: This informational message announces an operator request. User Action: None.
OPRQSTCAN
operator request canceled Facility: MOUNT, Mount Utility Explanation: You canceled your request by pressing Ctrl/Y; this canceled the MOUNT request. User Action: None.
OPRQSTDON
operator request canceled - mount completed successfully Facility: MOUNT, Mount Utility Explanation: The operator request is canceled because the request is completed. User Action: None.
OPRSNDERR
error sending request to operator Facility: MOUNT, Mount Utility Explanation: MOUNT failed in an attempt to send a message to the operator. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
OPSYNTAX
instruction operand syntax error Facility: PATCH, Patch Utility Explanation: There is a syntactical error in an operand within an instruction. User Action: Correct the syntax and retry.
OPTARGMIS
missing argument in options file 'filename' Facility: LINK, Linker Utility Explanation: A required argument for an option is missing. User Action: Correct the option line and relink.
OPTIGNSHR
option ignored for shareable image Facility: LINK, Linker Utility Explanation: An option that does not apply to a shareable image is specified in an options file. The linker ignores the option when creating a shareable image. User Action: Remove the option from the options file.
OPTIGNSYS
option ignored for system image Facility: LINK, Linker Utility Explanation: You specified an option in an options file that is ignored for system images. User Action: Remove the option.
OPTLIN
options line in error 'text' 'text' 'text' Facility: LINK, Linker Utility Explanation: Errors were found on the command line during options file processing. User Action: None.
OPTSYNERR
syntax error in options file 'filename' Facility: LINK, Linker Utility Explanation: A syntax error is detected in the options file. The next line of the error message displays the line in error. User Action: Correct the error and relink.
OPTVALERR
'name' option value 'decimal-number' is out of range ('decimal-
number' to 'decimal-number') in options file 'file -name'
Facility: LINK, Linker Utility
Explanation: An option specified an illegal value.
User Action: Correct the option line and relink.
ORBTOOBIG
object rights block too big Facility: SYSTEM, VMS System Services Explanation: The object rights block (ORB) for the specified object is too large to package and send to another subsystem. User Action: Have your system manager use the ACL editor to remove unnecessary access control lists (ACLs) from the object or reorganize the ACLs. See the Guide to VMS System Security for more information about ACLs.
ORDER
routine called out of order Facility: CONVERT, Convert Utility Explanation: You have called one of the callable routines out of order. The required order is CONV$PASS_FILES, CONV$PASS_OPTIONS, and CONV$CONVERT. User Action: Fix the order and try again.
ORDER_ERROR
record state invalid in transaction sequence Facility: LMCP, Log Manager Control Program Explanation: The transaction log file lists transaction states in an invalid sequence, for example, a prepare state is listed after a commit state. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP command for the given log file and the output of the DCL DUMP command for the same log file.
ORG
invalid file organization value Facility: RMS, VMS Record Management Services Explanation: An invalid file organization is encountered on a $OPEN system service or specified for a $CREATE system service. Files must be either sequential, relative, or indexed, unless block I/O processing is requested. User Action: Verify that the call to the VMS RMS system service is coded correctly. ORIGINAL line numbers no longer an EDT feature Facility: EDT, EDT Editor Explanation: EDT has been revised to enable users to edit sequence-numbered files and to retain the sequence numbers for future work. The new capabilities replace the original line number feature. User Action: None.
OSCTOOLON
operating system command string too long in record 'record-number' Facility: PSM, Print Symbiont Explanation: This status is returned indicating operating system command string is longer than allowed in this record number. User Action: None.
OUTCMDLNG
output command line too long for buffer Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report (SPR).
OUTCONERR
output conversion error Facility: OTS, General Purpose Facility Explanation: The result would have exceeded the fixed-length string. User Action: Increase the length of the fixed-length string and retry the operation.
OUTOFRANGE
value specified is not within the legal range for this qualifier Facility: LAT, LAT Facility Explanation: You specified a value that is out of range for a LATCP qualifier. User Action: Specify a value within the legal range (see the VMS LAT Control Program (LATCP) Manual).
OUTORDER
key or area primary defined out of order in statement 'number' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: If there are two or more AREA sections, they must be in ascending order by area number and must follow each other. If there are two or more KEY sections, they too must be consecutive and adjacent. User Action: Fix the order.
OUTPUT
command execution on node 'nnnnnn' Facility: SYSMAN, Cluster System Management Utility Explanation: A DO command generated output from node 'nnnnnn'. The output follows this message. User Action: If you do not want to see the output, press Ctrl/C to return to the SYSMAN> prompt. Output file could not be closed Facility: EDT, EDT Editor Explanation: EDT opened the output file and copied the MAIN buffer text into that file. However, for some reason at the system level, EDT cannot close that file. User Action: Correct the problem indicated in the accompanying message. Output file could not be created Facility: EDT, EDT Editor Explanation: EDT could not create the output file with the file specification you supplied with the EXIT command. This error can be caused by problems in the file name itself (either it contains too many characters or it contains an invalid character). Other causes include problems in the directory specification, if you used one (either the directory does not exist, you do not have access to it, or the directory specification format is incorrect). This message could also mean that a problem with the file system exists, such as insufficient disk space. User Action: After determining the cause of the problem, correct it. Output file could not be opened Facility: EDT, EDT Editor Explanation: EDT will display another message describing the error. User Action: Take corrective action based on the accompanying message.
OUT_RANGE
number cannot be less than 1 or larger than 127 Facility: SYSGEN, System Generation Utility Explanation: You entered a SYSGEN command CONFIGURE with a number that is either too small or too large. User Action: Reenter the command specifying a number within the range of 1 to 127.
OUTSIMG
attempted store location 'address' is outside 'name' ('address' to
'address') in module 'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An attempt is made to store outside the specified
program segment. This may be caused by an attempt to initialize
a shared COMMON of a shareable image when linking against the
shareable image.
User Action: Initialize the data either at execution time or when
linking the shareable image containing the COMMON.
OUTSIMGP
attempted store location 'address' is outside 'name' ('address'
to 'address') in psect 'psect-name' module 'module-name' file
'filename'
Facility: LINK, Linker Utility
Explanation: An attempt is made to store an address outside the
specified program segment. This is generally due to an attempt
to initialize a shared COMMON of a shareable image when linking
against the shareable image. This message is issued if the psect
name is known.
User Action: Initialize the data at execution time.
OUTSTRTRU
output string truncated Facility: LIB, Library Facility Explanation: The source and destination strings are character coded text datum, and the destination string cannot contain all of the output string. The output string is truncated. User Action: None.
OUTSWPERR
outswap write error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
OVERFLOW
overflow in floating addresses, illegal configuration Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN command CONFIGURE has computed an illegal floating address for a CSR or vector. User Action: Reenter the SYSGEN command CONFIGURE with the correct number of controllers.
OVERLAPRANGE
overlapping ranges, operation terminated Facility: VAXTPU, VAX Text Processing Utility Explanation: The source and destination ranges of a COPY_TEXT or MOVE_TEXT overlap. The operation was terminated before any modifications were performed. User Action: Do not specify overlapping ranges to COPY_TEXT or MOVE_TEXT.
OVERLAY
'filespec' being overwritten Facility: Shared by several facilities Explanation: A file is being successfully overwritten. This message is a success return. User Action: None.
OVERWRITE
relative volume 'volume-name' on device 'device-name' will be overwritten Facility: BACKUP, Backup Utility Explanation: This message notifies you that the volume header of the indicated volume will be overwritten with the information requested by the BACKUP command. User Action: None.
OVRALI
conflicting alignment on overlayed psect 'psect-name' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: Different definitions of an overlayed psect contain different alignment specifications. User Action: Ensure that the specified psect has the same alignment in all modules referencing it.
OVRDSKQUOTA
disk usage exceeds disk quota Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned by a file system ACP QIO request. Disk usage exceeds the specified quota. User Action: None.
OVRFLW
too much data - modify size of field or size of data Facility: CLI, Command Language Interpreter (DCL) Explanation: A data value specified is larger than the area defined to receive it; for example, a DCL command DEPOSIT requested that a value larger than 1 byte be deposited in a 1-byte area. User Action: Verify the value and the area to receive it; correct the value or the receiving area and reenter the command.
OVRSIZ
oversized management command message Facility: NCP, Network Control Program Explanation: A message from NCP using the Network Information and Control Exchange (NICE) protocol is too long for the Network Management Listener (NML) to receive. User Action: Submit a Software Performance Report showing all the commands leading to this error.
PACTOOLONG
packed decimal string too long Facility: MACRO, VAX MACRO Assembler Explanation: The numeric string in a .PACKED directive has more than 31 digits. User Action: Reduce the length of the decimal string.
PAD
PAD option ignored, output record format not fixed Facility: CONVERT, Convert Utility Explanation: You can pad records only with the FIXED record format in the output file. User Action: Either change the output file record format to FIXED, or do not specify a /PAD qualifier on the command line.
PAGECRIT
page file space critical, system trying to continue Facility: SYSTEM, VMS System Services Explanation: The system is running out of page file space. This message is more critical than the PAGEFRAG message. User Action: Create a new page file with more space. See the Guide to Setting Up a VMS System.
PAGEFRAG
page file badly fragmented, system continuing Facility: SYSTEM, VMS System Services Explanation: The system is running out of page file space. User Action: Create a new page file with more space. See the Guide to Setting Up a VMS System.
PAGEREDERR
page read error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.) Pages written to 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This message indicates the number of pages written to the specified output file (filename). User Action: None.
PAGEWRTERR
page write error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PAGLIMEXC
page limit exceeded for zone Facility: LIB, Library Facility Explanation: Allocation exceeds the page limit for the zone. A LIB$GET_VM request has attempted to allocate more pages than specified by the page_limit attribute for the zone. User Action: Modify your program to allocate fewer pages, to create a zone with a higher page limit, or to request pages from another zone.
PAGNTRNVAL
page not in transition or valid Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PAGOWNVIO
page owner violation Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: An image attempted to change a page in memory that is owned by a more privileged access mode. For example, an image executing in user mode attempted to delete a page owned by supervisor mode. User Action: Check for a programming error. Verify that pages referred to in system service calls are owned by the calling access mode.
PAGRDERR
page read error, reason mask = 'xx', virtual-address = 'location', PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: The system failed to read a page from disk into memory during a page fault operation. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Check the status of the device and repeat the request. Also check for a FORCEDERROR message on the image or in the page file by using the DCL command ANALYZE/DISK_STRUCTURE /READ_CHECK. If the failure persists, notify your system manager. Parallel Path is Closing Virtual Circuit - REMOTE PORT 'xxx' Facility: VAXport, VAXport Driver Explanation: The Port Driver switched communications from a low performance communication link to a high performance communication link. This event is a normal virtual circuit shutdown. User Action: None. Parenthesis mismatch Facility: EDT, EDT Editor Explanation: The number of right parentheses [)] does not match the number of left parentheses [(]. This error occurs when you are entering a change mode command string. User Action: Modify your change mode command string to include an equal number of properly nested left and right parentheses.
PARGTMTCH
value of 'x' for /PARALLEL is greater than /MATCH value of 'y', /PARALLEL set to 'y' Facility: DIFF, DIFFERENCES Command Explanation: A /PARALLEL value is specified that is greater than the /MATCH value. User Action: Decrease the /PARALLEL value. The /PARALLEL value must always be less than or equal to the /MATCH value.
PARITY
disk boot driver parity error Facility: VAXCLUSTER, VAXcluster Facility Explanation: There is a hardware error during a transfer from the satellite system disk. User Action: Check the error log for both the Ethernet and system disk, run diagnostics for the suspect hardware, or contact the Digital Services Group.
PARITY
parity error
Facility: SYSTEM, VMS System Services
Explanation: The exact meaning of this message depends on the
device.
If this message is associated with a status code returned by a
request to a DR11-W interface, a parity error is detected in a
block mode transfer when the Buffered Data Path of the UNIBUS
adapter is purged.
If this message is associated with a status code returned by a
request to a DR32 interface, either the microcode is not loaded
successfully or the DR32 controller detected a parity error and a
hardware malfunction is indicated. The second longword of the I/O
status block contains additional information pertaining to this
malfunction for the DR32; the following bit values are associated
with SS$_PARITY:
XF$V_IOS_WCSPE
XF$V_IOS_CIPE
XF$V_IOS_DIPE
XF$V_IOS_PARERR
If this message is associated with a status code returned by a
request to a disk driver, one or more of the following conditions
can cause this error:
o Drive parity error
o ECC hard error
o Header compare error
o Map parity error
o Header CRC error
o MASSBUS control parity error
If this message is associated with a status code returned by a
request to a magnetic tape driver, one or more of the following
conditions can cause this error:
Attempt to read beyond the logical end of volume
CRC error (NRZI only)
Control bus parity error
Correctable data error (PE only)
Correctable skew (PE only)
Data bus parity error
Incorrectable error (PE only)
Invalid tape mark (NRZI only)
Nonstandard gap
Longitudinal parity error (NRZI only)
Format error (PE only)
Vertical parity error (NRZI only)
Map parity error
MASSBUS control parity error
MASSBUS data parity error
Read data substitute
If this message is associated with a status code returned by a
request to an LPA11-K driver, a parity error occurred in a UBA-
buffered datapath.
If this message is associated with a status code returned by a
request to a terminal driver, a parity bit mismatch is detected by
the device interface during a read operation. The I/O operation
stopped when the mismatch is detected. (Data is received up to
this point in the operation.) SS$_PARITY is meaningful only on
terminal lines that have parity enabled.
User Action: Action depends on the type of device to which the I/O
request is directed.
PARMDEL
invalid parameter delimiter - check use of special characters Facility: CLI, Command Language Interpreter (DCL) Explanation: A command contains an invalid character following the specification of a parameter. Or an invalid character is present in a file specification. User Action: Check the command string for a spelling or grammatical error. Reenter the command.
PARNOTGRANT
parent lock must be granted Facility: SYSTEM, VMS System Services Explanation: A programming error has occurred because an attempt is made to create a sublock under a parent lock that is not granted. User Action: Correct the programming error and retry.
PARSE
error opening 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to access the specified file. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
PARSEERR
internal parsing error Facility: PATCH, Patch Utility Explanation: This message indicates an internal PATCH error. User Action: Submit a Software Performance Report (SPR).
PARSEERR
unable to parse input name 'name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility attempted to interpret the given name as a file name, but is unable to do so successfully. User Action: This message is followed by a second message giving more specific information about why the name is not a valid file name. Take corrective action based on the additional message.
PARSEFAIL
error parsing 'filespec' Facility: Shared by several facilities Explanation: An error is detected while parsing an input command or source line. User Action: Correct the error.
PARSEFAIL
error parsing 'filespec' Facility: VAXTPU, VAX Text Processing Utility Explanation: An error is detected by VMS RMS while parsing a file specification. This message should be accompanied by a VMS RMS message explaining the reason for the failure. User Action: Follow the recovery procedure for the specified VMS RMS message.
PARSEOVER
parser stack overflow Facility: VAXTPU, VAX Text Processing Utility Explanation: The program is too complex for VAXTPU to evaluate. User Action: Simplify the expression. Parsing stack overflow Facility: EDT, EDT Editor Explanation: The command you entered caused the memory space for the parse data to be filled before the command could be validated. User Action: Check your command string. If it is valid, reenter the command in segments.
PARTCOPIED
file 'filename' partially copied to 'filespec' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility had copied part of a file before an error is discovered. User Action: This message is followed by another message describing the specific error which occurred. Take corrective action based on the second message.
PARTESCAPE
partial escape Facility: SYSTEM, VMS System Services Explanation: A terminal escape sequence is only partially stored because the buffer space is exhausted before the sequence is complete. The type-ahead buffer contains the remainder of the escape sequence unless the terminal line had the TT$M_NOTYPEAHD characteristic. User Action: Check for a programming error. Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
PARTMAPPED
some file map pointers not permanently resident Facility: SYSTEM, VMS System Services Explanation: A call is issued to the $CRMPSC system service to map a section file; the ACP is unable to make all mapping pointers for the file permanently resident. The $CRMPSC call can be made directly or can be issued on the user's behalf when running an image. User Action: Either reduce the amount of fragmentation in the file (for example, by copying the file to a disk with a large amount of free space) or increase the process BYTCNT quota to allow the entire file to be permanently mapped.
PARTOOBIG
parameters too large - must be shortened Facility: SYSMAN, Cluster System Management Utility Explanation: You attempted to add a startup component file that uses /PARAM qualifiers to specify a set of qualifiers with a total length that exceeds the maximum length allowed. User Action: Reenter the command using a smaller parameter set.
PART_SECTN
unable to interpret partially written section Facility: LMCP, Log Manager Control Program Explanation: The section being analyzed by LMCP failed the write check test, this determines if the section was completely written to the log file. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP and the DCL DUMP commands for the given log file.
PASALREXI
pasteboard already exists for this device Facility: SMG, Screen Management Facility Explanation: A user tried to create a pasteboard for a device, when one is already created. This is normal in a modular environment. The existing pasteboard id is returned. Make sure you do not delete a pasteboard that you did not create. User Action: None. Pass bad status to caller Facility: EDT, EDT Editor Explanation: While using callable EDT, the bad status is not passed to the calling program due to an error in EDT. User Action: Submit a Software Performance Report (SPR).
PATERR
internal patch coding error Facility: PATCH, Patch Utility Explanation: An internal PATCH error has occurred. User Action: Submit a Software Performance Report (SPR). Path #0. Has become working but CROSSED to Path #1. - REMOTE PORT 'xxx' Facility: VAXport, VAXport Driver Explanation: The Port Driver logs this event. User Action: Check for crossed-cable pairs. Path #0. Has gone from BAD to GOOD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: None. Path #0. Has gone from GOOD to BAD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: Check Path A cables for breaks or improper connections. Path #0. Loopback has gone from BAD to GOOD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: None. Path #0. Loopback has gone from GOOD to BAD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: Check for crossed-cable pairs or faulty CI hardware. Path #1. Has become working but CROSSED to Path #0. - REMOTE PORT 'xxx' Facility: VAXport, VAXport Driver Explanation: The Port Driver logs this event. User Action: Check for crossed-cable pairs. Path #1. Has gone from BAD to GOOD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: None. Path #1. Has gone from GOOD to BAD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: Check Path B cables for breaks or improper connections. Path #1. Loopback has gone from BAD to GOOD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: None. Path #1. Loopback has gone from GOOD to BAD Facility: VAXport, VAXport Driver Explanation: The VAXport driver logs this event. User Action: Check for crossed-cable pairs or faulty CI hardware.
PATHAMBIG
line 'line-number': Path 'path-name' is ambiguous Facility: CDU, Command Definition Utility Explanation: CDU encountered a DISALLOW clause that referenced an ambiguous path. All DISALLOW path references must not be defined ambiguously. User Action: Edit the CLD file so that all DISALLOW path references are not ambiguous.
PATHLOST
path to network partner node lost Facility: SYSTEM, VMS System Services Explanation: The path to the remote node is lost due to too much network activity or communications problems. User Action: Wait, then check to see if the node is still reachable.
PATHTLONG
too many qualifiers on name Facility: PATCH, Patch Utility Explanation: You entered a path name consisting of more than 15 elements. User Action: Remove excess elements and retry.
PATHUNDEF
line 'line-number': Path 'path-name' refers to undefined verb or syntax Facility: CDU, Command Definition Utility Explanation: CDU encountered a DISALLOW clause which referenced an undefined verb or syntax. All DISALLOW references must be previously defined. User Action: Edit the CLD file so that all DISALLOW references are defined.
PATHUNRES
line 'line-number': Path 'path-name' cannot be resolved Facility: CDU, Command Definition Utility Explanation: CDU encountered a DISALLOW clause that referenced an undefined path. All DISALLOW references must be previously defined. User Action: Edit the CLD file so that all DISALLOW references are defined.
PATOVER
pattern stack overflow Facility: VAXTPU, VAX Text Processing Utility Explanation: A pattern that is being executed exceeds the maximum number (30) of active alternates. User Action: Reduce the number of active alternates.
PBDIN_USE
operation invalid while pasteboard is buffered Facility: SMG, Screen Management Facility Explanation: The operation you have tried to perform is not legal while output to the pasteboard is being batched. For example, you cannot change the pasteboard characteristics while the pasteboard is batched. User Action: Turn off pasteboard batching before attempting the operation. You may turn batching on again after the operation.
PBF
invalid prompt buffer Facility: RMS, VMS Record Management Services Explanation: The prompt buffer address of the RAB specifies an area of memory that cannot be read by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly. Specifically, check the address specified for the prompt buffer.
PC1
'filespec' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This message should never be displayed. User Action: Submit a Software Performance Report (SPR).
PC2
'n' index record[s] written to '.BRN filespec' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This informational message results from the use of /LOG. User Action: None.
PC3
'n' table-of-contents records written to '.BRN filespec' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This informational message results from the use of /LOG. User Action: None.
PDQUALERR
more than one display type qualifier specified for PROCESSES class Facility: MONITOR, Monitor Utility Explanation: The MONITOR command specified more than one of the display type qualifiers (/TOPBIO, /TOPCPU, /TOPDIO, /TOPFAULT) for the PROCESSES class. Only one of these qualifiers may be specified for each MONITOR request. User Action: Reenter the MONITOR command, specifying only one display type qualifier for the PROCESSES class.
PEAKUTIL
this product requires 'number' blocks during installation. Facility: VMSINSTAL, Install Procedures Explanation: The installation procedure for the product determined that there are not enough free blocks on the system disk to install the product. User Action: Do the following: 1. Purge and delete files to make more space on the system disk. 2. Try to install the product again.
PENDING
asynchronous operation not yet completed Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont input routine indicating the requested function is accepted but not completed. User Action: None.
PENDING
asynchronous operation not yet completed Facility: RMS, VMS Record Management Services Explanation: The program requested a VMS RMS asynchronous I/O operation; the operation is initiated but is not completed. This message is a success status code. User Action: None.
PERMSYM
deletion of permanent symbols not allowed Facility: CLI, Command Language Interpreter (DCL) Explanation: You are trying to delete or redefine a permanent symbol. Permanent symbols are $STATUS, $SEVERITY, and $RESTART. Permanent symbol deletion is invalid. User Action: Do not try to delete or redefine these symbols.
PES
partial escape sequence Facility: RMS, VMS Record Management Services Explanation: The user buffer filled before a complete escape sequence is entered. The remainder of the escape sequence will be returned with the next input operation. User Action: Increase the size of the user record buffer to allow for escape sequences, or modify the program, if necessary, to recognize and respond to the condition.
PEXFULL
process exhaustion list full; requestor PID: 'pid' Facility: AUDSRV, Audit Server Explanation: The audit server process exclusion list is full. User Action: Use the SET AUDIT/NOEXCLUDE command to remove existing entries, and try again.
PFMBSY
page fault monitor is in use Facility: SYSTEM, VMS System Services Explanation: The page fault monitor has already been activated for your process or group. User Action: Request the page fault monitor only once per image invocation, or wait until the other user finishes.
PFNLISTCNT
inconsistent PFN list count Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PFNREFNZRO
PFN reference count nonzero Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PGFGBLBAD
pagefault, global page table entry bad format Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PGFIPLHI
pagefault with IPL too high Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PGFLOCBAD
pagefault, location field has bad value Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PHANOTFND
phase not found Facility: SMI, System Management Integrator/Server Explanation: A search for startup components running in a given phase found no matching entries. User Action: Reenter the command with a different /PHASE argument.
PHYDEVGEO
device type of 'device-name' does not match input Facility: BACKUP, Backup Utility Explanation: In an operation with the /PHYSICAL qualifier, the output device must be the same type as the input device. User Action: Reevaluate the operation; perhaps another mode of operation, such as using the /IMAGE qualifier, is appropriate. Or retry the operation specifying the same type of device.
PHYFILSPE
the /PHYSICAL specification must have only device name Facility: BACKUP, Backup Utility Explanation: When you used the /PHYSICAL command qualifier, you specified more than a device name as an input-specifier or output- specifier. The file specification for a volume to be processed with the /PHYSICAL qualifier must contain only a device name. User Action: Refer to the VMS Backup Utility Manual for information on the /PHYSICAL command qualifier and reenter the command.
PHYSET
physical save set supplied to nonphysical operation Facility: BACKUP, Backup Utility Explanation: You cannot use a save set created with the /PHYSICAL qualifier as input to an operation without specifying the /PHYSICAL qualifier. User Action: Use the DCL command BACKUP/LIST to determine how the save set is created. Reevaluate the operation, and reenter the command. Please answer Y(es), N(o), Q(uit), or A(ll) Facility: EDT, EDT Editor Explanation: This prompt occurs when you have selected the QUERY qualifier and have failed to answer with one of the above in response to the question mark (?) prompt. User Action: Respond to the prompt using either Y, N, Q, or A.
PLG
error detected in file's prolog (reconstruct file) Facility: RMS, VMS Record Management Services Explanation: The contents of the file have been corrupted because the file's prolog has been damaged. User Action: Reconstruct the file.
PLV
unsupported prolog version Facility: RMS, VMS Record Management Services, and CONVERT, Convert Utility Explanation: The version number field in the file's prolog read on open indicates that the file cannot be processed by this version of VMS RMS. User Action: Verify the version of VMS RMS that you are using; use the correct version to process the file.
PLV
unsupported prolog version Facility: CONVERT, Convert/Reclaim Utility Explanation: You have specified a Prologue 1 or Prologue 2 indexed file; CONVERT/RECLAIM works only with Prologue 3 indexed files. User Action: Specify a Prologue 3 file, or else use the CONVERT utility to reorganize the Prologue 1 or 2 file.
POOLEXPF
pool expansion failure Facility: SYSTEM, VMS System Services Explanation: Pool expansion failure occurs when the system runs out of nonpaged pool and there are not sufficient free pages for pool expansion. User Action: Examine the status of the small packet (SRP), I/O request packet (IRP), and large packet (LRP) lookaside lists, as well as pool status. Use the DCL command SHOW MEMORY/POOL/FULL to display memory status. You can extend the lists or pool by resetting the appropriate SYSGEN parameters. If you suspect disk fragmentation, use the Backup Utility to compress the disk. Port Error Bits Set - CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 attempts, it marks the device off line. User Action: Check the error logs for a sanity timeout. This sanity timeout is indicated by bit 6 of the PSR (PSR = 'xxxxxx4x'). The error logs describe the sanity timeout bit as a "Maintenance Timer Expiration." If sanity timeouts occur, check the console log to see whether the operator has halted and continued the system for any reason. If the console log does not show operator intervention, increase the PASTIMOUT SYSGEN parameter until the timeouts no longer occur. For nontimeout errors, call the Digital Services Group to check the port hardware. Port has Closed Virtual Circuit Facility: VAXport, VAXport Driver Explanation: The VAXport driver closes the virtual circuit that the local VAXport opened to the remote port. User Action: Check the PP$DB_STATUS field of the error log entry to see why the virtual circuit is closed. This error is normal if the remote system crashed or is shut down. Port is going off line Facility: VAXport, VAXport Driver Explanation: The port driver has halted port operations because of an unrecoverable error or because the retry count has been exceeded. User Action: Examine the accompanying messages to determine the reason for the port shutdown. Take the necessary corrective action and reboot the system. Port Power Down Facility: VAXport, VAXport Driver Explanation: The port driver detected a power down interrupt from the port. User Action: Call the Digital Services Group to check the port power supply. Port Power Up Facility: VAXport, VAXport Driver Explanation: The port driver logs this event. User Action: None. Port timeout Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 attempts, it marks the device off line. User Action: Call the Digital Services Group to check the port hardware, the CI cable, and the node number configuration. Port Transition Failure - CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Call the Digital Services Group to check the port hardware. Port ucode not at current rev level. PROM/RAM rev is 'xxxx/xxxx' Facility: VAXport, VAXport Driver Explanation: The port driver continues port operation. User Action: Check the console storage device for the latest microcode version. For ports with on-board microcode, call the Digital Services Group to upgrade the port microcode. Prolonged operation of the port with obsolete microcode is not supported by Digital.
PORTRXERR
port receive error Facility: REM, Set Host Facility Explanation: The outgoing terminal line detected an error. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
POS
invalid key position (greater than MRS) for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The position of a key segment specified by a key definition XAB is greater than the maximum record size specified for the file. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
POSERROR
error positioning 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to reposition the specified file. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
POSITERR
error positioning 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to reposition the specified save set volume. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
POWERFAIL
power failure occurred Facility: SYSTEM, VMS System Services Explanation: A power failure occurred while a request is active or the device is powered down. If this message is associated with a status code returned by a request to an LPA11-K driver, a power failure occurred while a request is active. (Only for the start microprocessor, initialize LPA11-K, set clock, and start data transfer request functions.) User Action: If appropriate, rerun the program.
PRACCREM
proxies to 'user name' removed Facility: AUTHORIZE, Authorize Utility Explanation: Proxy access records for the specified user have been removed from the network authorization file. When a user name in the system user authorization file (SYSUAF.DAT) is removed, any corresponding records in the network authorization file (NETPROXY.DAT) are automatically removed at the same time. User Action: None.
PRACREN
proxies to 'user name' renamed Facility: AUTHORIZE, Authorize Utility Explanation: Proxy access records for the specified user have been renamed to the new user name. When a user name in the system user authorization file (SYSUAF.DAT) is renamed, any records in the network authorization file (NETPROXY.DAT) for the original user name are automatically renamed to the new user name. User Action: None.
PRCREAT
error creating process Facility: JBC, Job Controller Explanation: The job controller encountered an error in creating a process for a terminal that is attempting to log in. This failure usually occurs when there are no more process slots available in the system to create a new process. User Action: Try again later when fewer users are competing for system resources. Also, notify the system manager of this situation.
PREDEFREP
previous key-definition replaced Facility: SMG, Screen Management Facility Explanation: A previous key definition is replaced by a new definition. User Action: None.
PREMATUREEOF
premature end-of-file detected Facility: VAXTPU, VAX Text Processing Utility Explanation: The program parsed correctly until the compilation stopped. However, the compilation stopped because the end of the program is reached prematurely (for example, before a closing ENDPROCEDURE statement). User Action: Correct the program format and then recompile.
PREMEOF
premature end-of-file encountered in options file 'filename' Facility: LINK, Linker Utility Explanation: The options file ended before the end of a continued line is found. User Action: Correct the options file and relink.
PREMEOF
premature end-of-file on /INPUT file Facility: MONITOR, Monitor Utility Explanation: The input recording file is either empty or does not contain the required control information because the MONITOR request that created the file is canceled prematurely. For example, a MONITOR request with a future beginning time could cause the process to hibernate and then get canceled. User Action: Verify that the file specified with the /INPUT qualifier is the MONITOR recording file you desired. Then, reenter the MONITOR request.
PREMMSG
record removed from NETPROXY.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The record specifed in the AUTHORIZE command REMOVE /PROXY has been removed from the network user authorization file. User Action: None.
PRESENT
entity value is present in command string Facility: CLI, Command Language Interpreter (DCL) Explanation: This status is returned by the CLI$PRESENT CLI interface routine to indicate that the specified entity is explicitly present in the command line. User Action: None.
PREVDUPACE
previous ACE will supercede current ACE - not entered Facility: ACLEDIT, Access Control List Editor Explanation: An ACE already exists prior to the current position within the ACL and supersedes the ACE about to be entered, rendering it useless. The current ACE is not entered. User action: Modify the current ACE (or delete it), or modify the previous ACE.
PREVINIT
patch area has previously been initialized Facility: PATCH, Patch Utility Explanation: The patch area descriptor for the specified user- defined patch area has previously been initialized. PATCH set the patch area to the area named in the SET PATCH_AREA command, but did not initialize a new descriptor. User Action: Continue to enter patches into the user-defined patch area. To see the current status of the patch area, issue the SHOW PATCH_AREA command. In the future, do not use the /INITIALIZE qualifier if the descriptor has already been initialized.
PRIIHDBAD
invalid primary index file header, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The primary index file header on the specified relative volume is corrupted. The utility refreshes the primary index file header from the alternate index file header. User Action: None.
PRIMIN
error code of 'xx' parsing input file Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry.
PRIMNOSTP
PRIMARY CPU cannot be stopped Facility: SYSTEM, VMS System Services Explanation: The STOP/CPU command was used to stop a CPU, but the CPU cannot be stopped for one of the following reasons: 1) this is the only CPU in the system, 2) this is the primary CPU and primary switching is not supported by this system, or 3) the primary CPU owns a capability which no other CPU in the system owns. User Action: If the primary cannot be stopped because of capability ownership, and the system supports primary switching, the primary CPU can be stopped using the STOP/CPU/OVERRIDE_CHECKS qualifier.
PRIMOUT
error code of 'xx' parsing journal file Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed due to the error represented as 'xx'. User Action: Correct the error (represented as 'xx') and retry. Print file could not be closed Facility: EDT, EDT Editor Explanation: EDT opened the output file and copied the text specified with the PRINT command into that file. However, for some reason at the system level, EDT is unable to close that file. User Action: Correct the problem indicated by the accompanying message. Print file could not be created Facility: EDT, EDT Editor Explanation: EDT could not create the output file with the file specification you supplied with the PRINT command. This error can be caused by problems in the file name itself (either it has too many characters or an invalid character). Other causes include problems in the directory specification, if you used one (either the directory does not exist, you do not have access to it, or the directory specification format is incorrect). This message could also mean that there is a problem with the file system, such as insufficient disk space. User Action: Correct the problem indicated by the accompanying message.
printer Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "PRINT" class operations. User Action: None.
PRIOSMALL
scheduling priority has smaller value than requested Facility: JBC, Job Controller Explanation: A user without ALTPRI or OPER privilege specified a value for a job's priority that exceeded the queue's maximum priority for nonprivileged users. The job is entered in the queue, but its scheduling priority is lower than the value requested by the user. User Action: Use SHOW ENTRY/FULL to see the priority assigned to the job. If you must specify a higher scheduling priority, acquire the necessary privileges and use the DCL command SET ENTRY/PRIORITY to modify the job's priority, or see your system manager.
PRISECMAP
private terminal table used Facility: SMG, Screen Management Facility Explanation: The requested terminal definition is found in the caller's private copy of Termtable. User Action: None.
PRIV
privilege error Facility: CNF, NI Configurator Explanation: NICONFIG is executing without all the necessary privileges. User Action: See the accompanying messages for the missing privileges. Install NICONFIG with all the required privileges or run from an account with all the required privileges.
PRIVINSTALL
shareable images must be installed to run privileged image
Facility: SYSTEM, VMS System Services
Explanation: Two possible reasons for this error follow:
o You tried to run a privileged image with uninstalled shareable
images.
o You referenced an uninstalled shareable image when the main
program is installed with the /EXECUTE_ONLY qualifier.
User Action: Ask the system manager to install all shareable
images used by executable images.
PRMEOF
premature end-of-file Facility: SUMSLP, SUMSLP Batch Editing Utility Explanation: A SUMSLP command file terminated unexpectedly. This is probably due to the absence of a terminator (/) at the end of the command file. User Action: Insert a terminator (/) at the end of the command file and edit again.
PRMLEN
parameter too long Facility: NCP, Network Control Program Explanation: A parameter string or value has too many characters. User Action: Reenter the command with appropriate parameter information.
PRMLON
parameter too long 'text' Facility: NCP, Network Control Program Explanation: A parameter value is too long for the implementation to handle. The 'text' part of the message identifies the low and high bytes of the parameter type number. User Action: Reduce the length of the parameter.
PRMMS
parameter missing 'text' Facility: NCP, Network Control Program Explanation: A required parameter in your command is missing. The 'text' part of the message identifies which parameter is missing. User Action: Review the command description and reenter your command with the correct parameter.
PRMNA
parameter not applicable 'text' Facility: NCP, Network Control Program Explanation: Your parameter is not applicable to the component specified in the message. For example, you may have set a tributary address for point-to-point line or attempted to set a controller to loopback mode when the controller does not support that function. The 'text' part of the message identifies the parameter type. User Action: Review the command description and reenter the command with the correct parameter.
PRMRNG
parameter value out of range, 'parameter' Facility: NCP, Network Control Program Explanation: A numeric parameter value has an invalid range. The 'parameter' part of the message identifies which value is incorrect. User Action: Reenter the command with an appropriate parameter value.
PRO
invalid process identification Facility: NCP, Network Control Program Explanation: The format of the process identification is incorrect. User Action: Check the syntax rules for process identifiers and reenter your command with the correct process identifier.
PROCDONE
operation completed. Processing finished at 'date-time' Facility: BACKUP, Backup Utility Explanation: Standalone BACKUP processing has completed. User Action: None.
PROCESSEND
subprocess terminated Facility: VAXTPU, VAX Text Processing Utility Explanation: A VMS subprocess that is successfully activated has been stopped. This condition can be caused by leaving VAXTPU, deleting the process, entering a LOGOUT command while in the subprocess, or having the subprocess stopped by another system user. User Action: None.
PROCFILE
processing file 'filename' Facility: DSR, DIGITAL Standard Runoff Explanation: This informational message indicates that DSR has begun processing the file. User Action: None.
PROCGONE
Process not in system Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PROC_ID
identification of created process is 'process-ID' Facility: RUN, Run Detached Utility Explanation: The newly created process has an identification number of 'process-ID'. This is an informational message. User Action: None.
PROCINDEX
error processing index file on 'device,' RVN 'n' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to process the index file, [000000]INDEXF.SYS;1, on the specified relative volume of the specified device. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
PROCSUPERSEDED
definition of procedure 'name' superseded Facility: VAXTPU, VAX Text Processing Utility Explanation: The procedure you are defining already had a definition. The new definition you supplied replaces the old one. User Action: None.
PRODNOTINS
optional software product 'name' not installed Facility: Shared by several facilities Explanation: The specified optional software product is not installed on your system. User Action: Install the requested software.
PRODSKIP
Products that have not been installed will be skipped. Facility: VMSINSTAL, Install Procedures Explanation: You requested that multiple products be installed, but one of these products requires that the system be rebooted after its installation. To accomplish this, the remaining uninstalled products must be skipped. User Action: Install the remaining products after the system is rebooted.
PROERR
error protecting 'filename' Facility: SET, SET Facility Explanation: An error occurred when the file's protection was set. User Action: Take corrective action based on the accompanying message.
PROERR
prolog checksum error at VBN = 'nnn' Facility: CONVERT, Convert Utility and CONVERT, Convert/Reclaim Utility Explanation: The specified block of the file's prolog has been corrupted. This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error described in the RMS error message and try again.
PROGLOST
program lost - Sorry Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
PROL_WRT
prolog write error Facility: CONVERT, Convert Utility, CONVERT, Convert/Reclaim Utility Explanation: This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error described in the RMS error message and try again.
PRONOTCHG
protection on 'filename' not changed Facility: SET, SET Facility Explanation: The protection on the file is not changed. User Action: Take corrective action based on the accompanying message.
PROTECTED
ACE cannot be modified Facility: ACLEDIT, Access Control List Editor Explanation: The current ACE is protected against deletion. This is usually because it is an application ACE or it is marked hidden. User Action: None.
PROTECTED
'filename' file protection changed to 'protection' Facility: SET, SET Facility Explanation: The file protection has been successfully changed. This message is displayed when a SET FILE/PROTECTION command is entered with the /LOG qualifier. User Action: None.
PROTECTED
protection on 'filespec' changed to 'protection-string' Facility: Shared by several facilities Explanation: This informational message is associated with the execution of a DCL command SET PROTECTION. The protection of the named file is changed to the value specified. User Action: None.
PROTERR
internal protocol error Facility: REM, Set Host Facility Explanation: A system internal error has occurred. User Action: Submit a Software Performance Report (SPR).
PROTINSTALL
protected images must be installed Facility: SYSTEM, VMS System Services Explanation: Protected images must be installed. User Action: Use the /PROTECT qualifier to install a shareable image that contains user-written system services.
PROTMIS
server and host not running same SMI protocol version Facility: SMI, System Management Integrator/Server Explanation: Incompatible versions of SYSMAN and SMISERVER exist in the environment. Operation continues on the next node in the environment. User Action: Ensure that all nodes participating in a SYSMAN operation are running compatible versions of the VMS operating system or SMISERVER, or both.
PROTOCOL
network protocol error Facility: SYSTEM, VMS System Services Explanation: An error occurred attempting to initiate a DECnet-VAX logical link connection. User Action: Notify your software specialist. Refer to the VMS Networking Manual for additional information.
PROTOCOL
remote protocol error - data packet w/o INIT Facility: SMI, System Management Integrator/Server Explanation: This message indicates an internal error. SMI is trying to use a remote link without sending an initialize packet. User Action: Submit a Software Performance Report showing all SYSMAN commands leading to this error.
PROTOOLON
prompt-string is too long Facility: Shared by several facilities Explanation: The length of a prompt string exceeded 512 characters. User Action: Shorten the prompt string to 512 characters or fewer.
PRTEXT
file only partially extended. Volume may be too fragmented. Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN command CREATE failed. You have insufficient disk space. User Action: Clean up your disk space or specify a smaller /SIZE qualifier.
PRV
insufficient privilege or file protection violation
Facility: RMS, VMS Record Management Services
Explanation: One of the following has occurred:
o Your process does not have one or more of the privileges
necessary to perform the requested file access
o Your process is denied access to the file because of the
protection applied to the file or to the directory in which
the file is listed
User Action: Verify the protection applied to the file (using the
DIRECTORY/FULL command), and change the protection if necessary
(using the SET PROTECTION command). If you cannot change the
protection, ask the system manager or the owner of the file to
change it.
If the file's current protection should permit the desired access,
verify the protection applied to the directory in which the file
is listed.
If the preceding actions do not apply or fail to solve the
problem, ask the system manager for the necessary privileges.
PRVNOTFND
invalid privilege name Facility: AUTHORIZE, Authorize Utility Explanation: You specified an invalid privilege name. User Action: See the VMS Authorize Utility Manual for information on valid privilege names.
PRVNOTUNQ
privilege name 'name' is not unique Facility: INSTALL, Install Utility Explanation: You entered an abbreviation for a privilege name that is not unique. User Action: Specify at least 4 characters for the privilege name and retry.
PRVNOTUNQ
privilege name not unique Facility: AUTHORIZE, Authorize Utility Explanation: You did not specify enough characters of a privilege name to make it unique. User Action: Enter at least the first 4 characters of a privilege name.
PRVVIO
privilege violation Facility: NCP, Network Control Program Explanation: You do not have the privilege to perform the requested function. Privileges are required to perform all NCP commands, except for the following: HELP, CLEAR EXECUTOR NODE, LOOP EXECUTOR, LOOP LINE, LOOP NODE, SET EXECUTOR NODE, SHOW, and TELL. To use the PURGE, DEFINE, and LIST commands, you must have system privilege (SYSPRV) or have access to the files with the system protection. The remaining NCP commands require the operator privilege (OPER). User Action: None, unless your system manager gives you the required privilege.
PSCALI
psect 'psect-name' alignment ('decimal-number') illegal in module
'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: A module specified an illegal alignment for a psect.
User Action: Submit a Software Performance Report on the
appropriate language translator.
PSCNXR
transfer address is not in executable, relocatable psect in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The transfer address for a module is not in an executable, relocatable psect. User Action: Move the transfer address into an executable, relocatable psect.
PSECBUFOVF
PSECT context buffer overflow Facility: MACRO, VAX MACRO Assembler Explanation: The .SAVE_PSECT directive attempted to save a program section context when the program section context buffer is filled. A maximum of 31 program section contexts can be saved in the buffer. User Action: Reduce the amount of program section nesting.
PSECBUFUND
PSECT context buffer underflow Facility: MACRO, VAX MACRO Assembler Explanation: The .RESTORE_PSECT directive attempted to restore a program section context when the program section context buffer is empty. User Action: Ensure that each .RESTORE_PSECT directive corresponds to a .SAVE_PSECT directive.
PSECOPCNFL
conflicting PSECT options Facility: MACRO, VAX MACRO Assembler Explanation: The values specified in a .PSECT directive conflicted with each other or were not the same as the values specified in a preceding .PSECT directive that specified the same program section name. User Action: Correct the conflicting values in the .PSECT directives.
PSTFULL
process section table is full Facility: SYSTEM, VMS System Services Explanation: The section table in the process header is full. Additional sections cannot be created for this process. User Action: Relink the image, forcing fewer image sections, or reboot, increasing the SYSGEN parameter PROCSECTCNT.
PSUSPECT
customer defined text Facility: LAVC, Local Area VAXcluster Explanation: The local area VAXcluster network failure analysis has located a network problem and reported this network component as the primary suspect. User Action: Several PEDRIVER channels that were using this network component have failed. The analysis indicates that this component or something connected to it is the most likely cause of the network problems. Have the system manager or network manager look into the network problem.
PTELENVIOL
unexpected page table length violation Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PTRCNT
ACP block count exceeds retrieval pointer size Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PURABO
purge aborted due to errors Facility: NCP, Network Control Program Explanation: The purge requested by the WITH option of the NCP command COPY is aborted. The local node database is not affected. User Action: See previous error messages to determine why the purge is aborted.
PURGEVER
version numbers not permitted Facility: Shared by several facilities Explanation: The command does not allow version numbers in a file specification. User Action: Reenter the command; do not specify a version number for the file specification.
PURGWSSCN
purge working set scan error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
PUSSTAOVE
pushdown stack overflow Facility: LIB, Library Facility Explanation: The image pushdown stack overflowed. User Action: Use the debugger to determine whether the procedure stack does not contain an excessive number of entries, or if an infinite call loop has caused the stack to grow.
PUTERR
put error Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
PUTERR
put error code of 'xx' on file 'filespec' Facility: PATCH, Patch Utility Explanation: An error writing the specified file occurred due to the error code represented as 'xx'. User Action: Correct the error code (represented as 'xx') and retry.
PWDINDIC
password found in system dictionary; please choose another string Facility: SET PASSWORD Command Explanation: To help enforce the use of secure passwords, VMS does not allow you to select words that are contained in the system password dictionary. The system password dictionary contains approximately 50,000 English words. User Action: Choose a new character sequence or use a generated password.
PWDINHIS
password found in history list; please choose a new password Facility: SET PASSWORD Command Explanation: To help enforce the use of secure passwords, VMS does not allow you to reuse a password that you have used in the past. VMS maintains a list of your last 100 passwords. User Action: Choose a new character sequence or use a generated password.
PWDLOCKED
password is locked to prevent change Facility: SET, SET Facility Explanation: This message is returned by the command line interpreter for the DCL command SET PASSWORD. The system manager restricted an account from changing its password. Typically, this is done for demonstration accounts which may be accessed by a large number of users. User Action: If the user requires that the account not be restricted from changing its password, consult the system manager.
PWDNCH
password not changed Facility: AUTHORIZE, Authorize Utility Explanation: An error occurred using the random password generator to generate an account password. User Action: None.
PWDNOL
password not on list; try again Facility: AUTHORIZE, Authorize Utility Explanation: The password you specified is not one of those listed. User Action: Select another password and try again.
PWDNOTDIF
new password must be different from current password Facility: SET, SET Facility Explanation: The new password that you specified is the same as the old password. User Action: Change the password and reenter the command.
PWDNOTVAL
old password validation error - password unchanged Facility: SET, SET Facility Explanation: This message is returned by the command line interpreter for the DCL command SET PASSWORD. An old password validation error is detected. The user is required to enter the old password to help protect an unattended process. The old password may have been mistyped. User Action: Reenter the old password. If the old password has been forgotten, consult the system manager.
PWDNOTVER
new password validation error - password unchanged Facility: SET, SET Facility Explanation: This message is returned by the command line interpreter for the DCL command SET PASSWORD. The new password was not entered the same way twice. Entering the password twice ensures that the password intended by the user is properly entered. User Action: Repeat the entire sequence correctly.
PWDSYNTAX
illegal password syntax
Facility: SET, SET Facility
Explanation: An illegal password is used. Passwords may contain
from 1 through 31 characters. The valid characters are the
following:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
User Action: Reenter the password, using valid characters.
PWDSYNTAX
invalid password syntax Facility: AUTHORIZE, Authorize Utility Explanation: You entered a password using incorrect syntax. User Action: Enter a password using 1-31 alphanumeric characters, the dollar sign ($), or the underscore (_) characters.
PWDWEAK
password is too easy to guess; please choose another string Facility: SET PASSWORD Command Explanation: To help enforce the use of secure passwords, VMS does not allow you to choose certain passwords that are too easy to guess. In addition, your site security administrator may choose to further restrict your choice of passwords. User Action: Choose a new character sequence or use a generated password.
PWF
page number will not fit on title Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The title (on the first header information line) extends into the page number field, so that the page number will not fit. User Action: Reduce the length of the title.
QEMPTY
queue empty Facility: Shared by several facilities Explanation: If returned from a DR32 support routine call, the termination queue is empty but the transfer is still in progress. User Action: Continue trying to remove a command packet from the termination queue until you are successful or the transfer completes.
QFACTIVE
disk quota file is already active Facility: SYSTEM, VMS System Services Explanation: The quota file is already active. User Action: Check the device specified and proceed.
QFNOTACT
disk quota file is not active Facility: SYSTEM, VMS System Services Explanation: The quota file is not active. User Action: Check the device specified, or check the default device. Turn quotas on, if appropriate.
QIOBFOVF
QIO buffer overflow Facility: MOM, Maintenance Operation Module Explanation: An internal buffer used to obtain network management information is sized inadequately. This is a program logic error and should be reported. User Action: Submit a Software Performance Report (SPR).
QIOERR
internal QIO error Facility: REM, Set Host Facility Explanation: A system internal error has occurred. User Action: Submit a Software Performance Report (SPR).
QMANCREPRC
queue manager process could not be created Facility: JBC, Job Controller Explanation: The job controller could not create a queue manager process. An accompanying message gives information about why the process could not be created. One possible cause is too few process slots on the node. User Action: Correct the problem described in the accompanying message and try to restart the queue manager.
QMANDEL
unexpected queue manager process termination Facility: JBC, Job Controller Explanation: A queue manager process exited without being requested to do so. An accompanying message gives information about why the process terminated. User Action: Take action based on the accompanying message.
QMANNOTSTARTED
queue manager could not be started Facility: JBC, Job Controller Explanation: A START/QUEUE/MANAGER request failed to complete successfully. User Action: Check the console or operator log file for messages from the JOB_CONTROL or QUEUE_MANAGE username explaining why the queue manager could not be started. If you included the directory specification with the START/QUEUE/MANAGER command, verify that you specified the correct directory.
QST
Quoted string too long: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: A quoted text value contains too many characters. User Action: Reduce the number of characters. In some cases, only one quoted character is allowed (for example, the .DISPLAY ELEMENTS command). In other cases, up to 150 characters are allowed (for example, the .REPEAT command).
QUALINV
'class-name-qualifier' qualifier not valid for 'class-name' class Facility: MONITOR, Monitor Utility Explanation: An attempt is made to combine a class name with a qualifier for which it is not valid. Class name qualifiers are valid only for a subset of MONITOR classes. User Action: Check the valid combinations of class-names and class-name qualifiers by entering the DCL command similar to the following: HELP MONITOR class_name_qualifiers Then, reenter the MONITOR request.
QUALOBS
qualifier obsolete - '/qualifier' ignored Facility: LAT, LAT Facility Explanation: The specified LATCP command qualifier is obsolete and has no effect. The rest of the command is executed. User Action: Do not specify this qualifier in future commands.
QUEAUTOOFF
queue 'queue-name' is now autostart inactive Facility: QMAN, Queue Manager Explanation: The specified autostart queue has been stopped without a user request. The queue manager will not restart the queue until a user enters the START/QUEUE command for the queue. User Action: An accompanying message explains why the queue stopped. Correct the problem and try to restart the queue.
QUE_CLOSED
queue closed, jobs not accepted Facility: JBC, Job Controller Explanation: You attempted to enter or requeue a job to a queue that is marked closed. A closed queue cannot accept new jobs, but it will continue to process jobs already entered. User Action: Put the queue into an open state by using the /OPEN qualifier with the SET QUEUE, START/QUEUE, or INITIALIZE/QUEUE commands and retry your request.
QUEDISABLED
disabled queue cannot be modified, nor can jobs be submitted to it Facility: JBC, Job Controller Explanation: The queue manager disabled the queue upon detection of database corruption. User Action: Ask the system manager to delete and recreate the queue to which your command was directed.
QUEFORMAT
system job queue file has invalid format Facility: JBC, Job Controller Explanation: The job controller detected an error in the format of the system job queue file. The nature of the queue file corruption is such that the job controller is not able to repair the damage and continue operation using this queue file. User Action: Create a new queue file using the START/QUEUE/MANAGER /NEW_VERSION command or delete the existing queue file and create a new file using the START/QUEUE/MANAGER command.
QUEisEMP
queue is empty Facility: LIB, Library Facility Explanation: The queue is empty, and is not modified. User Action: None.
QUENOTMOD
modifications not made to running queue Facility: JBC, Job Controller Explanation: You tried to change a feature of the queue that can be changed only when the queue is in the stopped state. User Action: Enter a STOP/QUEUE/RESET or STOP/QUEUE/NEXT command, then reenter your original command when the queue is in the stopped state.
QUENOTSTART
queue 'queue-name' could not be started on node 'node-name' Facility: QMAN, Queue Manager Explanation: An error occurred while trying to start the specified autostart queue on the specified node. User Action: An accompanying message explains why the operation failed. Correct the problem and try to start the queue again.
QUENOTSTOP
queue must be stopped to perform operation Facility: JBC, Job Controller Explanation: A queue management operation that requires the queue to be in a stopped state was attempted while the queue was in another state. Deleting a queue is such an operation. User Action: Enter a STOP/QUEUE/RESET command to stop the queue, then reenter the original request.
QUERESET
job aborted during execution because queue was reset Facility: JBC, Job Controller Explanation: The queue is reset with a STOP/RESET command during execution of the affected job. User Action: Resubmit the job.
QUEUEMPTY
scheduling queue empty Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
QUITTING
editor quitting Facility: VAXTPU, VAX Text Processing Utility Explanation: You are exiting the VAXTPU image editing session. When you quit an editing session, the edits you made during the session are not saved. User Action: None.
QUO
error in quoted string Facility: RMS, VMS Record Management Services Explanation: The quoted foreign file specification string or the quoted task specification string of a file specification does not have the correct syntax. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary, if necessary, for the correct syntax and reenter the file specification.
QUOTAFAIL
failed to activate quota file; volume locked Facility: MOUNT, Mount Utility Explanation: An error occurred that enabled the volume's quota file; the volume is locked against allocation. A subsequent message describes the nature of the error. User Action: Correct the problem with the quota file. Then dismount and remount the volume.
QUOTAFILE
quota file is too small - use DISKQUOTA to rebuild Facility: BACKUP, Backup Utility Explanation: During a restore or copy operation with the /IMAGE qualifier, BACKUP found that the quota file, [000000]QUOTA.SYS;1, on the output volume is not large enough. User Action: After the restore or copy operation is complete, use the SYSMAN command DISKQUOTA REBUILD to reconstruct the quota file.
QUOTAFNF
quota file not found on volume Facility: MOUNT, Mount Utility Explanation: The MOUNT command specified /QUOTA or /CACHE=QUOTA, but there is no quota file on the volume. User Action: Create a quota file on the volume using the SYSMAN command DISKQUOTA CREATE. Quoted string required Facility: EDT, EDT Editor Explanation: A required quoted string is not supplied for the command you entered. An up arrow (^) indicates the position of the required quoted string. User Action: Reenter the command supplying the required quoted string.
RAB
invalid RAB or RAB not accessible Facility: RMS, VMS Record Management Services Explanation: The block identifier field of the record access block for a file does not indicate that this is a RAB. Or the RAB is not in an area of memory that can be written by the caller. An attempt may have been made to perform record operations to a FAB. User Action: Verify that the control block referred to is a RAB, that the RAB is properly initialized, and that it is not inadvertently modified during execution of the program.
RAC
invalid record access mode Facility: RMS, VMS Record Management Services Explanation: The record access mode (RAC) field of the RAB indicates an invalid record access mode. The field must contain either SEQ, KEY, or RFA. User Action: Verify that the call to the VMS RMS service is coded correctly.
RADRMOD
reserved addressing fault at PC 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An instruction specifies an addressing mode that is illegal within the context of its use. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine the instruction that caused the error. Range for RESEQUENCE must be contiguous Facility: EDT, EDT Editor Explanation: The range specification for the EDT command RESEQUENCE did not contain contiguous lines. User Action: Reenter the command specifying contiguous lines for the range. Range specified by /SEQUENCE would cause duplicate or non-sequential numbers Facility: EDT, EDT Editor Explanation: You have range specifications in the EDT command RESEQUENCE that would cause duplicate or nonsequential numbers. User Action: Modify the range specifications and reenter the command.
RAT
invalid record attributes Facility: RMS, VMS Record Management Services Explanation: The record attributes field of the FAB specified for a $CREATE or a $OPEN operation contains a value other than BLK, CR, FTN, or PRN, or an invalid combination is specified. User Action: Verify that the call to the VMS RMS service is coded correctly.
RAWFMT
an invalid raw event is seen and ignored Facility: EVL, Event Logger Explanation: NETACP obtained an invalid unprocessed event. The size of the event exceeded the buffer size. This is probably caused by a software error. User Action: Submit a Software Performance Report (SPR).
RBF
invalid record buffer Facility: RMS, VMS Record Management Services Explanation: The record buffer address of the RAB specifies an area of memory that cannot be correctly accessed by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly.
RCTUNRSZR
RCT unreadable, output SERIALNUM field set to zero Facility: BACKUP, Backup Utility Explanation: This message warns the user that the disk's Replacement and Caching Table was unreadable. As a result, the output volume serial number is set to 0. User Action: None.
RDBADDERR
unable to add 'id-name' to RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The identifier name you specified could not be added to the rights database file (RIGHTSLIST.DAT). This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. Most likely, the identifier name already exists in the rights database file. Duplicate identifier names are not allowed in the rights database file. User Action: Correct the condition identified by the RMS message and reenter your command. If you want to change the name of an identifier in the rights database file, use the AUTHORIZE command MODIFY/IDENTIFIER.
RDBADDERRU
unable to add 'id-name' value: '[UIC]' to RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The specified identifier name and its corresponding user identification code (UIC) could not be added to the rights database file (RIGHTSLIST.DAT). This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. Most likely, the identifier name already exists in the rights database file. Duplicate identifier names are not allowed in the rights database file. This error also occurs if you copy a record in the system user authorization file (SYSUAF.DAT) without specifying a new UIC value for the copy. By default, an identifier name and corresponding UIC value for the new record are written to the rights database file (RIGHTSLIST.DAT); if the UIC has not been changed, it will conflict with the UIC of the original record, and a 'duplicate identifier' error results. User Action: Correct the condition identified by the RMS message and reenter your command. If you want to change the UIC value of an identifier in the rights database file, use the /VALUE qualifier with the AUTHORIZE command MODIFY/IDENTIFIER. If you copy a record in the system user authorization file, and you want an identifier for the new record to be added to the rights database file, use the /UIC qualifier with the AUTHORIZE command COPY.
RDBADDERRV
unable to add 'id-name' value: 'hex code' to RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The specified identifier name and its corresponding integer value (expressed as an 8-bit hexadecimal code) could not be added to the rights database file (RIGHTSLIST.DAT). This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. Most likely, the identifier name or value already exists in the rights database file. Duplicate identifier names or values are not allowed in the rights database file. User Action: Correct the condition identified by the RMS message and reenter your command. If you want to change the value of an identifier in the rights database file, use the /VALUE qualifier with the AUTHORIZE command MODIFY/IDENTIFIER.
RDBADDMSG
identifier 'id-name' value: 'hex code' added to RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: A general identifier with the specified name and value has been added to the rights database file (RIGHTSLIST.DAT). User Action: None.
RDBADDMSGU
identifier 'id-name' value: '[UIC]' added to RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: A UIC identifier with the specified name and value has been added to the rights database file (RIGHTSLIST.DAT). User Action: None.
RDBCREERR
unable to create RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The rights database file, named RIGHTSLIST.DAT, could not be created. This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. For example, you cannot create another rights database file if one already exists, unless you first delete or rename the original file. User Action: Correct the condition identified by the RMS message and reenter your command. If you want to create a new rights database file, either delete or rename the current one (if you have sufficient privilege to do so). Once the current file has been deleted or renamed, reenter your command.
RDBDONEMSG
rights database modified Facility: AUTHORIZE, Authorize Utility Explanation: The rights database file (RIGHTSLIST.DAT) has been modified. User Action: None.
RDBMDFYERR
unable to modify identifier 'id-name' Facility: AUTHORIZE, Authorize Utility Explanation: The specificied identifier could not be modified. This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. User Action: Correct the condition identified by the RMS message and reenter your command.
RDBMDFYERRU
unable to modify identifier '[UIC]' Facility: AUTHORIZE, Authorize Utility Explanation: The specified UIC identifier could not be modified. This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. User Action: Correct the condition identified by the RMS message and reenter your command.
RDBMDFYMSG
identifier 'id-name' modified Facility: AUTHORIZE, Authorize Utility Explanation: The record for the specified identifier in the rights database file has been modified according to the AUTHORIZE command MODIFY/IDENTIFIER. User Action: None.
RDBNOMODS
no modifications made to rights database Facility: AUTHORIZE, Authorize Utility Explanation: The rights database file (RIGHTSLIST.DAT) is not modified. User Action: None.
RDBREMERR
unable to remove 'id-name' from RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The specified identifier could not be removed from the rights database file (RIGHTSLIST.DAT). This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. User Action: Correct the condition identified by the RMS message and reenter your command.
RDBREMMSG
identifier 'id-name' value: 'hex code' removed from RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The general identifier with the specified name and hexidecimal value has been removed from the rights database file (RIGHTSLIST.DAT). User Action: None.
RDBREMMSGU
identifier 'id-name' value: '[UIC]' removed from RIGHTSLIST.DAT Facility: AUTHORIZE, Authorize Utility Explanation: The UIC identifier with the specified name and user identification code has been removed from the rights database file (RIGHTSLIST.DAT). User Action: None.
RDDELDATA
read deleted data address mark Facility: SYSTEM, VMS System Services Explanation: This message is associated with read operations on RX02 disk drives. A sector that has a deleted data address mark is successfully read. User Action: None.
RDSNONRES
read data substitute page nonresident Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
READABORTED
READ_CHAR, READ_KEY, or READ_LINE built-in was aborted Facility: VAXTPU, VAX Text Processing Utility Explanation: The READ_CHAR, READ_KEY, or READ_LINE built-in procedure was aborted because the user action required executing other VAXTPU code. User Action: Return control to VAXTPU in order for the other code to execute.
READATTR
error reading attributes for 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to read the file attributes of the specified file. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
READBAD
error reading bad block data on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to read the bad block data recorded on the specified volume. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
READBLOCK
error reading block 'n' of 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to read the specified block of the specified file. The accompanying message provides additional information. User Action: Examine the file for corruption and reconstruct as necessary.
READBMAP
error reading storage bitmap on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to read the storage bit map file, [000000]BITMAP.SYS;1, on the specified volume. The volume cannot be used as a save set disk. User Action: Reinitialize the volume, or select another volume and retry the operation.
READBOOT
error reading boot block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the bootstrap block from virtual block 1 of the index file, [000000]INDEXF.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: Note that the volume probably cannot be used as a system volume for a VAX-11 processor model that requires access to the bootstrap block during a bootstrap operation.
READCHECK
read error detected during check on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: While rereading a block in order to perform a data check operation, the Exchange Utility encountered an input error. User Action: This message is followed by a second message giving more specific information about the error discovered by the I/O system. Take corrective action based on the additional message.
READCHECKREC
read check error recovered on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while checking a read on the volume, but the operation succeeded on a retry. User Action: The file is read successfully, but the user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent.
READDIR
error reading directory 'directory-name' Facility: BACKUP, Backup Utility and ANALDISK, Analyze/Disk_ Structure Utility Explanation: An error was encountered during an attempt to read the specified directory file. An accompanying message provides additional information. The Backup Utility terminates processing of the directory. User Action: Examine the directory using the DCL command DIRECTORY and reconstruct files as necessary.
READERR
error reading 'filename' Facility: ACCOUNTING, Accounting Utility Explanation: An input file specified cannot be read. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
READERR
error reading 'filename' Facility: SET, SET Facility Explanation: An error occurred while attempting to read the specified file. An accompanying message explains why the error occurred. User Action: Correct the problem described in the accompanying message, and retry the command.
READERR
error reading 'filespec' Facility: MACRO, VAX MACRO Assembler Explanation: The assembler encountered an I/O error when reading an input source or macro library file; filespec is the file specification of the file being read. User Action: Retry the assembly, or create a new copy of the input file and then retry the assembly.
READERR
error reading 'filespec' Facility: Shared by several facilities Explanation: An input file specified cannot be read. This message is usually accompanied by a VMS RMS message indicating the reason for the failure. User Action: Take corrective action based on the associated message.
READERR
error reading 'input-filespec' Facility: VAXTPU, VAX Text Processing Utility Explanation: An input file cannot be read. This message should be accompanied by a VMS RMS message indicating the reason for the failure. User Action: Follow the recovery procedure for the specified VMS RMS message.
READERR
I/O error reading boot file Facility: VAXCLUSTER, VAXcluster Facility Explanation: A hardware error occurred on the satellite system disk. User Action: Check the error log for the disk. Either run diagnostics on it or call the Digital Services Group.
READERRREC
read error recovered on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while reading the volume, but the operation succeeded on a retry. User Action: The file is read successfully, but the user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent.
READERRS
excessive error rate reading 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered numerous read errors in the specified save set. The save set medium is probably unusable. User Action: Retire the save set medium.
READEVT
error reading processed event record Facility: EVL, Event Logger Explanation: An error occurred while the event receiver is reading incoming event records. As a result, an event is discarded. User Action: Submit a Software Performance Report (SPR).
READFILE
file ('file-id') 'filename' error reading VBN 'n'
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to read
the specified virtual block of the specified file while executing
the /READ_CHECK function. An accompanying message provides
additional information.
User Action: Reconstruct the file from backup media if necessary.
READHEADER
error reading file header for 'filename' Facility: DUMP, File Dump Utility Explanation: The File Dump Utility encountered an error during an attempt to read the file header for the specified file. The accompanying message provides additional information. The File Dump Utility does not display the file header. User Action: Correct the condition that caused the error and reenter the command.
READHEADER
file ('file-id') 'filename' file header read error
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt
to read the specified file header from the index file,
[000000]INDEXF.SYS;1, on the specified relative volume. An
accompanying message provides additional information.
User Action: If the specified file header is currently in use, the
file can no longer be accessed by the operating system and must
be reconstructed from backup media. If the file header is not in
use, no action is necessary because the operating system will not
attempt to use it.
READHOME
error reading home block, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the home block from the specified virtual block of the index file, [000000]INDEXF.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system using one of the alternate home blocks. If the error persists, try copying the volume to fresh media. If you specify the /REPAIR qualifier, the read error might be cleared when the utility rewrites the block.
READIBMAP
error reading index file bitmap, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the index file bitmap from the specified virtual block of the index file, [000000]INDEXF.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system. However, if the error persists, copy the volume to fresh media or reconstruct the volume from backup media. If you specify /REPAIR, the utility rewrites the specified virtual block. This action may clear the error. If the error cannot be cleared, rewrite the volume.
READIMAP
error reading index file bitmap on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to read the index file, [000000]INDEXF.SYS;1, on the specified volume. The volume cannot be used as a save set disk. User Action: Reinitialize the volume, or select another volume and retry the operation.
READJNLACE
error reading journal ACE for 'filespec' file ID 'file-id' Facility: BACKUP, Backup Utility Explanation: BACKUP could not read the journal Access Control Entry for the specified file. User Action: Determine if the ACL could not be written. This could be due to a corrupted ACL or some other hardware or software related error. Correct the problem, if possible, and retry the BACKUP operation.
READQUEHEADER
attempt to read queue header of dscb: 'address' Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
READQUOTA
error reading QUOTA.SYS, VBN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the specified virtual block of the quota file, [000000]QUOTA.SYS;1, on relative Volume 1. An accompanying message provides additional information. User Action: If necessary, correct the condition that caused the error and reenter the command.
READSBMAP
error reading storage bitmap, VBN 'n' RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the storage bit map from the specified virtual block of the storage bit map file, [000000]BITMAP.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system. However, if the error persists, copy the volume to fresh media or reconstruct the volume from backup media. If you specify the /REPAIR qualifier, the utility rewrites the specified virtual block. This action may clear the error. If the error cannot be cleared, rewrite the volume.
READSCB
error reading storage control block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to read the storage control block from virtual block 1 of the storage bit map file, [000000]BITMAP.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system. However, if the error persists, copy the volume to fresh media or reconstruct the volume from backup media. If you specify the /REPAIR qualifier, the utility rewrites the specified virtual block. This action may clear the error. If the error cannot be cleared, rewrite the volume.
READYREAD
mount volume 'n' on 'device-name' for reading Facility: BACKUP, Backup Utility Explanation: The Backup Utility requires that the specified volume of an input save set be mounted on the specified device. User Action: Mount the volume. If the utility is executing as an interactive job, enter YES in response to the prompt on SYS$COMMAND. If the utility is executing as a batch job, use the DCL command REPLY to signal completion.
READYWRITE
mount volume 'n' on 'device-name' for writing Facility: BACKUP, Backup Utility Explanation: The Backup Utility requires that the specified volume of an output save set be mounted on the specified device. User Action: Note that the Backup Utility will write on the volume and mount a suitable volume. If the utility is executing as an interactive job, enter YES in response to the prompt on SYS$COMMAND. If the utility is executing as a batch job, use the DCL command REPLY to signal completion.
READZERO
read of record id 0, dscb: 'address' Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
REAJBCMBX
error reading job controller mailbox Facility: JBC, Job Controller Explanation: The job controller encountered an error reading its mailbox. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
REALLYQUIT
buffer modifications will not be saved, continue quitting (Y or N)? Facility: VAXTPU, VAX Text Processing Utility Explanation: This message prompts you for confirmation that you want to execute the built-in procedure QUIT rather than the built- in procedure EXIT. When you execute the QUIT procedure, your modifications to the buffer are not saved (written into an output file). In other words, your file remains as it is prior to the editing session. User Action: Respond with NO if you change your mind and wish to continue editing. Respond with YES if you want to complete the built-in procedure QUIT. You must respond with YES or NO.
REALLYRECOVER
continue recovery (Y or N) ? Facility: VAXTPU, VAX Text Processing Utility Explanation: A condition has been detected that might cause a journal file inconsistency if you continue. The condition is indicated by a warning message displayed prior to this prompt. User Action: Do not continue the recovery if your environment is different from that of the journaled environment.
REBLDREQ
rebuild not performed; some free spaces unavailable; disk quota usage stale Facility: MOUNT, Mount Utility Explanation: A volume has been improperly dismounted (such as during a system crash), and subsequently mounted with the /NOREBUILD qualifier of the MOUNT command. The error occurs because a volume that has been dismounted improperly must be rebuilt to recover any caching limits that were enabled on the volume when it is dismounted. The rebuild operation restores the volume's disk quota information and recovers any preallocated free space in the EXTENT cache and any file numbers in the FILE_ID cache. User Action: Rebuild the volume by entering the DCL command SET VOLUME/REBUILD.
REBLDWARN
insufficient number of bad sector files written to 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: When BAD attempted to rebuild the Manufacturer's Detected Bad Sector File (MDBSF) and the Software Detected Bad Sector File (SDBSF) on a last track device, it is only successful in writing to half of the last track or less. This implies that the medium may be unreliable. User Action: Service the medium (and or drive) to ascertain the reliability and data integrity.
REBOOT
this product requires that the system be rebooted. Facility: VMSINSTAL, Install Procedures Explanation: The product that is just installed requires the system to be rebooted to complete the installation. User Action: Reboot the system after it shuts down.
REBUILD
volume is improperly dismounted; rebuild in progress Facility: MOUNT, Mount Utility Explanation: A disk is improperly dismounted and information is lost. REBUILD will reconstruct the file structure on the volume. User Action: None.
RECGTRBL
record size is greater than block size Facility: MOUNT, Mount Utility Explanation: The record size specified is greater than the block size (specified or defaulted). User Action: Specify a smaller record size or a larger block size.
RECISDEL
deleting a record already marked as deleted Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal VAXTPU failure occurred. User Action: Submit a Software Performance Report (SPR).
RECLNG
file 'filename' has a record of illegal length ('decimal-number')
Facility: LINK, Linker Utility
Explanation: A record in a file is of illegal length.
User Action: Submit a Software Performance Report on the
appropriate language translator.
RECLNG
illegal record length Facility: LBR, Librarian Subroutine Package Explanation: The record length exceeds 512 bytes. User Action: Reformat the module.
RECLNG
illegal record length 'nnn' in module 'module-name' in 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: The specified module contains records that exceed the maximum record length of 2048 bytes. User Action: Correct the record length before inserting the module in the library. Record too big, truncated to 255 characters Facility: EDT, EDT Editor Explanation: The file you attempted to edit or to include has lines longer than 255 characters. EDT deleted all characters from position 256 on because EDT's line length is limited to 255 characters. User Action: None.
RECORDANS
auto-answer file will be recorded. Facility: VMSINSTAL, Install Procedures Explanation: You specified the auto-answer option when you started VMSINSTAL. An answer file will be recorded for the product about to be installed. User Action: Answer the prompts as usual.
RECORDSWL
'device-name' is write protected - backup date recording pass not executed Facility: BACKUP, Backup Utility Explanation: The input device is software write locked. The BACKUP Utility cannot perform the backup data recording pass. User Action: Dismount the input device, remount it as writable, and reenter the BACKUP command.
RECOVER
'product-name' is being installed when the system failed. Facility: VMSINSTAL, Install Procedures Explanation: The specified product is installed when the system failed because of a power failure or other problem. User Action: You will receive additional instructions.
RECOVERABORT
recovery aborted by journal file inconsistency. Journal file closed. Facility: VAXTPU, VAX Text Processing Utility Explanation: An inconsistency is found between what the journal file contained and what the executing procedure expected. The inconsistency is explained in the next message. The recovery has aborted, and the journal file has closed. User Action: VAXTPU has recovered as much as it can from your journal file. If the recovered information is sufficient, resume editing from this point. Otherwise, correct any inconsistencies between the initial terminal state and the terminal state when you recover your file with the journal file.
RECOVEREND
recovery complete Facility: VAXTPU, VAX Text Processing Utility Explanation: The recovery of a VAXTPU session from a journal file has completed successfully. User Action: Resume editing as before the interruption.
RECOVERFAIL
recovery terminated abnormally; journal file inconsistency Facility: VAXTPU, VAX Text Processing Utility Explanation: The recovery is probably not being performed on exactly the same text file as the original VAXTPU session, or the keys may have different definitions than those used in the original editing session. User Action: Try the recovery again on the same type of terminal, with the same terminal setup, using the original input file and command qualifiers. Enter the DCL command SHOW TERMINAL to determine your current terminal characteristics.
RECPRN
'filespec' contained 'nnn' records with invalid PRN fields ('mmm'
prefix 'ppp' postfix)
Facility: EXCHNET, EXCHANGE/NETWORK Command
Explanation: The specified file contained one or more records with
invalid printing control fields in the print file control area
(PRN). The first byte of the control area constitutes a prefix
area, while the second byte constitutes a postfix area. These
areas specify the carriage control to be performed before and
after printing, respectively. A carriage return and a line-feed
character were substituted for each invalid byte, and the file was
copied.
User Action: If the substitution is not acceptable, determine the
cause of the PRN field error, fix it, and reenter the command.
RECTOBIG
'record-size' byte record too large for MAIL buffer Facility: MAIL, Mail Utility Explanation: MAIL encountered an oversized record during a read operation. The record is in an illegal format. User Action: Delete the record.
RECTOOBIG
record too large in 'filename' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility discovered a record which is too large for EXCHANGE to handle. User Action: The file displayed with the message might be corrupted, or it might not be in the record format being used by EXCHANGE. Reenter the command using the correct /RECORD_FORMAT qualifier.
RECTOOSML
data overflows object record in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
RECTRUNC
record truncated Facility: LBR, Librarian Subroutine Package Explanation: The buffer supplied in the routine is too small for the record. User Action: Supply a sufficiently large buffer to contain the record.
RECTYP
file 'filename' has a record of illegal type ('decimal-number')
Facility: LINK, Linker Utility
Explanation: An illegal object record type is encountered.
User Action: Submit a Software Performance Report on the
appropriate language translator.
RECTYP
illegal record type 'type' in module 'module-name' in 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: The specified object module contains an illegal record type. User Action: Recompile the module and reenter the command string.
RECURLEARN
learn sequence reply halted due to recursion Facility: VAXTPU, VAX Text Processing Utility Explanation: The key learn sequence is bound within the learn sequence. This causes an infinite loop. User Action: Bind the learn sequence to a different key.
REDCACHE
volume mounted with reduced cache size Facility: MOUNT, Mount Utility Explanation: This informational message occurs when the /PROCESSOR=UNIQUE qualifier is used with the MOUNT command and insufficient paged pool is available to allocate a file system buffer cache using the sizes specified by the ACP_MAPCACHE, ACP_ DIRCACHE, ACP_HDRCACHE, and ACP_DINDXCACHE SYSGEN parameters. Instead, a unique cache with a minimal number of buffers is allocated. User Action: The usual reason to use the /PROCESSOR=UNIQUE qualifier before VMS Version 4.0 is to avoid the problem of file system activity on one volume degrading file system performance on other volumes. This degradation is caused by the single-threaded nature of the file system ACP. In VMS Version 4.0, the procedure- based file system XQP provides a higher level of concurrency than is previously possible even with multiple ACPs. The /PROCESSOR qualifier is retained to allow discrete I/O buffer caches to be associated with specific volumes, instead of all volumes sharing the same I/O buffer cache, which is the default behavior. Therefore, the recommended action is to remove the /PROCESSOR=UNIQUE qualifier. However, if you need discrete I/O buffer caches, increase the size of the SYSGEN parameter PAGEDYN to account for the number of I/O buffers required. Also, increase the value of the SYSGEN parameter SYSMWCNT, to avoid increased system paging.
REDEFSYM
redefining symbol 'symbol-name' from 'addr1' to 'addr2' Facility: PATCH, Patch Utility Explanation: A user-defined symbol is changed to a different value. This typically occurs when you enter the PATCH command DEFINE and specify a symbol currently used in the image file, or when PATCH moves a VAX MACRO instruction that contains a label to a patch area. User Action: None.
REDFLGERR
error reading UETP common event flag cluster Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
REENT
file could not be renamed and recovery failed; file has been lost Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $RENAME operation failed and the attempt to recover the file's directory entry also failed. The file has become a lost file. User Action: Either use the ANALYZE/DISK/REPAIR Utility to recover the lost file, or ask your system manager to recover the file.
REENTER
please reenter last line as it is ignored Facility: MAIL, Mail Utility Explanation: MAIL encountered an illegal escape sequence during a send operation. The line containing the illegal escape sequence is ignored. User Action: Reenter the line without illegal escape sequences.
REENTRANCY
reentrancy detected Facility: LIB, Library Facility Explanation: This message indicates reentrant invocation of a routine. User Action: Begin debugging procedures to verify and correct the problem. Whenever reentrancy is possible, such as at AST level, it is strongly recommended that users take appropriate action to ensure that their code executes properly in the event of reentrancy.
REF
invalid key-of-reference = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The key-of-reference number specified in a key definition XAB is either greater than 254 or not a defined key for the file. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
REFCNTNEG
PFN reference count is negative Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
REFERENCED
existing references prevent deletion Facility: JBC, Job Controller Explanation: Existing references to the specified form, characteristic, or queue by other queues or jobs prevent the specified item from being deleted. User Action: Use the SHOW QUEUE/FULL/ALL command to locate all such references. Remove the existing references and retry the delete operation.
REFRESH_NEEDED
screen refresh needed Facility: VAXTPU, VAX Text Processing Utility Explanation: This is an internal status message, which indicates that the screen needs to be refreshed. User Action: None.
REFUSED
you cannot attach to that process Facility: CLI, Command Language Interpreter (DCL) Explanation: Either you have attempted to attach to a process that is your own process or that is not part of your process tree. You cannot perform the attempted operation. User Action: None.
REGOPSYNX
register operand syntax error Facility: MACRO, VAX MACRO Assembler Explanation: The addressing mode syntax contained an error. User Action: Correct the addressing mode syntax.
REGWIDDUP
registration string already associated with a different widget Facility: VAXTPU, VAX Text Processing Utility Explanation: The registration string is already associated with a different widget. User Action: An application is attempting to register multiple widgets with the same name. Modify the application to use unique names for each registered widget.
REINITERR
error attempting reinitialization Facility: LAT, LAT Facility Explanation: LATCP cannot reinitialize in order to accept another command. An accompanying message explains why the program cannot reinitialize. User Action: Correct the situation based on the information in the accompanying message.
REJECT
connect to network object rejected Facility: SYSTEM, VMS System Services Explanation: A request to connect to an object at a remote node failed for one of the following reasons: o The object requested does not exist. o The access control information specified is invalid. o The partner NSP has no resources. o The partner task exited during the connect sequence. o The partner task rejected the connect. User Action: Determine which reason caused the failure and try to correct the condition.
RELCONCAT
relative file cannot be concatenated Facility: Shared by several facilities. Explanation: A relative file may not be concatenated with another file. User Action: Use a program to load the relative file.
RELINK
file 'filename' contains deferred relocation. Relink 'filename' and all images linked against it Facility: LINK, Linker Utility Explanation: The specified shareable image file is linked under the VMS Version 2.0 or Version 2.1 linker. User Action: Relink the specified shareable image.
RELMOVED
the product's release notes have been successfully moved to SYS$HELP. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL moved the product's release notes file to SYS$HELP. User Action: Contact the Digital Services Group.
REMABO
remote node not defined Facility: NCP, Network Control Program Explanation: The remote node specified in the NCP command COPY is not defined in the local node database. If the /WITH qualifier is included in the COPY command, the remote node is not placed in the local database. User Action: None is required; however, if you have sufficient privilege, you may want to add the remote node to the local node database.
REMARCEST
remote archive link established ('n' messages lost)
Facility: AUDSRV, Audit Server
Explanation: The audit server has established a new remote archive
file connection and enabled archiving to the remote archive file.
This informational message also displays the number of messages
lost while the remote node was unavailable.
User Action: None.
REMARCFAIL
remote archive link failure; archive messages will be lost (status: 'status') Facility: AUDSRV, Audit Server Explanation: The network link to a remote system audit archive file has failed. User Action: None. The audit server will reestablish a link to the remote node as soon as it becomes available.
REMARCNAVL
remote archive link not available; archive messages will be lost Facility: AUDSRV, Audit Server Explanation: The audit server could not establish a link to the node associated with the system audit archive file. This message may be accompanied by further information indicating the exact nature of the problem. If no further information is signaled, this indicates that the node is not available or not accepting remote connections. User Action: None. The audit server will establish a link to the remote node as soon as it becomes available.
REMARCSTS
remote archive link not available ('n' messages lost)
Facility: AUDSRV, Audit Server
Explanation: The audit server is unable to establish a link to
the node associated with the system audit archive file. This
message follows the REMARCNAVL or REMARCFAIL error message and
is broadcast each minute indicating the number of archive messages
being lost.
User Action: None. The audit server will establish a link to the
remote node as soon as it becomes available.
REMDEF
the DEFAULT record may not be removed Facility: AUTHORIZE, Authorize Utility Explanation: You attempted to remove the DEFAULT record. User Action: Do not attempt to remove the DEFAULT record.
REMDISABLED
resource monitoring disabled for journal 'name' Facility: AUDSRV, Audit Server Explanation: Resource monitoring has been disabled for the specified security audit journal file. User Action: None. This is an informational message.
REMENABLED
resource monitoring enabled for journal 'name' Facility: AUDSRV, Audit Server Explanation: Resource monitoring has been enabled for the disk volume associated with the specified security audit journal file. User Action: None. This is an informational message.
REMERR
error removing 'filename' Facility: SET, SET Facility Explanation: An error occurred while trying to remove the specified file. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
REMERR
unable to delete record Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
REMMSG
record removed from SYSUAF.DAT Facility: AUTHORIZE, Authorize Utility Explanation: This message is informational. User Action: None.
REMNOTENAB
resource monitoring not enabled for journal 'name' Facility: AUDSRV, Audit Server Explanation: The audit server could not perform the requested action because resource monitoring was not enabled for the specified audit journal. User Action: Enable resource monitoring for the specified journal, and try again.
REMOINSF
node name specification or /REMOTE missing from command line Facility: PRINT, PRINT Command and SUBMIT, SUBMIT Command Explanation: To print or submit a file residing on a remote node for processing on that node, the /REMOTE qualifier must be included in the PRINT or SUBMIT command and the file specification must contain the remote node name. Conversely, to print or submit a file without using the network, the /REMOTE qualifier cannot be used with the PRINT or SUBMIT command and the file specification cannot include a node name. User Action: Correct the error and reenter the command.
REMOTE
assignment completed on remote node Facility: SYSTEM, VMS System Services Explanation: An assignment for a transparent connect on a remote node completed successfully. User Action: None.
REMOTE
connection established to remote node 'node-name' Facility: REM, Set Host Facility Explanation: Connection to the remote system has been established. This is an informational message. User Action: None. Remote System Conflicts with Known System Facility: VAXport, VAXport Driver Explanation: The VAXport driver configuration poller discovered a remote system with SCSSYSTEMID or SCSNODE equal to that of another system to which a virtual circuit is already open. User Action: Shut the new system down as soon as possible. Reboot it with a unique SCSYSTEMID and SCSNODE. Do not leave the new system up any longer than necessary. If you are running a VAXcluster and two systems with conflicting identity are polling when any other virtual circuit failure takes place in the VAXcluster, then systems in the VAXcluster may crash with a CLUEXIT bugcheck.
REMOUVOL
REMOUNT relative volume nn (volume label) on 'device-name' Facility: MOUNT, Mount Utility Explanation: An error has occurred on a magnetic tape requiring operator intervention. User Action: Perform the required physical actions and use the DCL command REPLY to notify the ACO the volume is ready.
REMOVE
file ('file-id') error removing directory entry
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to remove
a directory entry referencing the specified file identification.
An accompanying message provides additional information.
User Action: Correct the condition that caused the error and
reenter the command.
REMOVED
'directory-name' removed Facility: SET, SET Facility Explanation: The requested directory is removed successfully. User Action: None.
REMOVED
entry for 'filespec' has been removed Facility: INSTALL, Install Utility Explanation: The Known File Entry is successfully removed. This is an informational message. User Action: None.
REMOVED
symbol 'symbol-name' removed from 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This success message is generated by the DCL command LIBRARY. User Action: None.
REMRSRC
insufficient system resources at remote node Facility: SYSTEM, VMS System Services Explanation: An attempt is made to initiate a DECnet-VAX logical link connection. The remote process encountered a resource allocation failure while trying to confirm the logical link. User Action: This condition is often temporary. If the condition persists after repeated retries, the remote process should be run under an account with higher quotas. Refer to the VMS Networking Manual for additional information.
REMSYS
the SYSTEM record may not be removed Facility: AUTHORIZE, Authorize Utility Explanation: You attempted to remove the SYSTEM record. User Action: Do not attempt to remove the SYSTEM record.
RENAMED
'filespec' renamed to 'filespec' Facility: Shared by several facilities Explanation: This message is associated with the execution of a DCL command RENAME. The name of the first file is changed to the name given in the second file specification. User Action: None.
RENDEF
the DEFAULT record may not be renamed Facility: AUTHORIZE, Authorize Utility Explanation: You attempted to rename the DEFAULT record. User Action: Do not attempt to rename the DEFAULT record.
RENMSG
user record renamed Facility: AUTHORIZE, Authorize Utility Explanation: This message is informational. User Action: None.
RENSYS
the SYSTEM record may not be renamed Facility: AUTHORIZE, Authorize Utility Explanation: You attempted to rename the SYSTEM record. User Action: Do not attempt to rename the SYSTEM record.
REPEAT
parameter repeated Facility: NCP, Network Control Program Explanation: A parameter is repeated in the command. A parameter may appear only once in a command. User Action: Reenter the command without repeating parameters.
REPLACED
'output-filespec' being replaced Facility: Shared by several facilities Explanation: An output file is replaced successfully by a new version. User Action: None.
REPLACED
module 'module-name' replaced in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This success message is generated by the DCL command LIBRARY. User Action: None.
REPLACEERR
replacement value too large for location Facility: PATCH, Patch Utility Explanation: When you replaced data with the PATCH utility command REPLACE, the new data contained more bytes than the old data. User Action: Correct and reenter the command.
REPLACERR
error replacing 'module-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: An error occurred during a module replacement operation. Either a VMS RMS error occurred or enough virtual memory is not available. User Action: Ensure that the new file in the replacement operation is not corrupt.
REPLAYFAIL
an inconsistency has been discovered, halting execution Facility: VAXTPU, VAX Text Processing Utility Explanation: A learn sequence stopped executing. The sequence of keystrokes that is saved is inconsistent with the current actions. This is probably because some keys have different definitions now than when the learn sequence is created. User Action: None is required. However, if you suspect that the replay of the learn sequence may have altered parts of your text incorrectly, check the text for changes.
REPLAYWARNING
an inconsistency has been discovered, continuing execution Facility: VAXTPU, VAX Text Processing Utility Explanation: During the execution of a learn sequence, an inconsistency is discovered between the original actions and the current ones. It is possible to continue execution, but the results may not be those expected. This is probably because some keys have different definitions now than when the learn sequence is created. User Action: None is required. However, if you suspect that the learn sequence did not complete correctly, check the text where the learn sequence is replayed.
REQARGSMISSING
one or more required arguments missing Facility: VAXTPU, VAX Text Processing Utility Explanation: You have not specified one or more required arguments for this DECwindows call. User Action: Specify all required arguments.
REQDITEMMISS
required item not in item list for call Facility: SMI, System Management Integrator/Server Explanation: This message indicates an internal error. An SMI call specifies an item list within which an item required for the given object and that function is not present. User Action: Submit a Software Performance Report showing the exact sequence of SYSMAN commands leading to the error.
REQFILMIS
requested file is missing from input file 'filename' Facility: MONITOR, Monitor Utility Explanation: The data describing the file requested with the /FILENAME qualifier did not exist in the input file. User Action: Correct the /FILENAME qualifier specification and reenter the MONITOR command.
REQKEY
at least one keyword must be specified for type 'type-name' Facility: CDU, Command Definition Utility Explanation: CDU encountered a type definition with no keywords. User Action: Edit the CLD file so that each DEFINE TYPE command includes at least one keyword.
REQPRMABS
required parameter is absent Facility: CLI, Command Language Interpreter (DCL) Explanation: You did not enter a required qualifier for a DCL command. User Action: Refer to the VMS DCL Dictionary for the command and reenter it using all the required qualifiers.
REQUEST
service required on queue 'name' for job 'number' user 'name' Facility: JBC, Job Controller Explanation: In response to the /OPERATOR qualifier of the PRINT command, this message is displayed at the operator's terminal. This message is followed by the text specified with the /OPERATOR qualifier. User Action: Take the reqested action and enter a START/QUEUE command to restart the queue. 'Character-name' required Facility: EDT, EDT Editor Explanation: The command requires the specified character. User Action: Reenter the command including the required character.
REQUIRESDECW
feature requires the VAXTPU DECwindows screen updater Facility: VAXTPU, VAX Text Processing Utility Explanation: The requested operator or feature is available only using the VAXTPU DECwindows screen updater. User Action: Do not use the feature.
REQUIRESTERM
feature requires a terminal Facility: VAXTPU, VAX Text Processing Utility Explanation: The requested feature is only available when there is a terminal. User Action: Do not use the feature or specify /DISPLAY qualifier.
RER
file read error Facility: RMS, VMS Record Management Services Explanation: Either VMS RMS could not read an input file, or a terminal read error occurred. User Action: If VMS RMS could not read the input file, the status value (STV) field of the RAB contains a system status code that provides more information about the condition. Take corrective action based on this status code. If a terminal read error occurred, reenter the input line.
RESCRASH
resources exhausted; server restarting Facility: AUDSRV, Audit Server Explanation: The process virtual memory allocated to the audit server (used to buffer incoming security alarms) has been exhausted. This message indicates that the audit server final action mode was set to RESTART and that the audit server process is restarting. Buffered security alarms received prior to the resource exhaustion condition will be stored in the process dump file SYS$SYSROOT:[SYSEXE]AUDIT_SERVER.DMP. User Action: None.
RESCRITICAL
security auditing resources exhausted on journal 'name' Facility: AUDSRV, Audit Server Explanation: The free disk space on the disk volume associated with the specified audit journal has fallen below the resource action threshold. An accompanying RESINFO message will indicate the number of free disk blocks and the number of disk blocks needed to dismiss the resource warning condition. Because of this condition, the audit server will suspend non-critical system processes in an attempt to prevent complete exhaustion of the associated volume. User Action: Log into a privileged account and free up disk space on the disk volume associated with the specified audit journal file.
RESDISMISS
resource exhaustion condition dismissed on journal 'name' Facility: AUDSRV, Audit Server Explanation: The free disk space on the disk volume associated with the specified audit journal has risen above the resource warning threshold. User Action: None.
RESERR
resource error Facility: NCP, Network Control Program Explanation: A resource necessary to complete the command, for example, the system resource nonpaged pool, is not available. User Action: Determine why the resource is not available.
RESET
circuit is reset Facility: SYSTEM, VMS System Services Explanation: The virtual circuit is reset while this request is being processed, or the circuit is in the process of being reset when you issued the request. User Action: Initialize the circuit and retry the call.
RESETQUE
error resetting queue 'queue-name' Facility: JBCUPGRAD, Queue Upgrade Utility Explanation: An error occurred during a $SNDJBC system service call attempting to reset the queue. User Action: The accompanying message gives information about why the operation failed. Correct the problem and retry the upgrade.
RESIGNAL
resignal condition to next handler Facility: SYSTEM, VMS System Services Explanation: A condition handler completed without terminating or continuing the image. This message is associated with an exit status code used by condition handling routines to indicate that the exception dispatcher continued its search for handlers. User Action: None, this message is not normally displayed.
RESINFO
resource information: 'n' blocks needed, 'n' blocks available Facility: AUDSRV, Audit Server Explanation: This informational message indicates the number of disk blocks needed to remove the preceding resource exhaustion condition on the volume associated with the specified security audit journal file. The number of disk blocks currently available is also given. User Action: None.
RESNOTDISK
resource monitoring ignored for journal 'name'; journal is directed to an invalid device type Facility: AUDSRV, Audit Server Explanation: Resource monitoring could not be enabled for the specified audit journal because the audit journal is not directed to a file-structured disk device. User Action: Redirect the audit journal to a file-structured disk device.
RESOKAY
free resources available on journal 'name' Facility: AUDSRV, Audit Server Explanation: The free disk space on the disk volume associated with the specified audit journal is above all thresholds. An accompanying RESINFO message will indicate the number of disk blocks free. User Action: None.
RESOPCODE
opcode 'xx' is reserved Facility: PATCH, Patch Utility Explanation: You specified an opcode that is reserved for Digital use only. User Action: None. Response Queue Remove Failure Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. This error is caused by a failure to obtain access to an interlocked queue. Possible sources of the problem are CI hardware failures or memory, SBI (11/780), CMI (11/750), or BI (8200, 8300, and 8800) contention. User Action: Call the Digital Services Group.
RESTART
audit server restart requested Facility: AUDSRV, Audit Server Explanation: A forced audit server restart was received by the audit server process. The audit server process will restart. Buffered security alarms received prior to the restart will be stored in the process dump file SYS$SYSROOT:[SYSEXE]AUDIT_ SERVER.DMP. User Action: None. This event results from the server FINAL_ACTION setting of RESTART.
RESTARTCOM
job Controller abort/restart action complete, queue manager restarted Facility: JBC, Job Controller Explanation: This message is signaled to the console terminal to inform the system manager that the job controller has recovered from a fatal error condition and has restored the batch/print queue environment. Recovery entails having the job controller respond to a fatal error by aborting itself, restarting itself in the context of a new process, and reopening the system queue file (if the /RESTART qualifier was used initially with the START/QUEUE /MANAGER command). Look for a "JBC-F-" message preceding this message on the console or an operator's terminal to find out what error condition caused the job controller to voluntarily abort and restart itself. User Action: None.
RESTORE
restoring product save set 'letter' . . . Facility: VMSINSTAL, Install Procedures Explanation: The Backup Utility is restoring the product save set that you specified from the distribution media. User Action: None.
RESTOREFAIL
error during RESTORE operation Facility: VAXTPU, VAX Text Processing Utility Explanation: An error occurred while VAXTPU is restoring a section file. This message should be accompanied by a VMS RMS message identifying the reason for the error. User Action: Check the directory specification, the file protection, or any other item specified in the accompanying VMS RMS message to make sure that you are trying to restore a valid section file.
RESTRICT
UAF restricts access at this time, please log out immediately Facility: JBC, Job Controller Explanation: The User Authorization File record for the owner of the interactive or batch process does not allow access to the system at the current time. A short time after this warning is issued, the job controller will delete the process. User Action: Close your files and logout immediately.
RESULTOVF
resultant string overflow Facility: SYSTEM, VMS System Services Explanation: A user buffer specified to receive data from the system is not long enough. The system does not truncate the data because the loss of data will damage its integrity. User Action: Check for a programming error. Verify that character string descriptors for output data buffers reflect the correct lengths.
RESUME
resuming operation on volume 'n' Facility: BACKUP, Backup Utility Explanation: The Backup Utility is continuing an operation on the specified volume of a save set. User Action: None.
RESUME
system operation resumed; security auditing resources available Facility: AUDSRV, Audit Server Explanation: Normal system operation has been resumed by the audit server process following a resource exhaustion condition. User Action: None.
RESUMED
connection resumed. Press Ctrl/'escape character' to quit, Facility: REM, Set Host Facility Explanation: Connection to the remote system has been resumed. This is an informational message. User Action: None required. If you wish to quit the session, type Ctrl/'escape character'. To access DTE command mode, type Ctrl /'command character'.
RESUMEFAIL
system operation not resumed; resource condition still exists on journal 'name' Facility: AUDSRV, Audit Server Explanation: The audit server was unable to resume normal system activity because the free disk space associated with the specified audit journal file is still less than the action threshold. User Action: Log into a privileged account and free up disk space on the disk volume associated with the specified audit journal.
RESUMEWARN
resource exhaustion condition dismissed (with resources still low) on journal 'name' Facility: AUDSRV, Audit Server Explanation: The audit server has resumed system activity following a resource exhaustion condition, however the free disk space associated with the specified audit journal file is still less than the warning threshold. User Action: Log into a privileged account and free up disk space on the disk volume associated with the specified audit journal.
RESWARNING
resource warning condition exists on journal 'name' Facility: AUDSRV, Audit Server Explanation: The free disk space on the disk volume associated with the specified audit journal has fallen below the resource warning threshold. An accompanying RESINFO message will indicate the number of disk blocks free and the number of disk blocks needed to dismiss the resource warning condition. User Action: Log into a privileged account and free up disk space on the disk volume associated with the specified audit journal file.
RETURNED
control returned to process 'process-name' Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is output by DCL when you log out of a spawned process. User Action: None.
REVERSECASE
CASE limits were reversed Facility: VAXTPU, VAX Text Processing Utility Explanation: A CASE statement is found with the upper and lower label value reversed. A CASE statement must specify the lower value first. User Action: Reverse the CASE values and recompile your program.
REVOKEERR
unable to revoke identifier 'id-name' from 'user ID ' Facility: AUTHORIZE, Authorize Utility Explanation: The specified identifier could not be revoked from the specified user. User Action: Make sure that the user has been granted the identifier you are trying to revoke. Use the AUTHORIZE commands SHOW/IDENTIFIER/FULL or LIST/IDENTIFIER/FULL to display an identifier and the users who hold it.
REVOKEMSG
identifier 'id-name' revoked from 'user-name' Facility: AUTHORIZE, Authorize Utility Explanation: The specified identifier has been revoked from the specified user. The user no longer has the rights associated with the identifier. User Action: None.
REWIND
the tape will be rewound to try again. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL is attempting to restore a product save set with the Backup Utility. It could not find the required save set on the distribution tape that is mounted. VMSINSTAL will rewind the tape in case the save sets were not recorded in order. User Action: None. Ignore any accompanying BACKUP messages.
REX
record already exists Facility: CONVERT, Convert Utility Explanation: You have tried to write a record into a relative file cell that already contains a record. User Action: Delete the record and try again.
REX
record already exists Facility: RMS, VMS Record Management Services Explanation: A $PUT operation using random record access mode to a relative file specified an existing record in the target record cell. The new record is not written. User Action: Modify the program, if necessary, to detect and respond to the condition. You may want to include the UIF option in the ROP parameter for the file.
RFA
invalid record file address (RFA) Facility: RMS, VMS Record Management Services Explanation: The record file address field of the RAB contains a zero value for RFA access in a $GET or $FIND operation. User Action: Verify that the call to the VMS RMS service is coded correctly.
RFAERR
RMS error using RFA access: RFA = xxxxxx, xxx Facility: SEARCH, SEARCH Command Explanation: SEARCH received an error from VMS RMS when trying to position to the start of a window. This message is accompanied by other messages. User Action: If the file being searched is on another network node, and one of the additional messages is "network operation not supported", then retry the command without the /WINDOW qualifier. Otherwise, if the error is reproducible, notify your system manager to submit a Software Performance Report (SPR). The numbers displayed with the error message and the file being searched should be included with the Software Performance Report (SPR).
RFAPASTEOF
VBN in map block request past EOF Facility: LBR, Librarian Subroutine Package Explanation: An unexpected internal consistency check occurred. One cause of this problem is insufficient virtual memory when creating or compressing a large library. Another cause is a corrupt library file. User Action: Inform your system manager and submit a Software Performance Report (SPR). If you are inserting or replacing a large number of modules, you may be successful by performing the operation in several pieces. If you are compressing a large library, your System Manager may have to increase your PGFLQUO and/or increase the SYSGEN parameter VIRTUALPAGECNT.
RFLOC
unable to locate related file Facility: FDL, Create/FDL Utility Explanation: The file that you specified with the AREA POSITION FILE_NAME or FILE_ID attribute cannot be found. User Action: Check on the location of the desired file, or else specify a different FILE_NAME or FILE_ID.
RFM
invalid record format Facility: RMS, VMS Record Management Services Explanation: The record format field of the FAB does not contain a valid value. The valid values for this field are FIX, STM, STMCR, STMLF, VAR, VFC, and UDF. User Action: Verify that the call to the VMS RMS service is coded correctly.
RHB
invalid record header buffer Facility: RMS, VMS Record Management Services Explanation: The record header buffer address of the RAB specifies an area of memory that cannot be accessed correctly by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly.
RLF
invalid related NAM block Facility: RMS, VMS Record Management Services Explanation: The address of the NAM block for a related file is nonzero but it does not point to a valid related file NAM block with a valid resultant name string. Or, too many related blocks have been chained together or the related NAM blocks have been chained together. User Action: Verify that the call to the VMS RMS service is coded correctly.
RLK
target record currently locked by another stream Facility: RMS, VMS Record Management Services Explanation: The target record is locked by another stream. User Action: Modify the program, if necessary, to detect and respond to the condition.
RLSSRVERR
error encountered while testing $RELEASE_VP system service Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error testing VMS system services. This error is received in relation to a previously displayed error condition or could be the result of a more serious VMS problem. User Action: Identify the condition causing the problem, correct it, and rerun the test. If the error persists, submit a Software Performance Report. If no condition can be identified, run diagnostics for VAX Vectors or contact the Digital Services Group.
RLSTMSG
listing file RIGHTSLIST.LIS complete Facility: AUTHORIZE, Authorize Utility Explanation: The contents of the rights database file (RIGHTSLIST.DAT) have been written to the listing file named RIGHTLIST.LIS. User Action: None.
RMALRDCL
resource manager name has already been declared Facility: SYSTEM, VMS System Services Explanation: This message indicates an error in the resource manager. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the output for both the LMCP DUMP command and the DCL DUMP command for the log file.
RMS
record caused RMS severe error Facility: CONVERT, Convert Utility Explanation: This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error specified by the RMS error message and try again.
RMSBUG
RMS has detected an invalid condition Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
RMSERROR
RMS service error Facility: Shared by several facilities Explanation: An error is encountered during a VMS RMS operation. A subsequent message explains the reason for the error. User Action: Retry the operation; refer to the VMS Record Management Services Manual for more information.
RMSFILINI
error occurred during RMS file initialization 'filename' on node 'nodename' Facility: MONITOR, Monitor Utility Explanation: An error occurred while the Monitor Utility tried to set up the specified file for statistics monitoring. Check the accompanying messages for more details. User Action: Correct the problem specified with the accompanying messages and reenter the MONITOR command.
RMSFILMIS
one or more requested RMS files are missing from input file Facility: MONITOR, Monitor Utility Explanation: The data describing one or more files requested with the /FILENAME qualifier did not exist in the input file. User Action: Correct the /FILENAME qualifier specification and reenter the MONITOR command.
RMTPATH
description of path between two remote nodes Facility: SYSTEM, VMS System Services Explanation: The described network path represents a network path between two remote nodes instead of a path used by the local node. This network path is not necessary for the local area VAXcluster network failure analysis performed by the local node. User Action: Removing this network path definition will prevent this informational message from occurring. However, this action is optional.
RMV
ACP remove function failed Facility: RMS, VMS Record Management Services Explanation: A file could not be removed or renamed correctly. This message is associated with a system status code returned from a file system ACP QIO request made by RMS. User Action: The status value (STV) field of the FAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
RNAME_ABSENT
Resource Manager name absent from this record Facility: LMCP, Log Manager Control Program Explanation: The resource manager selected for removal is not in the currently displayed record. User Action: None.
RNAME_INV
hex Resource Manager name contains non-hex characters Facility: LMCP, Log Manager Control Program Explanation: The hexadecimal resource manager name contains invalid characters or was not preceded by %X. User Action: Enter the resource manager name using hexadecimal characters.
RNAME_LONG
Resource Manager name too long Facility: LMCP, Log Manager Control Program Explanation: The name of the resource manager entered exceeds 32 ASCII or 64 hexadecimal characters. User Action: Enter the correct number of characters, up to 32 ASCII and 64 hexadecimal.
RNAME_ODD
hex Resource Manager name is an odd length Facility: LMCP, Log Manager Control Program Explanation: The hexadecimal resource manager name entered contains an odd number of characters which prevents translation. User Action: Enter the correct number of characters, up to 32 ASCII and 64 hexadecimal.
RNF
record not found Facility: RMS, VMS Record Management Services Explanation: A requested record could not be located in a $FIND or $GET operation on a relative or indexed file. Either the record is never written or it has been deleted. User Action: Modify the program, if necessary, to detect and respond to the condition.
RNL
record not locked Facility: RMS, VMS Record Management Services Explanation: The record specified for a VMS RMS $FREE or $RELEASE operation is not locked. User Action: Modify the program, if necessary, to detect and respond to the condition.
ROP
invalid record options Facility: RMS, VMS Record Management Services Explanation: An incorrect record option (ROP) is specified. User Action: Verify that the call to the VMS RMS service is coded correctly.
ROPRAND
reserved operand fault at PC 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: An instruction contains an operand in a format that is not acceptable. This message indicates an exception condition and is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Check for a programming error. Examine the PC and virtual address displayed in the message to determine the instruction that caused the error.
ROPRAND
utility converted a reserved operand to a valid value Facility: SORT, Sort/Merge Utility Explanation: SORT/MERGE has detected decimal data that contains an invalid sign or digit, or data that contains a floating reserved operand. The error is corrected, and processing continues. User Action: None.
ROUTREQ
line 'line-number': A ROUTINE clause is only valid when generating an object file Facility: CDU, Command Definition Utility Explanation: CDU did not encounter a ROUTINE clause while attempting to generate an object file. A ROUTINE clause is required for object file generation. User Action: Edit the CLD file so that a ROUTINE clause is present if object file generation is desired.
RPL
error detected while reading prolog Facility: RMS, VMS Record Management Services Explanation: An I/O error occurred during an attempt to read the file's prolog. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a system status code that provides additional information about the condition. Take corrective action based on this status code.
RPTCNTNABS
repeat count not absolute Facility: MACRO, VAX MACRO Assembler Explanation: The repeat count in a .REPEAT, .SIGNED_BYTE, or .SIGNED_WORD directive contained an undefined symbol or is a relative expression. User Action: Replace the expression with an absolute expression that does not contain any undefined symbols.
RQSTABORT
'request', 'time', request 'number' aborted by operator 'operator- name' Facility: OPCOM, Operator Communication Process Explanation: A request to an operator is denied by the DCL command REPLY/ABORT. User Action: None.
RQSTCAN
request 'nnn' is canceled Facility: OPCOM, Operator Communication Process Explanation: A request to an operator is successfully canceled. User Action: None.
RQSTCMPLTE
request 'nnn' complete by operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: An operator has completed a user's request successfully; the dialog between the user and the operator is complete. This message indicates success. User Action: None.
RQSTDONE
request 'number' is satisfied Facility: OPCOM, Operator Communication Process, MOUNT, Mount Utility Explanation: The request completed successfully and is canceled by the requestor. User Action: None.
RQSTPEND
request 'nnn' pending by operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: The named operator responded to the user's request with the DCL command REPLY/PENDING. The operator will respond to the request when able to do so. This message is informational. User Action: No action is required. If the request must be satisfied immediately, use Ctrl/C to interrupt the request and send another message.
RQSTSTST
request status for request 'number' Facility: OPCOM, Operator Communication Process Explanation: This message provides the operator with additional, detailed information about the request. User Action: None.
RRV
invalid RRV record encountered Facility: RMS, VMS Record Management Services Explanation: An invalid record reference vector (RRV) record is detected. This indicates either a previous failure to update RRV records (see RVU error message) or a VMS RMS or system software error. User Action: Reorganize the file using the CONVERT command. If a software error is suspected, collect as much information as possible and submit a Software Performance Report (SPR).
RSA
record stream currently active Facility: RMS, VMS Record Management Services Explanation: An attempt is made to issue a VMS RMS record operation to a record stream that has an outstanding request. The outstanding operation may be asynchronous; or the failed operation was attempted at an AST level, or in an inner access mode. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition. Enter a $WAIT request before entering any additional requests.
RSBREFNEG
RSB reference count negative Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
RSBREFNZRO
tried to deallocate RSB with non-zero ref. count Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
RSK
record shorter than primary key Facility: CONVERT, Convert Utility Explanation: The record does not contain enough data to fill the primary key field in the indexed output file. User Action: Compare the layout of the input and output records, and change one or the other to completely fill the primary key field of the output records with data.
RSL
invalid resultant string length Facility: RMS, VMS Record Management Services Explanation: The VMS RMS NAM block contains an invalid value in the resultant string length field for an operation (for example, $ENTER, $REMOVE, or $SEARCH) in which this field is a required input. This field is generally filled in by a previous $CREATE, $OPEN, or $SEARCH operation. User Action: Verify that the call to the VMS RMS service is coded correctly.
RSLOVF
buffer overflow - specify fewer command elements Facility: CLI, Command Language Interpreter (DCL) Explanation: The buffer used by the command interpreter to store a command string during parsing has overflowed. User Action: Simplify the command.
RS_LSS_AC
RSOFFSET field less than ACOFFSET Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: This message, issued along with the BADHEADER message, explains why the specified file header is corrupt. In this case, the Reserved Area Offset field of an ODS-2 header (FH2$B_RSOFFSET) contains a value less than the Access Control List Offset field (FH2$B_ACOFFSET), implying that the Reserved Area precedes the Access Control List in the header, which is invalid. User Action: None. See the BADHEADER message.
RSS
invalid resultant string size Facility: RMS, VMS Record Management Services Explanation: The resultant string area size does not define a buffer large enough to receive the resultant file specification string being returned from a VMS RMS operation. User Action: Verify that the call to the VMS RMS service is coded correctly.
RST
invalid resultant string address Facility: RMS, VMS Record Management Services Explanation: The resultant string area address in the NAM block specifies an address that is in an area of memory that cannot be written by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly.
RSV_ERR
cannot have RSV device - set to zero Facility: SYSGEN, System Generation Utility Explanation: RSV is a reserved device name and cannot be specified to SYSGEN CONFIGURE. User Action: Do not specify RSV as a device name.
RSZ
invalid record size
Facility: RMS, VMS Record Management Services
Explanation: The record size (RSZ) field of the RAB contains an
invalid value for one of the following reasons:
o The record size value is greater than the maximum record size
specified for the file.
o The record size value is not the correct size for fixed length
records.
o The record size value is not large enough to contain the
primary key for an indexed file.
o The record size value is different than the original record
size of a $UPDATE operation on a sequential file.
The maximum record size value must be in the range of 1 through
32,767 for the $PUT and $UPDATE services, and in the range of 1
through 65,535 for the $WRITE service.
User Action: Verify that the call to the VMS RMS service is coded
correctly.
RSZ
invalid record size Facility: CONVERT, Convert Utility Explanation: The record is either too long to fit in the specified bucket size (relative and indexed files), or it is longer than 512 bytes and block spanning is not allowed. User Action: Make the bucket size larger or specify block spanning.
RT11_BADDIRECT
volume 'volume-name' has invalid RT-11 directory Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has discovered an error in the directory structure on the specified volume. User Action: The volume is either not an RT-11 volume, or it is seriously corrupted.
RT11_BADFILE
bad block file created to cover bad block 'block' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has created a file named FILE.BAD to cover the listed bad block. User Action: The user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent.
RT11_BIGBADFILE
directory segment full, file has some good blocks Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility created a larger than necessary bad block file because the volume directory is full. User Action: The user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent. Look at the error message for RT11_OVERFLOW for tips on making space available.
RT11_DIRSIZE
volume 'volume-name' has directory showing 'number' blocks on a 'numeric-string' block device Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility discovered a mismatch between the size of directory and the size of the device. User Action: The volume has an error in structure. EXCHANGE will not write to the volume, but it will read the volume. If another computer system consistently produces volumes which give this error, it should be possible to initialize a volume with EXCHANGE and take the EXCHANGE-initialized volume to the other system. With the EXCHANGE-initialized volume, you will be able to transfer files between the two systems in both directions.
RT11_ERRLOCK
volume will be write-locked to prevent corruption Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has write-locked a volume because of a structure error. User Action: EXCHANGE has discovered a structure error, and is refusing to write to the volume so that the error will not be made worse. It should be possible to read some or all of the files on the disk. The Exchange Utility can be used to save all of the files on the volume, and then recreate the volume without any errors. Look at the command file SYS$UPDATE:CONSCOPY.COM to see how VMS uses EXCHANGE to make copies of the console device for some VAX processors.
RT11_EXTRA
extra words set to maximum of 119 Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility reduced the value on a /EXTRA_ WORDS qualifier to the maximum allowed. User Action: In the future, use a smaller value for extra words.
RT11_NOEND
segment end marker is missing from RT-11 directory Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility discovered that an RT-11 directory segment did not have a proper entry marking the end of the segment. User Action: EXCHANGE will assume that the last valid entry in the directory is the end, and will allow you to read the volume.
RT11_OVERFLOW
directory is full, unable to add file Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility is unable to add a file to an RT-11 directory because there is no space. User Action: Directory space can be made available by deleting files from the volume. It might also be possible to use the EXCHANGE INITIALIZE command and the /SEGMENTS qualifier to recreate the volume with more directory segments. See the command file SYS$UPDATE:CONSCOPY.COM for an example of how to save a volume as a virtual device, reinitialize the volume, and copy all the files back to the original volume.
RT11_STBLOCK
file start block - segment header inconsistent Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility discovered a mismatch between a stored block number and the value EXCHANGE computed. User Action: EXCHANGE will use the stored value as the correct value. Note that it is possible that there may be missing space or overlapping files on the volume.
RT11_TOOMANYBLK
too many blocks, using maximum allocation of 'xx' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility has reduced the /ALLOCATION value to the value shown. User Action: /ALLOCATION values cannot be larger than the device or 65,535, whichever is smaller.
RT11_TOOMANYSEG
too many segments, reducing to 'xx' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility reduced the value on a /SEGMENTS qualifier to the maximum allowed. User Action: In the future, use a smaller value for /SEGMENTS.
RT11_UNKENT
entry with unknown format in directory Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility found a directory entry which had an unexpected format. User Action: EXCHANGE will refuse to write to the volume, but will attempt to read the volume and make what sense of the volume that it can. See the explanation for the RT11_ERRLOCK for information on how to restore the volume.
RTB
'nnn' byte record too large for user's buffer Facility: RMS, VMS Record Management Services Explanation: A record returned from a $GET operation is too large for the user buffer provided. The status value (STV) field of the RAB contains the size of the record that is too large; the returned record is truncated to the size of the user buffer. User Action: Correct the program by providing a larger buffer.
RTL
input record too long: truncated 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: Too many characters were entered on a single input line; the excess has been discarded. User Action: Divide the record into several smaller ones.
RTL
record longer than Maximum Record Length Facility: CONVERT, Convert Utility Explanation: The record from the input file is longer than the maximum record length specified in the output file. This is an exception condition; the record will not be written to the output file. If the /EXIT qualifier is specified, processing will stop. User Action: Specify the /TRUNCATE qualifier.
RTNERROR
unexpected error status from user-written routine Facility: SORT, Sort/Merge Utility Explanation: A user-written comparison or equal-key routine returned an unexpected error status. User Action: Correct your comparison or equal-key routine.
RTOUTEOF
end-of-file on output 'filespec', insufficient space on volume Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ran out of space while copying an RT-11 file. User Action: RT-11 only supports contiguous files, therefore there must be a free space on the volume as large as the file you are trying to copy. Use the DIRECTORY/ALL command to see where the "unused" areas on the volume are. By deleting unneeded files that are adjacent to unused areas, it might be possible to create a large enough space. Also, if you use the COPY command to copy a file to the same volume, you can move files around and make larger free areas.
RTPROTECT
file is protected against modification Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility rejected a command to modify a protected file. User Action: If the file should be modified, use the EXCHANGE RENAME /NOPROTECT command to remove the protection from the file. Then reenter the command.
RTS
record too short for fixed record format file Facility: CONVERT, Convert Utility Explanation: The record in the input file is shorter than the fixed-length specified in the output file. This is an exception condition; the record will not be written. If the /EXIT qualifier is specified, then processing will stop. User Action: Specify one of the /PAD qualifier options.
RUCONFLICT
another facility has active recovery units on file Facility: SYSTEM, VMS System Services Explanation: The file cannot be accessed because another facility (such as RMS) has been updating the file using recovery units, and the file is potentially in an inconsistent state. User Action: If the file must be accessed (such as for BACKUP), either the file must be made consistent or, in an emergency, the recovery units must be turned off. If the file is still accessed by another facility, stopping the applications using the facility should return the file to a consistent state. For RMS files, closing the file or running down the process restores the file to a consistent state and turns off recovery units. If the file is not accessed by another facility, the recovery procedure for the facility that has recovery units on the file should be invoked to restore the file to a consistent state. For RMS files, typing the file or opening the file with RMS recovers the file automatically. If the file cannot be restored to a consistent state, or if you want to access the file without regard to consistency, use the SET FILE command with the /RU_FACILITY and /RU_ACTIVE qualifiers to turn off recovery units. For example, if RMS has active recovery units on the file EXAMPLE.DAT, and you wish to turn off recovery units, enter the following command: $ SET FILE EXAMPLE.DAT/RU_FACILITY=RMS/NORU_ACTIVE
RUF
fatal error detected by Recovery Unit Facility Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
RVN1NOTMT
root volume is not mounted Facility: MOUNT, Mount Utility Explanation: The root volume for the volume set specified in the DCL command MOUNT/BIND is not mounted. The root volume must be mounted when you add a new volume to an existing volume set. User Action: Verify that the root volume is mounted and online; if not, mount it and reenter the command. Verify the device names and volume labels specified in the command and retry the operation.
RVU
error updating RRV's, some paths to data may be lost Facility: RMS, VMS Record Management Services Explanation: VMS RMS failed to update all record reference vectors (RRVs) when a $PUT or $UPDATE service caused a bucket split. This error is usually caused by a hardware or system software error during VMS RMS RRV updating. All records are accessible by primary key only. RRV errors may subsequently occur. User Action: Reorganize the file with the CONVERT command.
SAMEDEVICE
repeated reference to device 'device' Facility: BACKUP, Backup Utility Explanation: The specified device appeared more than once in the BACKUP command. A device may not appear more than once in either a list of input devices or a list of output devices. Also, a device may not appear as both an input device and an output device. This occurs only in physical or image BACKUP operations when the output is not a saveset. The main purpose is to prevent the accidental initialization of the input disk to be saved. This situation will arise if the output specifier of the BACKUP command did not provide a device specification (or the device specification is syntactically incorrect) and the input device is the user's default device. In this case, the output device would default to the current default device (the input device). User Action: Check the command line to ensure that the device specifications are syntatically correct and that no device appears (explicitly or implicitly) more than once. Reenter the BACKUP command.
SAMEFILE
files are identical Facility: DIFF, DIFFERENCES Command Explanation: This success message is returned by the DIFF facility if the two files being compared are identical. User Action: None.
SAVEAMBIGSYM
saving ambiguous symbol 'symbol-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The named symbol could be either an undefined procedure or a variable; its correct usage has not yet been determined. User Action: Define the named symbol as either a PROCEDURE or a VARIABLE and save the section file again.
SAVEERROR
error during SAVE operation Facility: VAXTPU, VAX Text Processing Utility Explanation: An error occurred while VAXTPU is saving a section file. This message should be accompanied by a VMS RMS message identifying the reason for the error. User Action: Check the directory specification, the file protection, or any other item specified in the accompanying VMS RMS message to make sure that you are trying to save a valid section file.
SAVEUNDEFPROC
saving undefined procedure 'procedure-name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The named procedure is not defined, but it is saved in the section file as an undefined procedure. User Action: Define the named procedure and save the section file again.
SAVSETCLU
save set disk cluster factor must be 1 Facility: BACKUP, Backup Utility Explanation: The specified volume had a volume cluster factor larger than 1. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
SAVSETNAM
save set name must be in first list element Facility: BACKUP, Backup Utility Explanation: In a save set specifier, the first or only element of a list must contain a file name. The following list elements, if any, must contain only a device name. User Action: Enter the command again, with the save set name in the first element of the list.
SBIAERROR
fatal SBIA error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SCANADVANCE
scanner advanced to 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The scanner advanced so that the compiler could continue compiling after the error occurred. User Action: None.
SCANDEADPT
scan dead page table error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SCBRDERR
SCB physical read error halt Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SCHDWK
failed to schedule wakeup request for process 'process-id' Facility: RUN, Run Detached Utility Explanation: The $SCHDWK system service could not schedule a wakeup call to the created process. User Action: Determine error returned by the $SCHDWK system service, and act accordingly. Note that the created process will not be awakened, so it must be deleted and re-created.
SCRATCH_HEADER
scratch header used by XQP Movefile operation Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The Analyze/Disk_Structure Utility found a scratch file header (a temporary file header used by Movefile). This condition can be reported while an ANALYZE/DISK_STRUCTURE operation is being performed. During a Movefile operation, blocks can be temporarily allocated to more than one file header. In such cases, this message can be accompanied by one or more MULTALLOC messages. These messages cease when the scratch header is released. User Action: If the message occurs while you are performing an ANALYZE/DISK_STRUCTURE/NOREPAIR operation on a disk that is in use, no action is required. If the message occurs while you are analyzing a disk after a system crash, release any scratch file headers on the disk by performing an ANALYZE/DISK_STRUCTURE/REPAIR or SET VOLUME/REBUILD operation on the disk.
SCRBUFOVF
screen buffer overflow Facility: LIB, Library Facility Explanation: While buffering is in effect, a call to one of the terminal-independent screen procedures created more data than would fit in an entire buffer. User Action: Increase the size of the buffer specified in a call to LIB$PUT_BUFFER. SCSSYSTEMID has NOT been set to a nonzero value Facility: VAXport, VAXport Driver Explanation: The port driver will not attempt to start the port. User Action: Modify the SCSSYSTEMID SYSGEN parameter and reboot the system. See the appropriate VMS installation guide.
SDBSFFULL
software detected bad sector file is full on 'device-name' Facility: BAD, Bad Block Locator Utility Explanation: The Bad Block Locator Utility located the SDBSF; however, it is already full. User Action: Reinvoke the Bad Block Locator Utility without specifying any execution context that would cause the utility to attempt to keep the SDBSF. For example, the user should specify the /EXERCISE=NOKEEP qualifier.
SDBSFRFAIL
failed to read the software detected bad sector file on 'device- name' Facility: BAD, Bad Block Locator Utility Explanation: The Bad Block Locator Utility could not locate a valid SDBSF. User Action: Avoid using any execution context that attempts to obtain or preserve the SDBSF. The following qualifiers would cause the Bad Block Locator Utility to try to preserve the SDBSF: /BAD_ BLOCKS, /EXERCISE=KEEP, /OUTPUT/SHOW=BEFORE. Use an execution context that causes the Bad Block Locator Utility to recreate the SDBSF, for example, /EXERCISE. Search string cannot be null Facility: EDT, EDT Editor Explanation: You asked EDT to search for nothing. User Action: Reenter the command specifying a search string.
SEARCHFAIL
error searching for 'filename' Facility: ACCOUNTING, Accounting Utility Explanation: The specified file could not be found. A subsequent error message explains why. User Action: None.
SEARCHFAIL
error searching for 'filespec' Facility: Shared by several facilities Explanation: The specified file could not be found. A subsequent error message explains why. User Action: Take corrective action based on the associated message.
SECINTFAI
secondary interlock failure in queue Facility: LIB, Library Facility Explanation: Secondary interlock failed (severe error) retry-cnt times in a row. The queue is not modified. This condition can occur only when the queue is in memory being shared between two or more processors. User Action: Wait until the queue is free, then retry the operation.
SECOUT
error code of 'xx' parsing journal file Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed because of the error represented as 'xx'. User Action: Correct the error (represented as xx) and retry.
SECREFNEG
section reference count went negative Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SECTBLFUL
section table (process/global) is full Facility: SYSTEM, VMS System Services Explanation: The system space allocated to maintain information about sections is full; no more sections can be created. User Action: If you have created many private sections, you may have to delete sections when they are no longer needed. If the error occurs while a global section, in particular a system global section, is being created, this message may indicate that not enough space is allocated at system generation for the section tables. Notify the system manager of the deficiency.
SECTRESTORED
'count' procedures, 'count' variables, 'count' keys restored Facility: VAXTPU, VAX Text Processing Utility Explanation: The indicated items have been successfully restored from a section file. User Action: None.
SECTSAVED
'count' procedures, 'count' variables, 'count' keys saved Facility: VAXTPU, VAX Text Processing Utility Explanation: The indicated items have been saved in a section file. User Action: None.
SECTUNDEFPROC
saved 'count' undefined procedures, 'count' ambiguous symbols Facility: VAXTPU, VAX Text Processing Utility Explanation: The saved section file contains one or more undefined procedures or ambiguous symbols. User Action: Define the named procedures and symbols and save the section file again. See command on input line 'linenumber' of page 'pagenumber' of file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: This is a standard error message line that specifies the location of an error-related command in the input file. This message indicates the name of the input file (filename) in which the command is located, and the file page number and line number where the error occurs. User Action: Find and correct the invalid command.
SEG
overlapping segments or segmented key must be string for key = 'nnn' Facility: RMS, VMS Record Management Services Explanation: The number of key elements specified by a key definition XAB is greater than one, and the key data type is not STG. Or, the key segments overlap and prolog 3 is specified. User Action: The status value (STV) field of the FAB provides the key of reference of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
SEG_FAIL
process failed prior to voting Facility: DDTM, DECdtm Transaction Manager Explanation: The transaction was aborted because a process or image within the transaction failed. User Action: Retry the transaction after the problem with the process or image has been corrected. Select complete lines only Facility: EDT, EDT Editor Explanation: You used the SELECT line range specifier with a line mode command such as COPY, FILL, MOVE, PRINT, TAB ADJUST, or WRITE. However, the select range that is active had at least one partial line. The select range must include only complete lines when it is used with line mode commands. User Action: Reenter the command specifying a select range that includes complete lines. Select range is already active Facility: EDT, EDT Editor Explanation: You attempted to establish a select range when one is already in effect. User Action: None.
SELRANGEZERO
select range has 0 length Facility: VAXTPU, VAX Text Processing Utility Explanation: The range you selected for the built-in procedure SELECT_RANGE has a length of 0; therefore, no characters were selected. User Action: None.
SEMALRMAX
semaphore is already at its maximum value Facility: PPL, Parallel Processing Facility Explanation: The semaphore value cannot be incremented further. User Action: Recode the program to ensure that only the correct maximum number of PPL$INCREMENT_SEMAPHORE requests are entered.
SEMANTICS
inconsistent usage of RMS Semantics Facility: RMS, VMS Record Management Services Explanation: RMS XABITM item codes for stored semantics or access semantics have been used in an inconsistent manner. User Action: This message indicates a coding error. Check the documentation on the use of RMS semantics and verify that the application is correctly calling RMS.
SEMININON
semaphore initial value must be non negative Facility: PPL, Parallel Processing Facility Explanation: An improper initial value is specified. User Action: Recode your program to ensure that the correct value is passed.
SENDABORT
no message sent Facility: MAIL, Mail Utility Explanation: You pressed Ctrl/C while sending a mail message. User Action: None.
SENDERR
error sending to user 'user-name' Facility: MAIL, Mail Utility Explanation: An error occurred when you attempted to send mail to the specified user. This message is usually accompanied by a system error message indicating the reason for the failure. User Action: None.
SENDFAIL
unable to send to subprocess Facility: VAXTPU, VAX Text Processing Utility Explanation: The operation to write to the mailbox for the subprocess's input failed. User Action: Recreate the subprocess.
SEQ
primary key out of sequence (SEQ access) Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $PUT service specified sequential access, but the primary key value of the record is less than the previous record entered. $PUT operations in sequential access mode must be in ascending order of primary key value. User Action: Modify the program, if necessary, to detect and respond to the condition. Correct the program and use the $PUT system service to put records in ascending order of the primary key value.
SEQ
record not in order Facility: CONVERT, Convert Utility Explanation: You have specified /NOSORT, but the primary keys are not in ascending order. User Action: Specify /SORT, or specify /NOFAST.
SEQNCE
illegal record sequence in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A module contained an illegal sequence of object records. User Action: Submit a Software Performance Report on the appropriate language translator.
SEQNCE
illegal record sequence in module 'module-name' in 'library filespec' Facility: LIBRAR, LIBRARY Command Explanation: The object module you want to insert is illegally formatted. User Action: Recompile the object module before inserting it into the library.
SEQUENCE
illegal record sequence in module 'module' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR). Sequence increment must be less than 65,536 Facility: EDT, EDT Editor Explanation: You specified a number as the :increment specifier for the /SEQUENCE qualifier that is too large. User Action: Reenter the command specifying a smaller number. Sequence number must be less than 65,536 Facility: EDT, EDT Editor Explanation: You specified a number as the :integer specifier for the /SEQUENCE qualifier that is too large. User Action: Reenter the command specifying a smaller number.
SEQUENCE2
illegal record sequence Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable image you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
SERUNAV
service 'service-name' not currently available Facility: LAT, LAT Facility Explanation: A LAT connection was attempted to a service that is known by the local node but that is not currently available. User Action: Determine the availability problem with the remote node offering the specified service. Possibly the specified service has disabled connection requests.
SERVE_ERR
error serving device DDcnn: R0 status = nnnnnnnn Facility: STACONFIG, Standalone Configure Process Explanation: A newly discovered device that fits all the serving parameters could not be served. If the value in the R0 status is 00000084, the device was not served because the server is not loaded. User Action: Check to see that the MSCP server has been loaded properly. Use the SHOW DEV/SERVED command or examine SCS$GL_MSCP. This global address should be a valid system space address. If the R0 status is other than 84, get the corresponding message (using EXIT nn) and find out what is wrong with the device.
SERVEREXIT
requested audit server shutdown Facility: AUDSRV, Audit Server Explanation: The audit server has been shut down. User Action: None. This is an informational message.
SERVEXISTS
service name already exists Facility: LAT, LAT Facility Explanation: You attempted to create a service using the name of a service that already exists on the local node. User Action: Create a service using a different name.
SESLIM
session limit reached Facility: LAT, LAT Facility Explanation: A LAT connection attempt failed because the current LAT session limit has already been reached. User Action: Use the LATCP command SET NODE/SESSION_LIMIT=OUTGOING to increase the session limit or wait for a session slot to become available. Refer to the VMS LAT Control Program (LATCP) Manual for more information.
SETIMR
error setting timer Facility: JBC, Job Controller Explanation: The job controller encountered an error setting a timer for a job submitted with the /AFTER qualifier. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
SETKEY
keypad state has been set to 'state' Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified keypad state is set. User Action: None.
SETLIMIT
too many volumes on volume set Facility: MOUNT, Mount Utility Explanation: The maximum permissible number of volumes in a volume set (255) has been reached. User Action: Find the other volumes in the set and use them first.
SETMAX
value set to maximum for parameter 'name' Facility: SYSGEN, System Generation Utility and SYSBOOT, System Bootstrap Facility Explanation: The value entered in a SET command exceeds the maximum allowed. User Action: Verify the intended number.
SETMIN
value set to minimum for parameter 'name' Facility: SYSGEN, System Generation Utility and SYSBOOT, System Bootstrap Facility Explanation: The value entered in a SET command is less than the minimum allowed. User Action: Verify the intended number.
SEVINVALD
illegal severity value Facility: SMI, System Management Integrator/Server Explanation: An attempt was made to add an entry in the system loadable images database with an invalid value for the "severity" parameter. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
SHADBOOTFAIL
shadowing failed to boot from system disk shadow set
Facility: BUGCHECK, System Bugcheck
Explanation: Any of the following conditions can cause this error:
o A failure to allocate memory.
o One or more critical devices is inaccessible.
o The boot device is the target of a full copy operation.
o The boot device is not a source member of the existing shadow
set.
User Action: Try one or more of these user actions:
o If the boot device is the target of a full copy operation or
is not a source member of the existing shadow set, change the
device name in VMB to be a source member and reboot the node.
o If the boot device is a source member of the existing shadow
set, check the booting device's connections to all other shadow
set members.
o If all device and system connections are fine, check the SYSGEN
parameter settings for inappropriate memory configurations.
SHADDETINCON
SHADOWING detects inconsistent state Facility: BUGCHECK, System Bugcheck Explanation: The volume shadowing software reached an unrecoverable or inconsistent situation because the software failed an internal inconsistency check. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. If the system is configured to produce a memory dump, include the dump file with the SPR.
SHARCONF
the /SHARED qualifier conflicts with facility number Facility: MESSAGE, Message Utility Explanation: You have specified the /SHARED qualifier on the facility definition with a facility number other than zero. User Action: Remove the /SHARED qualifier from the facility definition.
SHASINGMBR
single member system shadow set formed Facility: INIT, INITIALIZE Command Explanation: The shadow set membership is changing to form a single-member shadow set consisting of only the boot device. User Action: None.
SHMGSNOTMAP
shared memory global section not mapped during creation Facility: SYSTEM, VMS System Services Explanation: A shared memory global section creation request did not specify a virtual address range into which the section is to be mapped. The section cannot be initialized unless it is mapped. User Action: Specify an input address range to map the section. Set RELPAG to zero.
SHMNOTCNCT
shared memory not connected Facility: SYSTEM, VMS System Services Explanation: The shared memory specified, that is, that part of the name to the left of the colon(:), is not connected to this processor. This error also occurs when colons are inadvertently placed in common event flag cluster, mailbox, or global section names. User Action: Connect the shared memory.
SHOFIL
unable to open output for SHOW or LIST Facility: NCP, Network Control Program Explanation: VMS RMS returned an error when attempting to open the output file for either a SHOW or LIST command. The VMS RMS error code describes the error condition. User Action: Take corrective action based on the accompanying VMS RMS message.
SHOIO
error writing output file for SHOW or LIST Facility: NCP, Network Control Program Explanation: RMS returned an error when attempting to write to the output file for either a SHOW or LIST command. The RMS error code describes the error condition. User Action: Take corrective action based on the accompanying message.
SHORTBLOCK
save set block is too short Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered a physical block shorter than the value recorded for the save set. Data in the save set is corrupted. User Action: None. Save set data has been lost.
SHORTDUMP
the dump only contains 'm' out of 'n' pages of physical memory Facility: SDA, System Dump Analyzer Explanation: This message occurs if the system dump file is not large enough to accommodate all of physical memory. The number of physical pages SDA can analyze is represented by 'm'. User Action: Refer to the VMS System Dump Analyzer Utility Manual for information on changing the size of the system dump file.
SHOW_ERR
error during show Facility: AUTHORIZE, Authorize Utility Explanation: This message is issued with other messages. User Action: Take corrective action based on the accompanying messages.
SHOWERR
SHOW command error Facility: MONITOR, Monitor Utility Explanation: An error occurred during execution of the SHOW command of the Monitor Utility. More information may be obtained by examining the accompanying message. User Action: Correct the error indicated by the accompanying message and rerun the SHOW command. Most such messages represent status values returned to MONITOR from the Run-Time Library Screen Management Procedures.
SHOWERR
unable to complete show command Facility: AUTHORIZE, Authorize Utility Explanation: The AUTHORIZE command SHOW could not be completed. This message should be accompanied by a VMS RMS message that identifies the specific reason for the error. User Action: Correct the condition identified by the RMS message and reenter your command.
SHR
invalid file sharing (SHR) options Facility: RMS, VMS Record Management Services Explanation: The file sharing field of the FAB contains an invalid value for the file organization and the specified access. User Action: Verify that the call to the VMS RMS service is coded correctly.
SHRCNTNEG
PFN share count negative Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SHRCPYIGN
COPY value for /SHARE qualifier ignored, using NOCOPY Facility: LINK, Linker Utility Explanation: The /SHARE=COPY qualifier may no longer be specified in order to obtain an image-private copy of a shareable image. User Action: None.
SHRIDMISMAT
ident mismatch with shareable image Facility: SYSTEM, VMS System Services Explanation: The global section match found in a shareable image does not correspond with the global section match in the executable image. User Action: Relink the executable image.
SHRINSYS
shareable images cannot be linked into a system image Facility: LINK, Linker Utility Explanation: An attempt is made to link a shareable image with a system image. User Action: Do not link a shareable image with a system image.
SHRPSCLNG
Psect 'string' has length 'number' in module 'module name' file 'file name' which exceeds length 'number' in shareable image 'image name' Facility: LINK, Linker Utility Explanation: In a linking operation that produces an executable image including a shareable image as input, the linker now issues an error message when an input-object module defines a COMMON area to have a greater length than the COMMON area of the same name defined in the input shareable image. Previously, the linker did not check multiple definitions of the same COMMON area for length descrepancies. User Action: Modify the length of the program section defining COMMON area (such as those used in VAX BASIC, VAX PL/I, VAX FORTRAN, and VAX C) to be less than or equal to the length of that program section in the shareable image.
SHRPSCREF
reference to psect 'psect-name' is not position-independent in psect 'psect-name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A reference to a psect in a shareable image is made without the use of .ADDRESS or general addressing mode. User Action: Correct the reference and relink.
SHRSEPCLU
shareable image being placed in separate cluster Facility: LINK, Linker Utility Explanation: A shareable image is put in a cluster with one or more object modules using the CLUSTER= option. User Action: Modify the CLUSTER= option so that it specifies either a single shareable image or one or more object modules.
SHRSYMREF
reference to symbol 'symbol-name' is not position-independent in psect 'psect-name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A reference to a symbol in a shareable image is made without the use of general addressing mode. User Action: Correct the reference to use general addressing mode.
SHRSYMTRA
attempted .TRANSFER of shareable image symbol 'symbol-name' illegal in psect 'psect-name' offset 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A symbol from another shareable image is specified in the .TRANSFER directive. User Action: Link with the object modules containing the symbol rather than the shareable image.
SHUT
local or remote node no longer accepting connects Facility: SYSTEM, VMS System Services Explanation: The local or remote node is in a state in which it no longer accepts connections. (This is not because of a lack of resources.) User Action: None. Try again later.
SHUTDOWN
OPCOM shutting down. Requested by operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: OPCOM is announcing the orderly shutdown of its activities. User Action: Be aware that OPCOM will not be available to perform requests.
SIGNAL_Q_FULL
unable to process condition variable signal Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A call to the pthread_cond_signal_int_np or cma_cond_signal_int routine cannot be performed because there are too many outstanding requests. User Action: Calls to the cma_cond_signal_interrupt routine are occurring too frequently. Reduce the number of calls or slow the rate of their arrival.
SIGNO_ARG
signal with no arguments Facility: LIB, Library Facility Explanation: A call is made to LIB$SIGNAL or LIB$STOP with no arguments; LIB$_SIGNO_ARL is substituted. User Action: None.
SIZ
invalid key size for key = 'nnn'
Facility: RMS, VMS Record Management Services
Explanation: An invalid key size is specified in a key definition
XAB. The size is invalid for one of the following reasons:
o It is greater than 255.
o It is zero for key data type STG, DSTG, COL, or DCOL.
o It is greater than 16 for key data type PAC DPAC.
o It is other than zero or two for key data types BN2, IN2, DBN2,
or DIN2.
o It is other than zero or four for key data types BN4, IN4,
DBN4, or DIN4.
o It is other than zero or eight for key data types BN8, IN8,
DBN8, or DIN8.
User Action: The status value (STV) field of the FAB provides the
key of reference of the XAB in error. Verify that the call to the
VMS RMS service is coded correctly.
SKC
.ENDIF/.ELSE not in same file as .IF/.IFNOT: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to use associated conditional commands in separate files. User Action: Put the associated conditional commands in the same file.
SKPDAT
image data (records not beginning with "$" ignored) Facility: CLI, Command Language Interpreter (DCL) Explanation: A command procedure contained lines that were not DCL commands (that is, the lines did not begin with dollar signs) or an image terminated without reading input data records. User Action: Check the command procedure for missing dollar signs before commands. Or check for the absence of the command that should read the data records.
SLOWRESP
system failed to respond within one-half second Facility: SMI, System Management Integrator/Server Explanation: A clusterwide CONFIGURATION SET TIME command is entered, and one of the cluster members took longer than one-half second to respond. The time is set and the operation proceeded with the next cluster member. User Action: Verify that the time was set within acceptable tolerances with a SYSMAN CONFIGURATION SHOW TIME command, and reenter the SET TIME command if desired.
SMALLPAGE
terminal size 'number' columns by 'lines' is too small Facility: FDL, Edit/FDL Utility Explanation: The value for x must be 80 or greater, and the value for y must be 24 or greater on video terminals. User Action: Set the terminal width to 80 or greater, and set the page length to 24 or greater with video terminals; with nonvideo terminals, any page length is acceptable.
SOFTRERRS
'n' recoverable media errors occurred reading 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility successfully recovered from read errors in the specified save set the specified number of times by rereading the blocks in error. User Action: None. However, if the number of errors appears excessive, consider retiring the save set medium when convenient. Software is Closing Virtual Circuit Facility: VAXport, VAXport Driver Explanation: The VAXport driver closes the virtual circuit to the remote port. User Action: Check error log entries for the cause of the virtual circuit closure. Faulty transmission or reception on both paths, for example, causes this error and may be detected from the one or two previous error log entries noting bad paths to this remote node. Software Shutting Down Port Facility: VAXport, VAXport Driver Explanation: The VAXport driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Check other error log entries for the possible cause of the port reinitialization failure.
SOFTWERRS
'n' recoverable media errors occurred writing 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility recovered successfully from uncorrectable write errors in the specified save set the specified number of times by rewriting the blocks in error. User Action: None. However, if the number of errors appears excessive, consider retiring the save set medium when convenient.
SOLCONNECT
error connecting to file SYS$SYSTEM:DNS$DEFAULT_FILE.DAT Facility: DNS, Distributed Name Service Clerk Service Explanation: The solicitor attempted to check the configuration file for errors, but was unable to connect to the file. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
SOLOPEN
error opening file SYS$SYSTEM:DNS$DEFAULT_FILE.DAT Facility: DNS, Distributed Name Service Clerk Service Explanation: The solicitor attempted to check the configuration file for errors, but was unable to open the file. User Action: A specific VMS error immediately follows the error text of this message. Take corrective action based on the accompanying VMS error message.
SOLREADLINE
error reading line in file SYS$SYSTEM:DNS$DEFAULT_FILE.DAT Facility: DNS, Distributed Name Service Clerk Service Explanation: Invalid configuration information was found in the DNS configuration file. User Action: You might need to edit the configuration file DNS$DEFAULT_FILE.DAT in SYS$SYSTEM. Make sure that the file contains only configuration information for the DNS clerk. You can reconfigure the system using the SYS$STARTUP:DNS$CHANGE_DEF_ FILE.COM command file. After making corrections, you must stop the DNS clerk (using SYS$STARTUP:DNS$CLERK_STOP.COM) and restart it (using SYS$STARTUP:DNS$CLERK_STARTUP.COM).
SOLTIMEOUT
timed out waiting for DNS$ADVER to read mailbox message from DNS$SOLICIT_MBX Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS solicit process was unable to communicate with the advertiser process. This may happen when the advertiser process (DNS$ADVER) is unable to start properly, or has terminated abnormally. User Action: Make sure the DNS$ADVER process is running. If it is not, then restart it using the SYS$STARTUP:DNS$CLERK_ STARTUP.COM command file. If it is running, then stop it using SYS$STARTUP.DNS$CLERK_STOP.COM, and then restart it. If this does not work, call the Digital Services Group.
SOLWAITING
waiting for DNS$ADVER to read mailbox message from DNS$SOLICIT_MBX Facility: DNS, Distributed Name Service Clerk Service Explanation: During the startup phase of the DNS clerk, you get this message if your system is heavily loaded. This informational message indicates that startup has taken longer than anticipated, but has not yet failed. User Action: None.
SORTALLOCMEM
insufficient virtual memory to sort all LBN entries Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: When the Analyze/Disk_Structure Utility determines that blocks have been multiply allocated, it attempts to generate a report, sorted by logical block number, of the multiply allocated blocks. The sort is performed in-memory and requires virtual memory. If the utility fails to allocate the needed virtual memory, it displays this error message and produces a partially sorted report. User Action: If the partially sorted report is not acceptable, correct the condition that caused the error and reenter the command. You may need to increase the page file quota of the account or the SYSGEN parameter VIRTUALPAGECNT.
SOURCELINE
at source line 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: This message gives the source line number of the error, which occurred during compilation. User Action: None.
SPAWNED
process 'process-name' spawned Facility: CLI, Command Language Interpreter (DCL) Explanation: This message is output by the DCL command SPAWN when it spawns a subprocess. User Action: None.
SPCIVC
invalid collating sequence specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: The syntax you specified for your collating sequence is incorrect. User Action: Correct the syntax and reenter your specification.
SPCIVD
invalid data type at line 'number' Facility: SORT, Sort/Merge Utility Explanation: In your specification file text, you incorrectly specified a data type or you specified a data type that is not recognized by SORT/MERGE. User Action: Correct your specification file text.
SPCIVF
invalid field specification at the line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly specified the text in the /FIELD clause in your specification file. User Action: Correct your specification file text.
SPCIVI
invalid include or omit specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly specified the text in an /OMIT or /INCLUDE clause. User Action: Correct your specification file text.
SPCIVK
invalid key or data specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly specified the text in a /KEY or a /DATA clause. User Action: Correct your specification file text.
SPCIVP
invalid sort process at line 'number'
Facility: SORT, Sort/Merge Utility
Explanation: Two possible explanations exist:
o The sort process you specified in your specification file is
not a record, tag, address, or indexed sort.
o You specified a nonrecord sort (tag, address, or index), which
is invalid if you are not using a random access device, if you
used the record interface on input, or if you specified your
own comparison or equal-key routine.
User Action: Specify the correct sort process for your sort.
SPCIVS
invalid specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You specified an invalid keyword in your specification file text. User Action: Correct your specification file text.
SPCIVX
invalid condition specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly specified the syntax in a /CONDITION clause in your specification file. User Action: Correct your specification file text.
SPCMIS
invalid merge specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly specified a sort process for a merge operation. User Action: Correct your specification file text.
SPCOVR
overridden specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: In combination with specification file instructions, you specified either SORT/MERGE qualifiers or callable arguments. These qualifiers or arguments override any corresponding entries in the specification file text. This message is a warning only and will not halt processing. User Action: None.
SPCSIS
invalid sort specification at line 'number' Facility: SORT, Sort/Merge Utility Explanation: You incorrectly requested sequence checking in a sort operation. User Action: Correct your specification file text.
SPDNOTSET
speed not set Facility: REM, Set Host Facility Explanation: The selected speed is not supported by the terminal. User Action: For specific information on supported speeds consult the hardware manual for your terminal. Select a supported speed and reenter the command.
SPECDEV
can't add component - contains device name Facility: SYSMAN, Cluster System Management Utility Explanation: You attempted to add a startup component file that specifies a device name in the file specification. User Action: Reenter the command without the device specification.
SPECDIR
can't add component - contains directory name Facility: SYSMAN, Cluster System Management Utility Explanation: You attempted to add a startup component file that specifies a directory name in the file specification. User Action: Reenter the command without the directory specification.
SPECIFY
specify option ('valid-options')
Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered a fatal error. You
must select a recovery action. If the QUIT option is selected, the
utility will terminate. If the CONTINUE option is selected, the
utility will ignore the error. If the RESTART option is selected,
the utility will restart the operation at the beginning of the
current save set volume.
User Action: Evaluate the preceding errors and select one of the
options listed in the message. If the utility is executing as an
interactive job, enter the option in response to the prompt on
SYS$COMMAND. If the utility is executing as a batch job, use the
DCL command REPLY to enter the option.
SPECNODE
can't add component - contains node name Facility: SYSMAN, Cluster System Management Utility Explanation: You attempted to add a startup component file that specifies a node name in the file specification. User Action: Reenter the command without the node specification.
SPECWILD
can't add component - contains wildcards Facility: SYSMAN, Cluster System Management Utility Explanation: You attempted to add a startup component file that contains a wildcard character in the file specification. User Action: Reenter the command without the wildcard characters.
SPL
spool or submit of command file failed on $CLOSE Facility: RMS, VMS Record Management Services Explanation: The spool or submit command file option that is specified on a $CLOSE operation failed. If the IFI field of the FAB is zero, the file is closed successfully. User Action: The status value (STV) field of the FAB contains a code that provides more information about the condition. Take corrective action based on this status code.
SPLACQERR
spin locks of higher rank already owned by CPU Facility: SMP, Symmetric Multiprocessing Explanation: A processor attempted to acquire a spin lock out of order. That is, the current spin lock acquisition is being made on a spin lock of lower rank than one that is already held by the current processor. The multiprocessor system could deadlock if spin locks are allowed to be acquired out of order. User Action: Analyze the crash dump, and determine which lock is being acquired and which locks are already owned by the acquiring processor. Correct your code so the locks are acquired in the correct order. One probable situation that can occur is when a processor acquired a lock many times during a driver's execution, then incorrectly executed a conditional release of the lock rather than unconditionally releasing it as might have been intended. This leaves the spin lock still owned by this processor. If the processor subsequently attempts to acquire a lower-ranked spin lock while still owning the previous lock, the operating system prevents a potential deadlock by issuing this bugcheck. Correct the driver code to prevent this, or similar, situations from occurring. Note that this bugcheck applies only to static spin locks, not to device locks. Device locks are not subject to the ranking rules that static spin locks (which include fork locks) are subject to.
SPLIPLHIGH
current IPL exceeds synchronization IPL of desired spin lock Facility: SMP, Symmetric Multiprocessing Explanation: A processor is attempting to acquire a spin lock from an IPL that is higher than the synchronization IPL associated with that spin lock. User Action: Analyze the crash dump and determine the code sequence that is trying to acquire the spin lock from the excessively high IPL. It might be, for instance, a case where driver code previously raised the IPL to accomplish something else, then failed to lower the IPL again prior to acquiring the lock that is synchronized by the lower IPL. Note that under no circumstances can a driver lower the IPL below that level from which it originally raised the IPL, unless it does so by creating a fork process.
SPLIPLLOW
IPL has fallen below level of owned spin locks Facility: SMP, Symmetric Multiprocessing Explanation: A processor is attempting to release a spin lock while executing at an IPL that is below the synchronization IPL associated with that spin lock, indicating that local processor synchronization is compromised. User Action: Analyze the crash dump and determine the point where your code has lowered the IPL below the level associated with the spin lock that is held. Correct the code such that IPL is not lowered before the spin lock is released.
SPLRELERR
spin lock to be released is not owned Facility: SMP, Symmetric Multiprocessing Explanation: A processor is attempting to release ownership of a spin lock that is not currently owned by that processor. User Action: Analyze the crash dump and determine why that spin lock wasn't owned when the processor tried to release it. Correct the code to eliminate the problem. The following situation is one that would cause this bugcheck. A processor, while executing a driver, might build up multiple, nested acquisitions of this spin lock through calling several levels of subroutine, each acquiring ownership of the spin lock. If one of the called subroutines incorrectly executes an unconditional release of this spin lock, then a caller of that subroutine tries to release the spin lock later, believing the spin lock to be held. The system checks for bugs because the code is trying to release a spin lock that the processor no longer owns.
SPLRSTERR
spin lock to be conditionally released is not owned Facility: SMP, Symmetric Multiprocessing Explanation: A processor is attempting to release a single level of ownership (restore) for a spin lock that is not currently owned by that processor. User Action: Analyze the crash dump and determine why that spin lock was not owned when the processor tried to release it. Correct the code to eliminate the problem. The following situation is one that would cause this bugcheck. A processor, while executing a driver, might build up multiple, nested acquisitions of this spin lock through calling several levels of subroutine, each acquiring ownership of the spin lock. If one of the called subroutines incorrectly executes an unconditional release of this spin lock, then a caller of that subroutine will try to release the spin lock later, believing the spin lock to be held. The system checks for bugs because the code is trying to release a spin lock that the processor no longer owns.
SPNAMLNG
PSECT module 'module-name' file 'library filespec' has illegal length 'nnn' Facility: LIBRAR, LIBRARY Command Explanation: The PSECT name length exceeds the maximum length of 31 characters. User Action: Change the PSECT name length, recompile the module, and reenter the command line.
SPTERRS
errors occurred writing the system page table to the dump file Facility: SDA, System Dump Analyzer Explanation: The first block of the dump file contains information indicating that there were errors while writing the memory associated with the system page table to the dump file. User Action: None. The dump file is probably not useful for analysis.
SPTFULL
system page table is full Facility: SYSGEN, System Generation Utility Explanation: There is no space available in the system page table to allocate a system page for the device (requested by DPT$_MSVP in the driver prologue table). User Action: Reboot the system, stopping in SYSBOOT, and increase the value of the system page table parameter (SPTREQ).
SPTNOTFND
system page table not found in dump file Facility: SDA, System Dump Analyzer Explanation: The operating system was unable to copy the system page table to SYSDUMP.DMP when it failed. As a result, SDA could not examine the dump file. User Action: None. The system page table is vital to SDA initialization.
SPWNIO
shared input or output files are not allowed - respecify Facility: CLI, Command Language Interpreter (DCL) Explanation: You used a file that is already opened by DCL as input or output to SPAWN. User Action: If input or output to DCL is SYS$INPUT or SYS$OUTPUT, do not specify the input or output qualifier. See the SPAWN command in the VMS DCL Dictionary for details on input and output interpretation.
SQO
operation not sequential (SQO set) Facility: RMS, VMS Record Management Services Explanation: An attempt is made to perform random access to a file opened or created with the SQO file processing option; the file can be processed only with sequential operations. User Action: Verify that the call to the VMS RMS service is coded correctly.
SQUALERR
more than one statistic qualifier specified for 'class-name' class Facility: MONITOR, Monitor Utility Explanation: The MONITOR request specified more than one of the statistic qualifiers (/CURRENT, /AVERAGE, /MINIMUM, /MAXIMUM, /ALL) for the indicated class. Only one of these qualifiers may be specified per class. User Action: Reenter the MONITOR request, specifying only one statistic qualifier per class.
SQUROONEG
square root of negative value user PC 'location' Facility: MTH, Mathematics Facility Explanation: A mathematics library procedure is called to evaluate the square root of a negative number. The result returned is the reserved operand, minus zero. User Action: Locate the call to the library procedure that returned the error. Correct your program making the argument zero or positive.
SRCLIN
the source input entry is 'string' Facility: BAD, Bad Block Locator Utility Explanation: This message is associated with the DUPBLKNUM error message and displays the portion of the command line that is in error. The duplicate block is ignored. User Action: None.
SRCMEM
only source member of shadow set cannot be dismounted Facility: DISMOUNT, DISMOUNT Command Explanation: An attempt was made to dismount a shadow set member that was the only valid source member of the set. User Action: If there is only one shadow set member, it cannot be dismounted. To dissolve the shadow set, dismount the virtual unit. If there is more than one member, remove a full member and wait for copy operations to complete before dismounting a member.
SRTIWA
insufficient space; specification file is too complex Facility: SORT, Sort/Merge Utility Explanation: The work area is too small for the number of instructions that you have specified in your specification file. User Action: Simplify your specification file text by reducing, for example, the number of /FIELD clauses.
SRVALLOAD
the MSCP server is already loaded Facility: SYSGEN, System Generation Utility Explanation: You attempted to load the MSCP server using the MSCP command within SYSGEN, and the server is already loaded using the SYSGEN parameter MSCP_LOAD. The MSCP server has been loaded the recommended way. This warning is printed to remind you that this command is obsolete. User Action: If this warning is printed because the MSCP command is still in a startup command procedure, this command should be edited out of the procedure.
SRVCNODE
service 'service-name' not offered by node 'node-name' Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a specified service and node failed because the node does not offer the specified service. User Action: Retry the connection request and specify a node that offers the desired service.
SRVDIS
outgoing connections are disabled Facility: LAT, LAT Facility Explanation: An outbound LAT connection was attempted when outbound connections are disabled. User Action: Enable connections using the LATCP command SET NODE. Refer to the VMS LAT Control Program (LATCP) Manual for more information.
SRVMISMATCH
monitor server on remote node is an incompatible version Facility: MONITOR, Monitor Utility Explanation: You attempted to monitor a node running on an incompatible version of the Monitor Utility. This can occur in a cluster if all of the nodes are not running the same Version of the VMS operating system. This is only a warning and the Monitor request will continue to monitor other requested nodes running the same version as the node on which the request was initiated. User Action: None.
SSCHANGE
unexpected end of save set on 'device-name' Facility: BACKUP, Backup Utility Explanation: Internal consistency checks have detected that the current save set has ended, and BACKUP is reading a new save set. User Action: You will be prompted to continue or quit. If you choose the continue option, BACKUP will continue reading the new save set.
SSERROR
'service-name' system service error Facility: MONITOR, Monitor Utility Explanation: The indicated system service returned a failing status code. The status code appears as a linked message that follows this message. User Action: Check the description of the failing status code for the indicated system service in the VMS System Services Reference Manual. Correct the condition causing the failure, if possible, and reenter the MONITOR request. Otherwise, submit a Software Performance Report (SPR).
SSFAIL
system service failure exception, status = 'xxxxxxxx', PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: A call to a system service returned an error or a severe error status code. The image has enabled system service failure exception mode. This mode allows an image to signal a software exception when a failure occurs in a system service call. The operating system displays the failure status code, the PC, and the PSL at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine the instruction that caused the error.
SSR
restricted character '^\' (octal 34) encountered in text, ignored Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR encountered a restricted character in the input file. User Action: Remove the restricted character. You cannot use it in a DSR input file.
SSRVEXCEPT
unexpected system service exception Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
STABLEEXC
equal-key routine and stable option cannot both be specified Facility: SORT, Sort/Merge Utility Explanation: You specified both an equal-key routine and the SOR$M_STABLE option when only one or the other is allowed. User Action: Specify either the equal-key routine or the stable option.
STACKDUMP
non-symbolic stack dump follows Facility: TRACE, Traceback Facility Explanation: This informational message precedes a traceback dump. The accompanying message indicates why the traceback is nonsymbolic. The nonsymbolic stack dump is displayed following this message. User Action: None.
STACKOVER
stack overflow during compilation Facility: VAXTPU, VAX Text Processing Utility Explanation: The program is too complex for VAXTPU to parse. The program may be written in a language other than VAXTPU. User Action: If you are compiling a valid VAXTPU program, please submit a Software Performance Report describing the conditions that led to the error.
STACKOVF
attempted stack overflow was detected Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A thread overflowed its stack. User Action: Create the erring thread with a larger stack or redesign the code to require less stack space; for example, nest your calls less deeply or allocate less storage on the stack.
STALITUDF
stack of undefined literal 'number' in record 'number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An attempt is made to stack an undefined literal. User Action: Submit a Software Performance Report on the appropriate language processor.
STARTDELETE
starting file deletion pass Facility: BACKUP, Backup Utility Explanation: The Backup Utility is beginning to delete files in response to the /DELETE qualifier. User Action: None.
STARTED
queue already started
Facility: JBC, Job Controller
Explanation: The queue cannot be started because it is already
running.
User Action: None.
Starting memory dump . . .
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS operating system reached an unrecoverable or
inconsistent situation and is beginning a bugcheck sequence. If
the system is configured to take a memory dump, messages similar
to the following messages might accompany the dump:
Header and error log buffers dumped . . .
SPT & GPT dumped . . .
System space (S0) dumped . . .
Global pages dumped . . .
'process-name' dumped . . .
'process-name' dumped . . .
**** Memory dump complete . . . .
These messages give information about the progress of the writing
of that dump. These messages appear if the SYSGEN parameter
DUMPSTYLE is set so that a selective dump (that is, a dump of
selected portions of system space and process address space in
virtual memory) is written.
A selective dump is similar to a complete dump when writing the
dump header and system error log buffers. Following these items,
it differs from the complete dump by immediately writing out
the system and global page tables. The page tables and system
space are the minimum content needed to analyze a crash dump;
configuring your dump file so that this minimum cannot be dumped
causes the dump to be useless.
The global pages written during the dump are written separately
from the processes that might reference them. This allows a single
copy of each global page to exist in the dump. Processes are
selected to have their P0 and P1 spaces dumped in the following
order: current processes (if any) on the CPU that initiated the
bugcheck, special system processes, current processes (if any) on
other CPUs, and any other processes. A message giving the name of
the process follows the writing of the dump for that process if it
completed successfully.
Global and process pages are optional when writing a dump in
that the dump may still yield useful information if they are not
present. However, Digital recommends that you use a dump file at
least as large as the one created by AUTOGEN. If the dump file is
not large enough to hold all process and page files, the dump is
still considered to have finished normally.
User Action: None. However, if the situation that caused the
VMS operating system to write the memory dump indicates that you
should submit a Software Performance Report (SPR), a copy of the
dump file should accompany the SPR.
Starting memory dump . . . Memory dump complete
Facility: BUGCHECK, System Bugcheck
Explanation: The VMS operating system reached an unrecoverable or
inconsistent situation and is beginning a bugcheck sequence. If
the system is configured to take a memory dump, these messages
accompany the dump. No other messages appear if the SYSGEN
parameter DUMPSTYLE is set so that a full dump (that is, a dump of
all of physical memory) is written.
User Action: None. However, if the situation that caused the
system to write the memory dump indicates that you should submit
a Software Performance Report (SPR), a copy of the dump file just
written should accompany the SPR.
STARTRECORD
starting backup date recording pass Facility: BACKUP, Backup Utility Explanation: The Backup Utility completed a save or copy operation and is beginning to update back-up dates in response to the /RECORD qualifier. User Action: If the /SINCE=BACKUP or /BEFORE=BACKUP qualifiers are used, note that data will be lost if you restart the operation using the same output medium. If it is necessary to restart the operation because of a system failure, use another volume.
STARTUP
VMS startup begun at 'dd-mmm-yyyy hh:mm:ss.ss' Facility: STDRV, System Startup Driver Explanation: VMS has begun executing the system startup driver, which is used to start up individual VMS system processes and to start VMS after a reboot. User Action: None. This is an informational message.
STARTVERIFY
starting verification pass Facility: BACKUP, Backup Utility Explanation: The BACKUP Utility completed the operation on the current volume and is beginning to verify data in response to the /VERIFY qualifier. User Action: None.
STASMALLMEM
small memory system. Booted device must stay online during operation. Facility: BACKUP, Backup Utility Explanation: The amount of system memory is too small to lock all of standalone BACKUP into the working set. User Action: Ensure that the device from which standalone BACKUP booted stays online during the entire BACKUP operation.
STATENTSVD
software state not saved during powerfail Facility: BUGCHECK, System Bugcheck Explanation: Before power is lost, the volatile software state of the VAX processor is not completely saved in memory. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to one. User Action: Check all processor mechanisms related to the detection of a power failure. Be sure that no peripheral adapter recognizes an impending power failure before the processor does because, in that case, the processor would be prevented from handling the failing power condition.
STATE_UNK
transaction state UNKNOWN: xx (xx) Facility: LMCP, Log Manager Control Program Explanation: An attempt was made to dump a record that contained an unknown transaction state. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error and include a BACKUP save set containing the output of the LMCP DUMP command for the given log file and the output of the DCL DUMP command for the same log file.
STATOOLONG
truncating status line to 'count' characters Facility: VAXTPU, VAX Text Processing Utility Explanation: You have defined a window status line that is too long to fit within the boundaries of the current physical width of the terminal. The text has been truncated to fit on the screen. User Action: Redefine the status line to a shorter line of text.
STD
too many nested .NOTEs and/or .LISTs: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to nest more than 20 notes or 20 lists (or more than 7 within a footnote). User Action: Reduce the number of nested notes or lists.
STDISPIC
illegal non-relocatable displacement value in psect 'name' offset 'offset' Facility: LINK, Linker Utility Explanation: The linker encountered a nonrelocatable reference while linking what is intended to be a position-independent shareable image. User Action: Find the reference using the information in the message, and make the reference relocatable.
STGTRUNC
string truncated Facility: PATCH, Patch Utility Explanation: The Patch Utility truncated an ASCII string entry because it exceeded the current length mode or because the entry is inappropriate for the context in which it is specified. User Action: Correct the ASCII string and retry.
STILLKEYS
keys still point at data Facility: LBR, Librarian Subroutine Package Explanation: This warning message is generated by the Librarian routines. Keys in other indexes still point to the text. The call to LBR$DELETE_DATA did not delete the text. User Action: None. Processing continues.
STKNOTCHANGE
the stock associated with a form cannot be changed Facility: JBC, Job Controller Explanation: A DEFINE/FORM command for an existing form specified /STOCK with a new stock value while references to the form are still outstanding. User Action: Use the SHOW QUEUE/FULL command to locate existing references. Remove any outstanding references and reenter the DEFINE/FORM/STOCK request.
STKOVF
command procedures too deeply nested - limit to 32 levels Facility: CLI, Command Language Interpreter (DCL) Explanation: The maximum level of nesting of command procedures is exceeded. Too many procedures invoked other procedures. User Action: Simplify the command procedure hierarchy to reduce the level of nesting.
STKOVFLO
stack of 'number' pages falls below control region to 'address' Facility: LINK, Linker Utility Explanation: The memory allocation for P1 space does not allow enough room for the stack. User Action: Correct the allocation to allow enough room for the stack.
STMRECFMT
illegal stream record format in 'record' Facility: EXCHANGE, Exchange Utility Explanation: While processing a file with /RECORD_FORMAT=STREAM, the EXCHANGE utility found an invalid record. User Action: The input file might contain a record too large for an output stream file, or an input file is not a valid stream file. Use the correct /RECORD_FORMAT type for the file.
STNOTAVAIL
requested starting block number is not available Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility could not satisfy a /START_BLOCK request. User Action: Either the requested block is already contained inside a file, or it is larger than the largest block on the volume. Use the EXCHANGE DIRECTORY /FULL /ALL to discover the location and sizes of unused areas on the volume.
STPCLU
component file is cluster-wide Facility: SYSMAN, Cluster System Management Utility Explanation: A SYSMAN STARTUP command is entered with the environment set with the /CLUSTER qualifier. The /CLUSTER qualifier is ignored. User Action: None.
STPINVALD
illegal load step value Facility: SMI, System Management Integrator/Server Explanation: An attempt was made to add an entry in the system loadable images database with an invalid value for the "load step" parameter. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
STRCPYERR
unexpected error from string copy routine Facility: DIFF, DIFFERENCES Command Explanation: An unexpected error occurred during an RTL string copy operation. User Action: Submit a Software Performance Report (SPR). String delimiter must be nonalphanumeric Facility: EDT, EDT Editor Explanation: You used a letter, digit, or percent sign (%) as a string delimiter. User Action: Reenter the command using a valid string delimiter. String is not found Facility: EDT, EDT Editor Explanation: The string defined in the range specification cannot be found. User Action: Verify that EDT is searching in the expected direction and that you typed the string correctly.
STRIS_INT
string is interlocked Facility: LIB, Library Facility, OTS, General Purpose Facility, STR, String Manipulation Facility Explanation: Code being executed at AST level attempted writing into a string that is being written into or whose length is being used for length computation immediately before the AST. User Action: Do not write to strings at AST level that are used at non-AST level or in other AST-level processing. If it is necessary to use the same strings for interrupt routines, then disable ASTs while string assignments are in progress.
STRLVL
illegal object language structure level ('decimal-number') should be
'decimal-number' in module 'module-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An object module header record specified an illegal
object language structure level.
User Action: Submit a Software Performance Report on the
appropriate language processor.
STRLVL
illegal object language structure level in module 'module-name' Facility: LIB, Library Facility Explanation: The Run-Time Library encountered severe format errors in the shareable you are trying to call. User Action: Enter the ANALYZE/IMAGE command specifying the image in question. If the errors indicate an operating system internal error, submit a Software Performance Report (SPR).
STRLVL
object structure level 'nnn' unsupported in module 'module-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: This error message is generated by the DCL command LIBRARY. An illegally formatted object file is inserted. User Action: Recompile the object file and insert it into the library.
STRNOTFOUND
string not found Facility: VAXTPU, VAX Text Processing Utility Explanation: A search for a simple string or a pattern failed. User Action: None.
STRNOTWCB
data structure not window block Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
STRTERESC
illegal escape sequence embedded in string Facility: DTK, DECtalk Facility Explanation: A DTK$ output routine passed an escape sequence embedded in the output string. User Action: Check your output string to determine which escape sequence is being passed. If you need this escape sequence, most likely a DTK$ routine has already been defined that provides that feature.
STRTERESC
illegal escape sequence embedded in strings Facility: SMG, Screen Management Facility Explanation: An SMG output routine is passed an escape sequence embedded in the output string. The output string is written to the virtual display but the string is terminated at the escape sequence. User Action: Check your output string to determine what escape sequence is being passed. If you need the action provided by this escape sequence, there is most likely an SMG routine that performs that function.
STRTNOMULTI
cannot request /START_BLOCK with multiple input files Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility does not allow the use of the /START_BLOCK qualifier when more than one input file is specified. User Action: Leave the /START_BLOCK qualifier off, or copy the files one at a time with the /START_BLOCK present.
STRTOOLARGE
string greater than 65535 characters Facility: VAXTPU, VAX Text Processing Utility Explanation: A string operation has generated a string that exceeds 65,535 characters in length. User Action: Use an expression that generates a shorter string.
STRTOOLNG
specified string for parameter 'name' is too long Facility: SYSBOOT, System Bootstrap Facility and SYSGEN, System Generation Utility Explanation: A string specified in a SET command is longer than the maximum length for that parameter. User Action: Reenter the command specifying a shorter string.
STRTOOLNG
string argument is too long - shorten Facility: CLI, Command Language Interpreter (DCL) Explanation: The specified string argument is too long. User Action: Check the description of the command in the VMS DCL Dictionary for restrictions on the argument length. The VMS DCL Concepts Manual also describes the maximum allowable length of an argument for any command. Modify the string accordingly and retry the command.
STRTOOLON
string is too long (greater than 65535) Facility: STR, String Manipulation Facility Explanation: An attempt is made to create a string that is longer than allowed by the String Facility or the descriptors in the VMS Procedure Calling and Condition Handling Standard. The maximum length string supported is 65,535. User Action: Do not specify string lengths greater than 65,535. Check that a concatenation operation will not attempt to create a string longer than 65,535.
STRTRU
string truncated Facility: LIB, Library Facility Explanation: A Run-Time Library procedure returned a string that did not fit into the specified receiving area resulting in lost trailing characters. This message is associated with a status code returned from the Run-Time Library. User Action: Correct your program to increase the area specified to receive the string.
STRUCLEV
inconsistent structure level on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Files-11 structure level of the specified volume is different from other volumes in the same list of devices. The volume must not be part of the same volume set. User Action: Locate and mount the correct volume.
STRUCT_LEVEL
system job queue file has incompatible structure level of 'number' Facility: JBC, Job Controller Explanation: After opening the system job queue file, the job controller determined that the internal format of the queue file or revision level is different from the format currently supported by the system. This situation usually occurs when an old queue file is used after installing a new release of VMS or after a maintenance update in which the queue file format has changed. User Action: Create a new queue file using the START/QUEUE/MANAGER /NEW_REVISION command, or delete the existing queue file and create a new file using the START/QUEUE/MANAGER command.
SUBABORT
subordinate process encountered error Facility: UETP, User Environment Test Package Explanation: A vector processor device test subordinate process encountered an error during testing. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
SUBALREXI
subprocess already exists for this display Facility: SMG, Screen Management Facility Explanation: A user tried to create a subprocess for a virtual display when one is already created. This is normal in a modular environment. User Action: None.
SUBINTERR
error initializing subordinate process Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
SUBLOCKS
cannot dequeue a lock with sublocks Facility: SYSTEM, VMS System Services Explanation: A programming error occurred because an attempt is made to dequeue a lock that had sublocks under it. User Action: Correct the programming error and retry. (Note that you may use the flag bit LCK$M_DEQALL on the $DEQ system service request to dequeue all the locks for a given access mode.)
SUBMITERR
error submitting file to queue 'queue-name' Facility: SUBMIT, SUBMIT Command Explanation: This message is issued with another message indicating the problem. User Action: Take corrective action based on the accompanying message.
SUBRNG
arithmetic trap, subscript out of range at PC = 'xxxxxxxx', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: A subscript out of range caused an arithmetic exception condition. User Action: Examine the PC location displayed in the message, and check the program listing to verify that operands or variables are specified correctly.
SUBSCHERR
error scheduling subordinate process Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
SUBSPNERR
error spawning subordinate process Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
SUBSTSERR
error obtaining subordinate process status Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error which is the result of a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
SUBTRACED
protected subsystem image cannot be linked /TRACE or /DEBUG Facility: SYSTEM, VMS System Services Explanation: An attempt was made to activate an image with an associated protected subsystem ACE that was linked with either traceback information or a debug symbol table. For security reasons, protected subsystem images cannot contain either of these types of records. User Action: Link the image /NOTRACE and /NODEBUG.
SUCCDUPACE
current ACE will supersede succeeding ACE - not entered Facility: ACLEDIT, Access Control List Editor Explanation: An ACE exists after the current position within the ACL, which would be rendered useless by the current ACE. The current ACE is not entered. User Action: Modify or delete the current ACE or the succeeding occurrence of the ACE.
SUCCESS
normal successful completion Facility: CDU, Command Definition Utility Explanation: Your operation completed successfully. User Action: None.
SUP
network operation not supported; DAP code = 'xxxxxxxx' Facility: RMS, VMS Record Management Services Explanation: The requested VMS RMS operation failed because either the specified remote node does not support the function or VMS RMS does not support the function in a network context at the local node. User Action: Consult the VMS Networking Manual and the applicable DECnet manual for the remote node to determine which functions are supported by both the local and remote nodes. The status value (STV) field of the FAB or RAB contains a DAP status code. See the appropriate DECnet manual for the remote node for an interpretation of the DAP status code.
SUPERSEDE
created file superseded existing version Facility: RMS, VMS Record Management Services Explanation: The file created by a VMS RMS $CREATE operation superseded an existing version of the same file. This message indicates a success status. User Action: None.
SUPERSEDE
logical name superseded Facility: SYSTEM, VMS System Services Explanation: A request to place a logical name in a logical name table completed successfully by replacing an existing logical name table entry. (Because this is a success message, it is not normally displayed.) If this message is returned from a call to an ACP, it indicates that an existing file with the same file name, type, and version number is deleted as the result of a CREATE request. User Action: None. Note the condition and modify the source program, if necessary, to detect and respond to the condition.
SUPERSEDE
previous value of 'value' has been superseded Facility: CLI, Command Language Interpreter (DCL) Explanation: You redefined the specified logical name. User Action: None.
SUPPORT
network operation not supported Facility: RMS, VMS Record Management Services Explanation: VMS RMS rejected the request because it is not supported between two DECnet systems. The STV field contains either another VMS RMS completion code or a FAL status code, depending on whether VMS RMS at the local node or FAL at the remote node could not support the request. User Action: The status value (STV) field contains either an RMS status code or a $FAC status code that provides more information about the condition. Take corrective action based on this status code.
SUSPEND
service routine pausing for other input Facility: PSM, Print Symbiont Explanation: This status is returned by a print symbiont format routine requesting the current input service routine be paused. User Action: None.
SUSPEND
system operation suspended; security auditing resources exhausted Facility: AUDSRV, Audit Server Explanation: The free disk space on the disk volume associated with the specified audit journal file has fallen below the resource action threshold. Consequently, the audit server has suspended all noncritical processes. User Action: Log into a privileged account and free up disk space on the disk volume associated with the specified audit journal file.
SUSPENDED
process is suspended Facility: SYSTEM, VMS System Services Explanation: The specified process is suspended or placed in miscellaneous wait state. User Action: The requested operation cannot be performed when the specified process is suspended. Resume process or retry the operation.
SWAPAGINS
second page/swap file already installed Facility: SYSGEN, System Generation Utility Explanation: Two second page or swap files were installed. User Action: If it is necessary to change the page/swap file, reboot and install the correct file.
SWAPWSLE
swap working set list entries error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SYITSTERR
error encountered while testing $GETSYI system service Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error testing VMS system services. This error is received in relation to a previously displayed error condition or could be the result of a more serious VMS problem. User Action: If the condition causing the problem can be identified, correct the condition and rerun the test. If the error persists, submit a Software Performance Report (SPR). If the condition cannot be identified, run diagnostics for VAX Vectors or contact the Digital Services Group.
SYMABR
abbreviated symbols not allowed - remove "*" from symbol name Facility: CLI, Command Language Interpreter (DCL) Explanation: You abbreviated a symbol using an asterisk (*) or in a context where abbreviated symbol definitions are not valid. User Action: Remove the asterisk (*) from the symbol name.
SYMCREPRC
error creating symbiont process for 'device-name' Facility: JBC, Job Controller Explanation: The job controller encountered an error creating an input symbiont process for card reader input on the specified device. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
SYMDCLEXTR
symbol declared external Facility: MACRO, VAX MACRO Assembler Explanation: A label definition or direct assignment statement specified a symbol that is previously declared external in an .EXTERNAL directive. User Action: Delete the external declaration or change the name of the internal symbol.
SYMDEFINMO
symbol is defined in module Facility: MACRO, VAX MACRO Assembler Explanation: An .EXTERNAL directive specified a label that is previously defined in the module. User Action: Delete the external declaration or rename the internal symbol.
SYMDEL
invalid symbol or value delimiter - check command syntax Facility: CLI, Command Language Interpreter (DCL) Explanation: An illegal character is present on a command line containing a symbol definition. This error can also indicate that arguments were specified for a lexical function that does not require arguments. User Action: The rejected portion of the command is displayed between backslashes. Reenter the command.
SYMDEL
unexpected symbiont process termination Facility: JBC, Job Controller and QMAN, Queue Manager Explanation: A symbiont process exited without being requested to do so. The accompanying message provides additional information. User Action: Take action based on the accompanying message. A process dump might have been created. This message can result from an unplanned node or cluster shutdown.
SYMDELETE
error symbol deleted Facility: VAXTPU, VAX Text Processing Utility Explanation: The error symbol was deleted in order for the compiler to continue compiling. User Action: None.
SYMINSERT
'name' inserted before error symbol Facility: VAXTPU, VAX Text Processing Utility Explanation: In order for the compiler to continue compiling, 'name' was inserted before the error symbol. User Action: None.
SYMLNG
symbol name is too long - shorten the name Facility: CLI, Command Language Interpreter (DCL) Explanation: You specified a symbol name that is too long. User Action: Shorten the symbol name.
SYMNAMLNG
'module-type' module 'module-name' file 'library-name ' has illegal length 'nnn' Facility: LIBRAR, LIBRARY Command Explanation: The specified module name exceeds the name length limit. User Action: Make sure that all the symbol names in the module are less than the library's name length limit or compress the library with a larger key length.
SYMNOTABS
symbol is not absolute Facility: MACRO, VAX MACRO Assembler Explanation: The argument in a macro string operator is a relative symbol or is undefined. User Action: Ensure that the symbol is defined as an absolute symbol.
SYMNOTFOU
global symbol 'symbol' not found in shareable image 'image' Facility: SET PASSWORD Command Explanation: VMS was unable to locate the specified global routine in the named shareable image. User Action: Ensure that the routine declaration is properly declared as a GLOBAL symbol and that the LINK options file contains a UNIVERSAL option for the symbol.
SYMOUTPHAS
symbol out of phase Facility: MACRO, VAX MACRO Assembler Explanation: A label definition specified a label that is defined later in the module; or a local label definition specified a local label that is defined later in the same local label block. User Action: Ensure that the label is defined only once in the module, or that the local label is defined only once in the local label block.
SYMOVF
no room for symbol definitions - delete some symbols Facility: CLI, Command Language Interpreter (DCL) Explanation: The command interpreter cannot hold any more symbol definitions or labels. Note that this error can occur when a nested procedure is executed, because the command interpreter defines the symbols P1 through P8 before executing the procedure. If an ON condition is not established for warnings in the procedure, the procedure continues execution. However, the procedure may fail later if you refer to the symbol that could not be defined. User Action: If necessary, interrupt the command procedure with Ctrl/Y to stop its execution. Use the DCL commands SHOW SYMBOL and SHOW KEY to determine how many global symbols and keypad symbols are defined; delete unused symbols to recover symbol table space. If the error occurs frequently, simplify the command procedure or procedures, and use local symbols within procedures whenever possible. You may also increase the size of the command language interpreter (CLI) symbol table by resetting the SYSGEN parameter CLISYMTBL. The format of the command is SYSGEN SET CLISYMTBL n, where n is the size of the table expressed in pages. The SYSGEN SHOW CLISYMTBL command shows you the default table size, and the range of allowable table sizes. Note that the SYSGEN SET command sets the new value for the duration of your process only. It does not change the permanent parameter value.
SYMREPLACE
error symbol replaced by 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: The error symbol was replaced in order for the compiler to continue compiling. User Action: None.
SYMTOOLNG
string too long Facility: CDU, Command Definition Utility Explanation: You entered a command string that is too long and therefore invalid. User Action: Reenter a shorter command string.
SYMTOOLNG
symbol 'symbol-name' is too long to copy to subprocess Facility: CLI, Command Language Interpreter (DCL) Explanation: When you spawned a subprocess, a logical name, a logical value, a symbol name, or a symbol value is too long to be copied to the subprocess. User Action: Break the specified name or value into several parts.
SYMTOOLNG
symbol name too long Facility: MESSAGE, Message Utility Explanation: You have assigned a symbol name with more characters than are permitted. User Action: Shorten the symbol name.
SYMTOOLONG
the symbol 'symbol-name' is longer than 31 characters Facility: CDU, Command Definition Utility Explanation: CDU encountered a symbol name longer than 31 characters while reading from a CLD file. User Action: Edit the CLD file so that symbol names are not greater than 31 characters in length.
SYMTRUNC
preceding symbol value has been truncated Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the symbol value displayed through the SHOW SYMBOL command is too large to be fully displayed. The value is truncated in the display. User Action: None.
SYN
file specification syntax error Facility: RMS, VMS Record Management Services Explanation: The file specification syntax string contains a syntax error. For example, invalid characters were used, or required punctuation marks were omitted. User Action: Correct the syntax and reenter the command or correct the program that caused the error.
SYNCH
synchronous successful completion Facility: SYSTEM, VMS System Services Explanation: This alternate success code indicates that the requested operation completed synchronously and as expected. User Action: None.
SYNERR
syntax error Facility: SMG, Screen Management Facility Explanation: The Termtable compiler encountered invalid syntax. For instance, there may be a misplaced or missing equal sign. User Action: Check your terminal definition.
SYNTAX
command syntax error at or near 'location' Facility: PATCH, Patch Utility Explanation: A syntax error in a file name has been discovered in a CREATE command. User Action: Reenter the command specifying the correct syntax.
SYNTAX
error parsing 'string' Facility: Shared by several facilities Explanation: The command syntax is invalid. The message displays the rejected portion of the command. User Action: Use the DCL command HELP or refer to the VMS DCL Dictionary for the correct syntax and reenter the command.
SYNTAX
invalid ACE syntax Facility: ACLEDIT, Access Control List Editor Explanation: An error was encountered trying to parse the ACE currently being entered. The portion of the ACE after the point of error is displayed. User Action: Correct the error and enter the ACE again.
SYNTAX
syntax error Facility: SYSBOOT, System Bootstrap Facility Explanation: A syntax error is detected. User Action: Reenter the command with the correct syntax.
SYNTAX
syntax error: 'string' Facility: SYSGEN, System Generation Utility Explanation: A syntax error is detected. The 'string' part of the message displays the nonparsed input. User Action: Reenter the command with the correct syntax.
SYNTAX
syntax error in statement 'number' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: An FDL syntax error is encountered. User Action: Examine the specified line in the FDL file, determine which validity rule is violated, and correct the line.
SYNTAX
syntax error in statement 'number' 'reference-text' Facility: NCP, Network Control Program Explanation: An element in the command syntax could not be parsed. User Action: Reenter the command.
SYNTAXERR
string syntax error detected by LIB$TPARSE Facility: LIB, Library Facility Explanation: The string passed to the LIB$TPARSE library procedure contained a syntax error. User Action: Correct the syntax error in the string.
SYNTAXERROR
syntax error Facility: VAXTPU, VAX Text Processing Utility Explanation: The program being compiled has a syntax error. User Action: Correct the syntax error and recompile your program.
SYS
QIO system service request failed Facility: RMS, VMS Record Management Services Explanation: VMS RMS encountered an error while trying to issue a $QIO system service request for an I/O operation. This message may occur if calls to VMS RMS fail because of insufficient resource quotas; for example, if a process exceeds its AST limit quota. User Action: The status value (STV) field of the RAB contains a system status code that provides more information about the condition. Take corrective action based on this status code. Check for a programming error that causes the process to exceed a resource quota required for VMS RMS I/O operations.
SYSADJWSL
system service adjust working set limit error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.) SYSBOOT-E-Bad image header detected while checking system version Facility: SYSBOOT, System Bootstrap Facility Explanation: The versions of the system loadable image being read do not match the current VMS operating system versions. The images on your system disk are incompatible. User Action: Obtain a new copy of the VMS system disk. SYSBOOT-E-Device names not allowed Facility: SYSBOOT, System Bootstrap Facility Explanation: Device names are not valid when specifying a parameter with the USE command. The device defaults to the system root (usually the [SYS0.] directory on the system device). User Action: Reenter the command without a device name. SYSBOOT-E-End of file error reading Facility: SYSBOOT, System Bootstrap Facility Explanation: An end-of-file error occurred while SYSBOOT was reading a system loadable image; the error message includes the file name. The system disk may be corrupted. User Action: Attempt to reboot the system or try a different drive. If this fails, obtain a new copy of the VMS system disk. SYSBOOT-E-Error reading file Facility: SYSBOOT, System Bootstrap Facility Explanation: An irrecoverable error occurred while SYSBOOT was reading a parameter file in response to a USE command. The error message contains the file name. User Action: Reenter the command specifying the correct file name. SYSBOOT-E-I/O error reading file Facility: SYSBOOT, System Bootstrap Facility Explanation: An irrecoverable I/O error occurred while SYSBOOT was reading a parameter file or a system loadable image. If the error occurred while a parameter file was being read, SYSBOOT does not perform the requested action. If the error occurred while a system loadable image was being read, SYSBOOT terminates the bootstrap operation. User Action: Attempt to reboot the system or try a different drive. SYSBOOT-E-Not a parameter file Facility: SYSBOOT, System Bootstrap Facility Explanation: A file specified in a USE command is not a parameter file. The error message contains the file name. User Action: Reenter the command specifying a parameter file. SYSBOOT-E-System version mismatch found Facility: SYSBOOT, System Bootstrap Facility Explanation: The versions of the system loadable image being read do not match the current VMS operating system versions. The images on your system disk are incompatible. User Action: Obtain a new copy of the VMS system disk. SYSBOOT-E-Unable to locate file Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT cannot locate a file; error message will contain the file name. User Action: Reenter the command specifying the correct file name or mount the correct medium in the console drive. SYSBOOT-F-Boot time files have too many noncontiguous pieces Facility: SYSBOOT, System Bootstrap Facility Explanation: This error occurs during system initialization. The system dump, page, or swap file is overly fragmented, that is, approximately 100 pieces. User Action: Backup the system disk using the backup disk as the new system disk. The BACKUP Utility copies the files in a such way that the files consist of fewer fragments. SYSBOOT-F-FBIC version less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call the Digital Services Group. SYSBOOT-F-Invalid console ID Facility: SYSBOOT, System Bootstrap Facility Explanation: The console type code in the console identification register does not correspond to any supported console device for the VAX-11 processor being booted. User Action: Call the Digital Services Group. SYSBOOT-F-Microcode revision level too low to boot Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level for the VAX-11 processor being booted is below that required to boot the VMS system. User Action: Call the Digital Services Group. SYSBOOT-F-Not enough nonpaged pool to map Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT is unable to allocate sufficient nonpaged pool to map a driver or system loadable image. The error message will include the file name. User Action: Reboot the system with a larger value for NPAGEDYN. SYSBOOT-F-Pageable system space exceeds 512 MB Facility: SYSBOOT, System Bootstrap Facility Explanation: The size of pageable system space exceeds that which can safely be mapped with page file backing store. User Action: Reconfigure the system to require less pageable system space and reboot the system. Reduce one or more of the PAGEDYN and GBLPAGES parameters. SYSBOOT-F-PFN allocation overwrites CI ucode Facility: SYSBOOT, System Bootstrap Facility Explanation: The allocation of physical pages for the system page table, nonpaged dynamic pool, interrupt stack, and resident executive overwrites the CI microcode. User Action: Reconfigure the system to require less physical memory and reboot the system. Reduce one or more parameters controlling the allocation of physical memory: NPAGEDYN, BALSETCNT, and VIRTUALPAGECNT. SYSBOOT-F-PFN bit map conflict - Physical page count set too low Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT cannot find sufficient contiguous pages of physical memory (within the bounds specified by the parameter PHYSICALPAGES) to contain the PFN bitmap. User Action: Reboot the system with a larger value for PHYSICALPAGES. SYSBOOT-F-Switch of boot volume attempted with S0_PAGING=0, must be 1 Facility: SYSBOOT, System Bootstrap Facility Explanation: An attempt was made to switch the boot volume while system paging was turned on. System paging must be turned off. User Action: Set the system parameter S0_PAGING to 1 and reboot. SYSBOOT-F-System revision less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call the Digital Services Group. SYSBOOT-F-Unable to allocate physical memory Facility: SYSBOOT, System Bootstrap Facility Explanation: The sum of pages required for the system page table, nonpaged dynamic pool, interrupt stack, and resident executive exceeds available physical memory. User Action: Reconfigure the system to require less physical memory and reboot the system. Reduce one or more parameters controlling the allocation of physical memory: NPAGEDYN, BALSETCNT, and VIRTUALPAGECNT. SYSBOOT-F-Unable to allocate PTEs for Boot Driver Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT is unable to allocate the system page table entries (PTEs) needed by the boot driver. User Action: Increase the value of parameter SPTREQ. SYSBOOT-F-Unable to allocate SPT+PHD+SCB Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT cannot find enough contiguous pages of physical memory to contain the required system page table (SPT), process header (PHD), and system control block (SCB). User Action: Reduce parameters controlling SPT size: VIRTUALPAGECNT, BALSETCNT, REALTIME_SPTS, and SPTREQ. SYSBOOT-F-Unable to locate storage bit map file Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT cannot locate the storage bitmap file (BITMAP.SYS) in directory [000000] on the system disk. The system disk is either defective or corrupted. User Action: Obtain a new copy of the VMS system disk. SYSBOOT-F-Unable to locate SYS.EXE Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT cannot locate the system image file in directory [SYS$LDR] on the bootstrap volume. User Action: The system disk is either defective or corrupted, or the disk you are accessing is not the system disk. Obtain a new copy of the VMS system disk. SYSBOOT-F-Unable to read continuation volume Facility: SYSBOOT, System Bootstrap Facility Explanation: An error occurred while trying to read the continuation volume when booting the VMS operating system from multiple volumes. User Action: Attempt to reboot the system; try a different drive or obtain a new copy of the VMS system disk. SYSBOOT-F-Unexpected exception Facility: SYSBOOT, System Bootstrap Facility Explanation: An unexpected exception occurred indicating a probable hardware error or SYSBOOT logic error. User Action: Call your local field service representative. SYSBOOT-F-Unexpected machine check Facility: SYSBOOT, System Bootstrap Facility Explanation: An unexpected machine check occurred indicating a probable hardware error or SYSBOOT logic error. User Action: Call your local field service representative. SYSBOOT-F-Unknown processor Facility: SYSBOOT, System Bootstrap Facility Explanation: The processor type code in the system identification register does not correspond to any supported model of a VAX-11 processor. User Action: Call your local field service representative. SYSBOOT-I-GBLPAGES have been trimmed Facility: SYSBOOT, System Bootstrap Facility Explanation: The combined size of the system and global page tables exceeds the VMS architectural maximum (4,194,303 pages). SYSBOOT has reduced the size of the global page table by decreasing the SYSGEN parameter GBLPAGES. User Action: Review the ACTIVE value of the GBLPAGES parameter to make sure it is large enough to support normal system operation in your environment. Using SYSMAN, reevaluate the values of the parameters that determine the size of the system and global page tables, especially if the value computed by AUTOGEN has been overridden in MODPARAMS.DAT. (Refer to the VMS SYSMAN Utility Manual.) SYSBOOT-W-DMPFRG SYSDUMP.DMP is too fragmented to be used Facility: SYSBOOT, System Bootstrap Facility Explanation: The system dump file is severely fragmented. User Action: Back up the system disk and use the backup disk as the new system disk. SYSBOOT-W-ECO level less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call your local field service representative. You may continue the bootstrap operation but the integrity of the software may be compromised. SYSBOOT-W-FPLA, PCS, or WCS version less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call your local field service representative. You may continue the bootstrap operation but the integrity of the software may be compromised. SYSBOOT-W-Maximum WS raised to PHD+MINWSCNT Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT raised the specified maximum working set size to accommodate the minimum working set size allowed by VMS. To execute, every process requires a minimum fluid working set (MINWSCNT) plus space for its process header (PHD). User Action: None. SYSBOOT-W-Microcode patch level less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call your local field service representative. You may continue the bootstrap operation but the integrity of the software may be compromised. SYSBOOT-W-Microcode version less than minimum required for VMS. Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call your local field service representative. You may continue the bootstrap operation but the integrity of the software may be compromised. SYSBOOT-W-Primary home block is bad Facility: SYSBOOT, System Bootstrap Facility Explanation: The primary home block of the system disk could not be read and an alternate block was selected for use as the home block. User Action: Back up the system disk and then use the backup disk as the new system disk. The current system disk should be reinitialized. SYSBOOT-W-System ROM version less than minimum required for VMS Facility: SYSBOOT, System Bootstrap Facility Explanation: The hardware ECO level is below the level required for correct software operation. User Action: Call your local field service representative. You may continue the bootstrap operation but the integrity of the software may be compromised. SYSBOOT-W-WS default and quota raised to PDH+MINWSCNT Facility: SYSBOOT, System Bootstrap Facility Explanation: SYSBOOT raised the default working set size you specified to accommodate the sizes of the process header plus the minimum fluid working set size. User Action: None.
SYSDEV
the system device cannot be dismounted Facility: DISMOUNT, DISMOUNT Command Explanation: The device name specified in the DCL command DISMOUNT is the system volume. User Action: Verify the device name (or logical name, if a logical name is specified) in the command and reenter the DCL command DISMOUNT specifying the correct device.
SYSDIR
this product creates system directory 'directory-name' Facility: VMSINSTAL, Install Procedures Explanation: The product being installed creates the specified system directory. User Action: None.
SYSDISK
this product creates system disk directory 'directory-name' Facility: VMSINSTAL, Install Procedures Explanation: The product being installed creates a directory on the system disk. User Action: None.
SYSERROR
system service error Facility: Shared by several facilities Explanation: An error occurred while executing a system service. An accompanying message explains which service failed and why it failed. User Action: Follow the recovery procedure for the accompanying message.
SYSERRORPC
'name' system service error at PC 'location' Facility: Shared by several facilities Explanation: An error is detected by a system service. A subsequent message explains the reason for the error. User Action: Take corrective action based on the associated message.
SYSFAIL
system failed during execution Facility: JBC, Job Controller Explanation: The system crashed during execution of a batch or symbiont process. User Action: Resubmit the batch job or restart the output queues previously associated with the affected symbiont process.
SYSFAOERR
unexpected error from SYS$FAO Facility: DIFF, DIFFERENCES Command Explanation: An unexpected error occurred during a call to the $FAO system service. User Action: Submit a Software Performance Report (SPR).
SYSID
error while obtaining system ID message
Facility: CNF, NI Configurator
Explanation: An error occurred during the read to the NI device
driver.
User Action: See the accompanying message to determine the
appropriate action.
SYSINIT-E-create process error on STARTUP
Facility: SYSINIT, System Initialization
Explanation: An error occurred while creating the STARTUP process.
An accompanying message provides more information.
User Action: Take corrective action based on the accompanying
message and reboot the system.
SYSINIT-E-error allocating pool - error log buffers not copied
Facility: SYSINIT, System Initialization
Explanation: There was insufficient nonpaged pool available to
allocate the error log recovery buffer used to store the error log
messages for ERRFMT to copy out later to the error log file. Since
not enough pool is available to allocate the storage area, the
error log messages cannot be saved.
User Action: Increase the SYSGEN parameter NPAGEDYN so that enough
nonpaged pool is available to allocate the error log recovery
buffer.
SYSINIT-E-error creating shadowed system disk, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when creating the shadowed
system disk. The 'status' field provides the actual failure status
represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization, which can determine
the ident for you.
SYSINIT-E-error loading message file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system message file, SYS$MESSGAE:SYSMSG.EXE,
could not be loaded into the system. The 'status' field provides
the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error loading RECOVERY_UNIT_SERVICES.EXE, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The VMS RECOVERY_UNIT_SERVICES image, SYS$LOADABLE_
IMAGES:RECOVERY_UNIT_SERVICES.EXE, could not be loaded into the
system. The 'status' field provides the failure status represented
as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error loading RMS.EXE, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The VMS RMS image, SYS$LOADABLE_IMAGES:RMS.EXE, could
not be loaded into the system. The 'status' field provides the
failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error mounting system device
Facility: SYSINIT, System Initialization
Explanation: An error condition is preventing the system disk from
being mounted. In general, these error conditions are no different
from errors that prevent other volumes from being mounted, such as
a random I/O error, a corrupted file system, or an incorrect ACP
image.
User Action: Correct the problem that is preventing the system
disk from being mounted and reboot the system.
SYSINIT-E-error opening or mapping F11BXQP, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The VMS file system, SYS$SYSTEM:F11BXQP.EXE, could
not be opened or mapped. The 'status' field provides the failure
status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error opening page file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:PAGEFILE.SYS,
could not be opened. The 'status' field provides the failure
status.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error opening swap file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system swap file, SYS$SYSTEM:SWAPFILE.SYS, could
not be opened. The 'status' field provides the actual failure
status.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-error opening system dump file, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: The system dump file, SYS$MESSAGE:SYSDUMP.DMP, could
not be loaded into the system. The 'status' field provides the
failure status represented as a hexadecimal number.
User Action: If you do not have a running system available to
determine the ident, contact your software support organization to
determine the ident for you.
SYSINIT-E-error reading system dump file error log buffers, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error occurred while reading the error log
buffers in from the dump file. The hexadecimal error status value
described by 'status' is the failure status returned after the
read operation failed.
User Action: Check the system dump file for disk errors. It might
be necessary to create a new dump file.
SYSINIT-E-error taking out lock on system disk, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when acquiring a cluster-
wide lock on the system device. The 'status' field provides the
actual failure status.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-E-failed to create system logical names
Facility: SYSINIT, System Initialization
Explanation: An error occurred while attempting to create
a logical name needed by SYSINIT (SYS$SYSTEM, SYS$SHARE,
SYS$MESSAGE). The complete list of errors that can occur when
creating logical names is given in the VMS System Services
Reference Manual. The error that occurred while SYSINIT was
executing (assuming that the SYSINIT image is not corrupted) is
due to insufficient paged dynamic memory.
User Action: Set the SYSGEN parameter PAGEDYN to a reasonable
value (at least 10,000) and reboot the system.
SYSINIT-E-invalid date/time
Facility: SYSINIT, System Initialization
Explanation: A syntax error is detected in the date or time that
is typed to set the system time.
User Action: Enter the date or time in the correct format.
SYSINIT-E-page file or swap file control block initialization error
Facility: SYSINIT, System Initialization
Explanation: An error occurred, for one of the following reasons,
while attempting to install the primary paging or swap file:
o There is not enough nonpaged pool for the PFL bitmap.
o The SYSGEN parameter, PAGFILCNT, is set to zero.
o The file is badly fragmented and an error occurred while trying
to map the file completely.
User Action: Correct the error using one of the following methods
and reboot the system:
o If there is not enough nonpaged pool, see the message INSFMEM
for information about making enough nonpaged pool available for
booting the system.
o Do not set PAGFILCNT to zero.
o You can prevent the complete mapping of a file if there is not
enough nonpaged dynamic memory or if the SYSGEN parameter PQL_
DBYTLM is set too small.
SYSINIT-E-recoverable error encountered when mounting system device, status= 'status'
Facility: SYSINIT, System Initialization
Explanation: A recoverable disk I/O error was encountered when
mounting the system disk. The mount operation will be retried
automatically.
User Action: None.
SYSINIT-E-unable to obtain lock for system ID resource, status = 'status'
Facility: SYSINIT, System Initialization
Explanation: An error was encountered when acquiring a system-
owned lock whose name contains the system ID. The 'status' field
provides the failure status represented as a hexadecimal number.
User Action: Try to determine the cause of the failure. If you
do not have a running system available to determine the ident,
contact your software support organization to determine the ident
for you.
SYSINIT-I-no dump file - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The system disk does not have either a dump file
SYSDUMP.DMP or a page file PAGEFILE.SYS; therefore, the contents
of the error log buffers at the time of the last shutdown/crash
that were saved in the dump file are not available for recovery
from the dump file into the error log buffer recovery area.
User Action: Create a page file PAGEFILE.SYS or a dump file
SYSDUMP.DMP on the system disk, and reboot the system so that
a dump file is available and error log buffers are saved across a
shutdown or system failure.
SYSINIT-I-PAGEFILE.SYS not found - system initialization continuing . . .
Facility: SYSINIT, System Initialization
Explanation: The primary paging file, SYS$SYSTEM:PAGEFILE.SYS
could not be found.
User Action: Use the command procedure SYS$UPDATE:SWAPFILES.COM
to place a page file in the system directory SYS$SYSTEM.
Alternatively, you can install one or more secondary page files by
editing the SYS$SPECIFIC:[SYSMGR]SYPAGSWPFILES.COM file.
SYSINIT-W-dump file write errors - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: Since the entire dump file contents are suspect, the
dump file write is not successfully completed, and no attempt is
made to recover the saved error log messages from the dump file.
User Action: None.
SYSINIT-W-invalid dump header version - error log buffers not saved
Facility: SYSINIT, System Initialization
Explanation: The dump file contains the contents of a dump written
under a version of the VMS operating system different from the
version that is being booted now. Therefore, the error log
messages saved in the dump file are not read out from the dump
file, since the format of the dump file and error log messages may
be different from that format being used on this version.
User Action: None required. This message is primarily to warn
users that some error log messages have been lost.
SYSJNLFULL
device full error on journal SECURITY; automatic server restart suppressed Facility: AUDSRV, Audit Server Explanation: The device associated with the system security audit journal file is full. When this event occurs, the audit server will not restart itself. Buffered security alarms received prior to the error will be stored in the process dump file, SYS$SYSROOT:[SYSEXE]AUDIT_SERVER.DMP. User Action: Free up space on the system volume and restart the audit server process using the command SET AUDIT/SERVER=START.
SYSJNLNAC
system audit journal inaccessible; SYS$COMMON:[SYSMGR]SECURITY_ AUDIT.AUDIT$JOURNAL used instead Facility: AUDSRV, Audit Server Explanation: The audit server process cannot open the system security audit log file. This condition occurs, for example, when the device on which the log file resides is unavailable or full. Audit messages are redirected to the default system security audit log file SECURITY_AUDIT.AUDIT$JOURNAL in the SYS$MANAGER directory. User Action: Correct the device problem and redirect the system security audit log file to the alternate device.
SYSLOAD
system loaded from node 'node-name' Facility: VAXCLUSTER, VAXcluster Facility Explanation: This informational message indicates that the NISCS bootstrap is starting execution. User Action: None.
SYSMGT
system specific mangement function not supported Facility: NCP, Network Control Program Explanation: The requested function cannot be performed because it is a system-specific function that is not supported on the system where the command is executed. User Action: Examine the provided system-specific error message, if present.
SYSMSG2
error code 'hex code' not found Facility: AUTHORIZE, Authorize Utility Explanation: The $GETMSG system service could not find a corresponding message for the specified error code, which probably indicates that the code is incorrect. Since an incorrect error code obviously should not be generated, this message probably indicates an internal software error. User Action: Submit a Software Performance Report that describes the conditions leading to the error.
SYSNAM
NICONFIG requires SYSNAM privilege Facility: CNF, NI Configurator Explanation: NICONFIG must run with SYSNAM privilege in order to declare itself as a known image to be eligible for multiple connects. User Action: Install NICONFIG with SYSNAM privilege or run from an account with SYSNAM privilege.
SYSNOTUPD
I/O database not updated for volume 'volume' Facility: SET, SET Facility Explanation: The attempt to modify the volume's home block is successful, but the system information about the volume is not updated. User Action: To ensure that no ambiguities exist in the system I/O database, the volume should be dismounted and then remounted. Until then, a SHOW DEVICE of the drive on which the volume is mounted will still show the old volume characteristics.
SYSPWDMOD
system password modified Facility: AUTHORIZE, Authorize Utility Explanation: The system password has been changed to the password directed by your command. User Action: None.
SYSSRVERR
error encountered during vector system services testing Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error testing VMS system services. This error is received in relation to a previously displayed error condition or could be the result of a more serious VMS problem. User Action: If the condition causing the problem can be identified, correct the condition and rerun the test. If the error persists, submit a Software Performance Report. If the condition cannot be identified, run diagnostics for VAX Vectors or contact the Digital Services Group.
SYSTRMERR
SYSINIT-terminal IO error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
SYSVERCHK
system version mismatch - function aborted Facility: SYSGEN, System Generation Utility Explanation: An attempt to do a WRITE CURRENT operation failed because the version of SYSGEN.EXE does not match SYS.EXE. User Action: Reenter the command with the proper version of SYSGEN.EXE.
SYSVERDIF
privilege removed - system version mismatch - please relink Facility: SYSTEM, VMS System Services and RMS, VMS Record Management Services Explanation: A SYS.STB that links the image being run is different from that of the currently running system. User Action: Relink the image. The image is allowed to run without CMEXEC or CMKRNL privilege.
SYSVERDIF
system version mismatch - please relink Facility: INSTALL, Install Utility Explanation: The image being installed is not linked against the current version of the system. User Action: Relink the image and retry the installation.
SYSVERDIF
system version mismatch - reassemble and relink driver Facility: SYSGEN, System Generation Utility Explanation: You have encountered a driver mismatch. User Action: Reassemble and relink all drivers at each major release of VMS.
SZTOOBIG
record size or block size greater than 65534 Facility: MOUNT, Mount Utility Explanation: The record size or block size specified by /RECORDSIZE or /BLOCKSIZE is greater than 65,534. User Action: Check the source program and make the necessary correction.
TABEXIST
'table-name' already exists - not superseded Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the CREATE /NAME_TABLE command without the SUPERSEDE attribute specified encountered a table with the same name as the one it is about to create. A new table is not created. User Action: If the existing table is to be replaced by a new table, reenter the command with the /ATTRIBUTES=SUPERSEDE qualifier.
TABID_MIS
terminal table id mismatch Facility: SMG, Screen Management Facility Explanation: The Termtable internal consistency check failed. The routines that fetch information from Termtable have a different version number than the Termtable data. User Action: The routines that fetch the data may be newer than your Termtable.EXE. Recompile TERMTABLE.TXT to update your TERMTABLE.EXE.
TABLEFULL
element ID table overflow Facility: MONITOR, Monitor Utility Explanation: A MONITOR request for a component class is terminated prematurely because of an overflow of an internal buffer. User Action: Reexecute the MONITOR request. Please submit an SPR including a transcription of the exact MONITOR command entered and a dump of the MONITOR image.
TABNOTFND
previous table 'table-name' is not found - new table created Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the CREATE/NAME_TABLE/ATTRIBUTES=SUPERSEDE command could not find an existing table of the same name. The new table is created. User Action: None.
TABSUPER
previous table 'table-name' has been superseded Facility: CLI, Command Language Interpreter (DCL) Explanation: This informational message signifies that the CREATE /NAME_TABLE/ATTRIBUTES=SUPERSEDE command found an existing table with the same name and replaced it with a new table. User Action: None.
TAMPER
file 'filename' has been tampered with. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL is attempting to update a system text file, but the file has been modified locally. VMSINSTAL cannot update the file. User Action: Digital software cannot update system text files that you have modified.
TAPECLASS
fatal error detected by Tape Class driver (TUDRIVER) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
TAPEFULL
'save-set-spec' is full Facility: BACKUP, Backup Utility Explanation: The specified volume contains file data that extends past the end-of-tape reflective strip, indicating that no space is available for more data. User Action: Retry the operation using another volume.
TAPEPOSLOST
magnetic tape position lost Facility: SYSTEM, VMS System Services Explanation: The magnetic tape ACP (ancillary control process) lost the current position on the tape and cannot continue processing. User Action: Close all open files. Dismount and remount the tape and position it to the desired position, if possible. If the error persists, the tape may be defective.
TAPES
tapes Facility: OPCOM, Operator Communication Process Explanation: This message is issued when operator status is requested either explicitly by the REPLY/STATUS command or implicitly as with the REPLY/ENABLE command. It indicates that the operator's terminal is enabled for "TAPES" class operations. User Action: None.
TAR
no text allowed after .REQUIRE command: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You attempted to insert commands or text directly following a .REQUIRE command file specification. User Action: Put the commands on a separate line.
TBIT
T-bit pending trap at PC = 'location', PSL = 'xxxxxxxx' Facility: SYSTEM, VMS System Services Explanation: This message indicates an exception condition. It is usually followed by a display of the condition arguments, registers, and stack at the time of the exception. User Action: Examine the PC and virtual address displayed in the message to determine the instruction that caused the error.
TBKBUG
please report TRACE bug no. 'nnn' Facility: TRACE, Traceback Facility Explanation: An internal coding error occurred in the traceback program. User Action: Collect as much information as possible and submit a Software Performance Report (SPR). Include the bug number displayed in the message in the Report (SPR).
TERMDSBL
terminal disabled, operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: A terminal is successfully disabled with the DCL command REPLY/DISABLE. User Action: None.
TERMENAB
terminal enabled, operator 'operator-name' Facility: OPCOM, Operator Communication Process Explanation: A terminal is successfully enabled with the DCL command REPLY/ENABLE. User Action: None.
TERMFAIL
failed to enable terminal Facility: OPCOM, Operator Communication Process Explanation: This message is a response to a REPLY/ENABLE request indicating that your request to OPCOM is rejected. User Action: Ask you, system manager to give you OPER privilege and try again.
TEROUT
error code of 'xx' parsing command file Facility: PATCH, Patch Utility Explanation: A command interpreter callback request failed due to the error code being represented as 'xx'. User Action: Correct the error code (represented as 'xx') and retry.
TEXT
'message' Facility: VAXTPU, VAX Text Processing Utility Explanation: The message text is displayed and should describe the problem. User Action: Take action based on the content of the message text.
TEXT
'text' Facility: UETP, User Environment Test Package Explanation: Some UETP tests use this message to convey information that is usually self-explanatory. The device tests, for example, use this message to explain why a device failed its test. User Action: In most cases no user action is indicated by this message itself. Take the action implied by the other messages that usually accompany it. In other cases, the text should explain the nature of the problem.
TEXT
no input file given Facility: MACRO, VAX MACRO Assembler Explanation: The DCL command MACRO did not contain any source files; it contained only macro library files. User Action: Specify a source file in the command line.
TEXTD
'string' Facility: DSR, DIGITAL Standard Runoff Explanation: This message accompanies one or more other messages that describe an error condition. This message displays the text that is being processed when the error occurred. User Action: Correct the text by editing the source file.
TEXTD
entry text: 'string' Facility: DSR, DIGITAL Standard Runoff Explanation: The indicated index entry caused this error. This message accompanies one or more other messages. User Action: Correct the entry in error by editing the source file.
TFE
too few end commands Facility: RUNOFF, DIGITAL Standard Runoff Explanation: An .END command (for example, .END LIST) is missing. User Action: Insert the missing .END command.
TFRSYS
transfer address in system image 'image-name' ignored Facility: LINK, Linker Utility Explanation: The linker encountered a transfer address in the creation of a system image. System images cannot have transfer addresses. User Action: Remove the transfer address. That key is not definable Facility: EDT, EDT Editor Explanation: The key selected for the EDT command DEFINE KEY is not available for definition. User Action: Select a different key to define.
THIRDPARTY
logical link disconnected by a third party Facility: SYSTEM, VMS System Services Explanation: A DECnet-VAX logical link is disconnected by a system manager at some location in the network. User Action: Reinitiate the connection.
TIMED_OUT
timed condition wait expired Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: On a cma_cond_timed_wait routine, the timer expired before the condition was signaled or broadcast. User Action: Take appropriate action based on program dependencies for the specific condition variable wait that timed out.
TIMEOUT
a timeout has occurred Facility: Shared by several facilities Explanation: This informational message indicates that the output device has timed out. User Action: None.
TIMEOUT
built-in timed out Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure timed out. User Action: A software error has occurred. Please submit a Software Performance Report (SPR).
TIMEOUT
device timeout Facility: SYSTEM, VMS System Services Explanation: An input operation did not complete because the timeout period specified with the request elapsed before the input was received. If this message is associated with a status code returned by a request to an LPA11-K driver, a device timeout occurred. (Only for the start microprocessor, initialize LPA11-K, set clock, and start data transfer request functions.) An interrupt is not received within one second after the request is issued. If this message is associated with a status code returned by a request to a DR11-W interface driver, the timeout period specified for this request is exceeded. A device reset is issued to the DR11-W when the timeout occurs. If this message is associated with a status code returned by a request to a terminal driver, the specified terminal could not perform the QIO read operation because a timeout occurred at the terminal. In other words, an interrupt is lost, or IO$M_TIMED is specified on a read operation, or a hardware timeout occurred. IOSB+2 contains the number of bytes transferred before the timeout occurred. If associated with a DECnet-VAX operation, the connect request is not completed within the maximum time. User Action: The action to take depends on the context of the command or application. For example, if a timeout occurs during the execution of a DCL command MOUNT, verify that the physical device is ready and that the volume is properly loaded on the device.
TIMEOUT
disk boot driver initialization timeout Facility: VAXCLUSTER, VAXcluster Facility Explanation: The boot node could not respond to the MSCP messages within the timeout interval. User Action: Check for resource deprivation on the boot node or an overloaded Ethernet.
TIMEOUT
no response within timeout period Facility: LAT, LAT Facility Explanation: A LAT connection was lost because the remote node did not respond within the timeout period. User Action: Check the network availability of the remote node. If this error persists, you may need to increase the retransmit limit on the local node.
TIMEOUT
transaction exceeded execution time limit from $START_TRANS service Facility: DDTM, DECdtm Transaction Manager Explanation: The transaction aborted because the time specified in the timout argument when calling $START_TRANS has been exceeded. User Action: None.
TIPCUFLOW
NETACP - transmit count underflow Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
TIRLNG
object command data overflows record by 'decimal-number' bytes in module 'module-name' record 'record-name' file 'filename' Facility: LINK, Linker Utility Explanation: The object record is not long enough to contain all required data. User Action: Submit a Software Performance Report on the appropriate language processor.
TIRNYI
unimplemented TIR command ('decimal-number') encountered in module
'module-name' record 'record-name' file 'filename'
Facility: LINK, Linker Utility
Explanation: An object module contained an object language command
that is not implemented.
User Action: Submit a Software Performance Report on the
appropriate language processor.
TITLE
empty ident or title Facility: FDL, Edit/FDL Utility Explanation: There is no string value specified for the TITLE primary. User Action: You can either ignore this message or modify the FDL file and supply a value for the TITLE primary.
TITLETRUNC
maximum length of 'n' exceeded, title truncated Facility: ACCOUNTING, Accounting Utility Explanation: The length of the title string specified by the /TITLE qualifier is too long. The title string will be truncated to the maximum length specified in the error message. User Action: Reduce the length of the title string.
TKNOVF
command element is too long - shorten Facility: CLI, Command Language Interpreter (DCL) Explanation: An element, that is, any string placed between two delimiters, in the command line exceeded the maximum length of 255 bytes. User Action: Reenter the command with the element shortened.
TLKINUSE
DECTalk is in use Facility: DTK, DECtalk Facility Explanation: A DTK$ routine is called from an AST routine that interrupted a DTK$ routine with the same voice_id argument. User Action: Correct the code to call the routine with the correct synchronization.
TMF
too many footnotes, excess footnotes merged Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You have more than twenty footnotes in a file. All footnotes after the twentieth are merged into one large footnote and output after the next page of text. (This large footnote will probably exceed the page length.) User Action: Use fewer footnotes, shorten them, or spread them out.
TMO
timeout period expired Facility: RMS, VMS Record Management Services Explanation: A VMS RMS operation specified a timeout period and the timeout period expired before the operation completed. The user buffer contains the input characters (if any) received before the timeout period expired. User Action: If this message occurs during the login procedure, repeat the procedure. If the request is for a record lock, the lock request is not granted. Other actions depend on the program issuing the request; user programs should be coded to detect and respond to I/O timeouts.
TMP
too many page ranges on /PAGES qualifier Facility: RUNOFF, DIGITAL Standard Runoff Explanation: More than five separate page ranges have been specified with the qualifier. User Action: Reduce the number of ranges specified.
TMPMBX
NICONFIG requires TMPMBX Facility: CNF, NI Configurator Explanation: NICONFIG must run with TMPMBX privilege. User Action: Install NICONFIG with TMPMBX privilege or run from an account with TMPMBX privilege.
TMR
SETIMR system service request failed Facility: RMS, VMS Record Management Services Explanation: A VMS RMS operation specified a timeout period and the attempt to declare the system timer failed. The operation is aborted. User Action: Verify that sufficient TQE quota is available by entering the SHOW PROCESS/QUOTA command. If necessary, increase the TQE quota, and try the operation again; or modify the program so there are not too many $SETIMR requests simultaneously.
TMS
too many saves, corresponding .SAVE and .RESTORE ignored Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You have nested more than 20 .SAVE directives. User Action: Correct your program to nest fewer than 20 .SAVE directives.
TMSCPLDERR
TMSCP server must be loaded using SYSGEN parameter TMSCP_LOAD Facility: SYSGEN, System Generation Utility Explanation: You attempted to load the TMSCP server using the TMSCP command within SYSGEN. User Action: The proper way to load the TMSCP server is to set the SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which services all locally connected MSCP-type tape drives during SYSBOOT.
TMT
too many tab settings; excess ignored: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: More than 40 separate settings were used with a single .TAB STOPS command. User Action: Reduce the number of tab settings.
TMV
too many /VARIANTs Facility: RUNOFF, DIGITAL Standard Runoff Explanation: More than 20 variable names were used with the qualifier. User Action: Reduce the number of variable names.
TNS
terminator not seen Facility: RMS, VMS Record Management Services Explanation: A VMS RMS $GET service request to a terminal terminated when the user buffer is filled to capacity. No record terminator is encountered. Subsequent $GET service requests can retrieve additional characters from the input line. User Action: Modify the source program, if necessary, to detect and respond to the condition or provide a user buffer large enough to contain an entire input line, including the terminator sequence.
TODISCON
type ^'character' to disconnect the session Facility: LAT, LAT Facility Explanation: Use the specified control character to disconnect the SET HOST/LAT session. User Action: Enter the specified control character.
TOODEEP
maximum subindex depth exceeded Facility: DSR, DIGITAL Standard Runoff Explanation: The number of levels of subindex entries has been exceeded. User Action: Check the subindex entries.
TOOFEW
too few arguments Facility: VAXTPU, VAX Text Processing Utility Explanation: You have not specified all of the arguments required by the built-in procedure you want to execute. User Action: Reenter the procedure with all of the required arguments. If you do not know the correct arguments, check the description of the built-in procedure in the VAX Text Processing Utility Manual, or use online help.
TOOLONG
specified parameter is too long (over 255 characters) Facility: DTK, DECtalk Facility Explanation: The length of the specified string is too long. User Action: Correct your program so that it requests a phone number or dictionary substitution of 255 characters or fewer.
TOOMANCLS
number of classes in text library module greater than allowable classes Facility: ERF, Error Log Utility Explanation: An inconsistency in the text library was encountered. User Action: Submit a Software Performance Report (SPR).
TOOMANDIS
too many displays Facility: SMG, Screen Management Facility Explanation: An internal limit on the number of virtual displays that your program may have has been exceeded. The limit is currently 255. This includes any virtual displays that some outer routine may be using. This includes displays on all pasteboards. User Action: Use fewer virtual displays. Make sure that your program is not in a loop creating virtual displays. Be sure that you delete a virtual display when you are done with it.
TOOMANNOD
too many nodes in node list - must be shortened Facility: SMI, System Management Integrator/Server Explanation: The result of an ENABLE or DISABLE operation would force the list of nodes for an entry to surpass the maximum length. User Action: Check if the node list can be shortened by changing the operation from ENABLE to DISABLE, or from DISABLE to ENABLE.
TOOMANPAS
too many pasteboards Facility: SMG, Screen Management Facility Explanation: An internal limit on the number of pasteboards that your program may have has been exceeded. The current limit is 31. User Action: Use fewer pasteboards.
TOOMANY
too many arguments Facility: VAXTPU, VAX Text Processing Utility Explanation: You have specified too many arguments to the built-in procedure you want to execute. User Action: Locate and remove the extra argument or arguments. Then reenter the procedure. If you do not know the correct arguments, check the description of the built-in procedure in the VAX Text Processing Utility Manual, or use online help.
TOOMANYARGS
more arguments than defined in routine table Facility: SMI, System Management Integrator/Server Explanation: This is an internal error. SMI is trying to send a call to a remote node, and the argument list is longer than the maximum length defined for the object. User Action: Submit a Software Performance Report showing the sequence of SYSMAN commands leading to the error.
TOOMANYCOL
too many columns, reduced number to fit listing width Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered a DIRECTORY /COLUMNS value too large for the display line. EXCHANGE has used the largest number of columns which will fit on the line. User Action: None.
TOOMANYLEV
too many levels of nested input detected in record 'record number' Facility: PSM, Print Symbiont Explanation: This status is returned indicating too many levels of nested input detected in this record number. User Action: Please submit a Software Performance Report (SPR).
TOOMANYLNAM
logical name translation exceeded allowed depth Facility: SYSTEM, VMS System Services Explanation: Ten translations were performed on the logical name; however, the name has not been translated. User Action: Display all logical name tables and remove those entries that caused the problem.
TOOMANYPARAM
too many formal parameters/local variables at line 'integer' Facility: VAXTPU, VAX Text Processing Utility Explanation: A maximum of 31 formal parameters or local variables is permitted. User Action: Reduce the number of formal parameters or local variables to less than 31.
TOOMANYREDS
too many redirects Facility: SYSTEM, VMS System Services Explanation: This call is redirected more than eight times. User Action: Modify your program so that it performs fewer levels of call redirection.
TOOMANYSUB
SPAWN failed due to too many subprocesses; DIRECT mode used Facility: STDRV, System Startup Driver Explanation: The startup database directed the startup driver to run too many spawned subprocesses. STDRV ran one or more of the processes in the main startup procedure using DIRECT mode. System startup should complete normally. User Action: You can use the SYSMAN utility's STARTUP commands to display and modify the startup database to spawn fewer subprocesses.
TOOMANYVER
too many higher file versions Facility: SYSTEM, VMS System Services Explanation: The maximum number of file versions already exists for the specified file, and all existing version numbers were greater than the specified version number. User Action: Change the version limit of the file or delete some of the existing versions.
TOO_MNY
too many of this device type Facility: SYSGEN, System Generation Utility Explanation: The SYSGEN command CONFIGURE is entered with too many controllers specified for a given type. User Action: Reenter the SYSGEN command CONFIGURE with the correct number of controllers.
TOOMNYARG
too many arguments Facility: LBR, Librarian Subroutine Package Explanation: A call to a librarian function passed more arguments than were expected. User Action: Reduce the number of arguments so that the call is in the correct format.
TOOMNYARGS
too many arguments in MACRO call Facility: MACRO, VAX MACRO Assembler Explanation: The macro call contained more arguments than were specified in the .MACRO directive in the macro definition. User Action: Ensure that the macro call corresponds to the macro definition.
TOOMNYDLM
more than maximum of 'n' comment delimiters specified Facility: DIFF, DIFFERENCES Command Explanation: Too many comment delimiters were specified. User Action: Reenter the command, specifying one less than 'n' comment delimiters.
TOOMNYENDR
too many .ENDR in macro 'macro-name' in 'library-name' Facility: LIBRAR, LIBRARY Command Explanation: The specified MACRO contains an unmatched .ENDR. User Action: Reformat the macro source file.
TOOMNYFIL
more than two input files specified Facility: DIFF, DIFFERENCES Command Explanation: Too many input files were specified. User Action: Reenter the command; specify no more than two input files.
TOOMNYFILES
too many input files specified Facility: MONITOR, Monitor Utility Explanation: More than 5000 input files were specified on the /INPUT qualifier. User Action: Reenter the MONITOR request specifying a file specification list which identifies no more than 5000 files. For performance reasons, it is a good idea to archive or purge MONITOR recording files which are unlikely to be used in a multi-file summary request.
TOOMNYGST
number of symbol records exceeds count in image header Facility: CDU, Command Definition Utility Explanation: The input tables have an invalid format or were corrupted. User Action: Do not use these files again with SET COMMAND.
TOOMNYLIB
too many libraries open Facility: LBR, Librarian Subroutine Package Explanation: Too many libraries are open. Only 16 libraries may be open simultaneously. User Action: Use LBR$CLOSE to close any library that you do not need to access.
TOOMNYOPND
too many operands for instruction Facility: MACRO, VAX MACRO Assembler Explanation: Too many operands were specified for the instruction. User Action: Reduce the number of operands.
TOOMNYOUT
too many outputs defined Facility: CDU, Command Definition Utility Explanation: There are too many outputs included in the CLD file. User Action: Reduce the number of outputs specified in the CLD file.
TOOMNYPSEC
too many PSECTs declared Facility: MACRO, VAX MACRO Assembler Explanation: More than 255 user-defined program sections were declared. User Action: Reduce the number of program sections.
TOOMUCHDATA
too much optional or interrupt message data Facility: SYSTEM, VMS System Services Explanation: A network interrupt message is rejected because it contains more than 16 bytes of data. On a write request, the DEUNA hardware incorrectly read the value for the buffer size because the DEUNA device driver previously verified that the buffer size is correct. User Action: Repeat the request; do not specify more than 16 bytes of data. The UNIBUS and UNIBUS Adapter especially the Data Path board, should be checked.
TOOMUCHINFO
size of data in request exceeds system constraints Facility: JBC, Job Controller Explanation: The amount of data specified for a record within the queue manager's database is too large. User Action: Submit a Software Performance Report (SPR) to notify VMS Engineering that current constraints do not meet your needs.
TOPLINETRUNC
calculated new first line 'integer', changed to 1 Facility: VAXTPU, VAX Text Processing Utility Explanation: You adjusted a window. The new first line, however, would have been less than 1. Therefore, VAXTPU has truncated it at 1. User Action: None is required. However, you may reexecute the built-in procedure ADJUST_WINDOW with arguments that will not result in a first line less than 1.
TOQUIT
connection established. Press Ctrl/'escape character' to quit, Facility: REM, Set Host Facility Explanation: This informational message reports that a connection to the remote system has been established. User Action: None required. To quit the session, type Ctrl/'escape character'. To access DTE command mode, type Ctrl/'command character'.
TOTAL
'n-records' selected, 'n-records' rejected, 'n' input files Facility: ACCOUNTING, Accounting Utility Explanation: When the /LOG qualifier is used, this informational message displays the total number of records that were selected and/or rejected, as well as the total number of input files processed. User Action: None.
TOTAL
'n' selected, 'n' rejected, 'n' skipped, 'n' input files Facility: ERF, Error Log Utility Explanation: This message reports the total number of input files processed and the total number of entries selected, rejected, and skipped across all the files. User Action: None.
TPSFAOERR
could not format display line Facility: SDA, System Dump Analyzer Explanation: The structure displayed contains data that could not be formatted properly. User Action: If further analysis is required, use the SDA FORMAT command to examine the structure.
TPSINVBLK
invalid block type in specified block Facility: SDA, System Dump Analyzer Explanation: An attempt was made to copy an unrecognized structure. User Action: For an active system, retry the command. For a system crash dump, submit a Software Performance Report (SPR) that describes the conditions leading to the error; include a BACKUP save set containing the output of the SDA command.
TPSTERM
TP Services structure display terminated prematurely Facility: SDA, System Dump Analyzer Explanation: The selected SDA command was unable to complete. The Transaction Processing (TP) structures displayed by this command are corrupt. User Action: None.
TPSUTCERR
no valid timestamp Facility: SDA, System Dump Analyzer Explanation: The displayed structure can contain an optional timestamp. The structure displayed currently does not have a timestamp. User Action: None. This is an informational message.
TRACEBACK
symbolic stack dump follows Facility: TRACE, Traceback Facility Explanation: This message precedes a symbolic traceback dump. User Action: None.
TRACIGN
suppression of traceback overridden by DEBUG specification Facility: LINK, Linker Utility Explanation: The command line specified both /NOTRACE and /DEBUG. /NOTRACE is ignored. The link continues as if /NOTRACE were not specified. User Action: None.
TRE
error in index tree Facility: RMS, VMS Record Management Services Explanation: VMS RMS detected an invalid index pointer in an indexed file. User Action: Reorganize the file with the CONVERT command. This error is caused by hardware errors, VMS RMS or system software errors, or inadvertent modifications of files by non-VMS RMS programs.
TRMMBX
terminal has associated - terminate image and then SPAWN Facility: CLI, Command Language Interpreter (DCL) Explanation: A SPAWN command failed because the current image has associated a mailbox with the terminal. User Action: Terminate the current image and reenter the SPAWN command.
TRMNOTANS
terminal is not ANSI compatible Facility: SMG, Screen Management Facility Explanation: A call to SMG$GET_PHYSICAL_CURSOR is made specifying that the terminal is to be queried to determine where the cursor is. This could not be done because the terminal is not ANSI standard, and this feature is available only on ANSI terminals. User Action: Rerun your application on an ANSI terminal such as a VT100.
TRU
truncation Facility: STR, String Manipulation Facility Explanation: An attempt is made to place more characters into a string than it could contain. The value is truncated on the right to fit. User Action: Do not exceed the maximum string length. This error may be ignored if right truncation is acceptable.
TRUNC
data truncated Facility: DCX, Data Compression/Expansion Utility Explanation: The buffer provided is insufficient to receive the compressed data record produced by DCX$COMPRESS_DATA or the expanded data record produced by DCX$EXPAND_DATA. As much data as the buffer could hold has been returned. User Action: Provide a larger buffer.
TRUNC
truncation error in psect 'psect-name' offset 'address' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A reference using byte or word relative addressing mode is too far away. User Action: Correct the reference to use longword relative addressing mode.
TRUNCATE
line truncated to 'count' characters Facility: VAXTPU, VAX Text Processing Utility Explanation: The text you tried to add to a line would extend the line beyond its maximum length. Therefore, the additional text is truncated to the maximum allowable length of the line. User Action: None.
TRUNCATE
records in 'filename' truncated to 'nnn' bytes Facility: SEARCH, SEARCH Command Explanation: One or more records in the listed input file were too long for SEARCH's internal buffers. The records were shortened to the length specified before the SEARCH was performed. The SEARCH was successfully performed on the shortened records. This is an informational message. User Action: None.
TRUNCATED
string too long - truncated Facility: DSR, DIGITAL Standard Runoff Explanation: DSR encountered a string that is too long. The string is truncated. User Action: Edit the file and shorten the line.
TRUNCDAT
computed value is 'value1' value written is 'value2' at location 'address' Facility: LINK, Linker Utility Explanation: This message, which is always issued with the message TRUNC, gives more information about the truncation error. The variable, 'value1' is the value the linker needed to store; 'value2' is the value the linker is able to store (a truncated version). This error is usually caused when a reference using byte or word PC-relative displacement is made to a target requiring longword relative displacement. User Action: Correct the reference to use longword relative addressing mode.
TSRVALLOAD
the TMSCP server is already loaded Facility: SYSGEN, System Generation Utility Explanation: You attempted to load the TMSCP server using the TMSCP command within SYSGEN. The TMSCP server has already been loaded in the recommended way. User Action: The proper way to load the TMSCP server is to set the SYSGEN parameter TMSCP_LOAD to 1. This action loads the server, which services all locally connected MSCP-type tape drives during SYSBOOT.
TSTPHSNAM
error obtaining test phase name Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error during initialization. This error is received in relation to a previously displayed error condition. User Action: Correct the condition leading to this problem and rerun the test. If the error persists, submit a Software Performance Report.
TTL
text too long: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: The text value for the command (for example, .TITLE, .CHAPTER, or .NOTE) is too long for the specified margin setting or page size, or it contains excessive use of underlining, boldface, or overstriking. User Action: Reduce the length of or simplify the text.
TWICE
device 'controller-name' - count changed from 'count' to 'count' Facility: SYSGEN, System Generation Utility Explanation: A controller name is specified twice for a given SYSGEN command CONFIGURE. User Action: Verify the value you intend to use.
TWOWIDTHS
the /WIDTH and /LINE_WIDTH qualifiers are redundant - /LINE_WIDTH value ignored, /WIDTH value used Facility: DIFF, DIFFERENCES Command Explanation: You specified both /WIDTH and /LINE_WIDTH; /LINE_WIDTH is unnecessary. User Action: None.
TYP
error in file type Facility: RMS, VMS Record Management Services Explanation: The file type specified in a file specification contains invalid syntax, for example, more than 39 characters. Or the use of a logical name resulted in a duplicate file type specification. User Action: Correct the syntax of the file specification. Reenter the command or correct the program, as necessary.
TYPMISMCH
library type mismatch Facility: LBR, Librarian Subroutine Package Explanation: This warning message is generated by the Librarian routines. On a call to LBR$OPEN, the library type you requested conflicts with the library type you specified in the create options argument. Processing continues based on the actual library type. User Action: None.
UAEERR
invalid username, username already exists Facility: AUTHORIZE, Authorize Utility Explanation: You tried to create a user-record that already exists by using the DCL command COPY, ADD, or RENAME. User Action: For the new records, enter a user name that does not currently exist.
UAFGETERR
error reading user authorization file Facility: MAIL, Mail Utility Explanation: An error occurred reading the user authorization file. User Action: Use the VMS RMS status code that accompanies this message to determine your action.
UAFOPNERR
error opening user authorization file Facility: MAIL, Mail Utility Explanation: An error occurred opening the user authorization file. User Action: Use the VMS RMS status code that accompanies this message to determine your action.
UBF
invalid user buffer Facility: RMS, VMS Record Management Services Explanation: The user record buffer address of the RAB specified an area of memory that cannot be written to by the caller. User Action: Verify that the call to the VMS RMS service is coded correctly.
UBMAPEXCED
UNIBUS map register allocation exceeded Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UDAPORT
fatal error detected by UDA port driver (PUDRIVER) Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UDEFPSC
attempt to reference undefined psect number 'decimal-number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: A module referenced an undefined psect. User Action: Submit a Software Performance Report on the appropriate language processor.
UDF_BKS
cannot convert UDF records into spanned file Facility: CONVERT, Convert Utility Explanation: UDF records cannot span block boundaries. User Action: Specify no block spanning.
UDF_BLK
cannot fit UDF records into single block bucket Facility: CONVERT, Convert Utility Explanation: The records in the file are longer than 512 bytes (1 block). User Action: Specify a bucket size that is long enough for the records.
UDFENV
'undefined environment reference' Facility: LINK, Linker Utility Explanation: An undefined reference to an environment is encountered after Pass 1. User Action: Determine why the reference is undefined and correct the condition.
UDFSYM
'symbol-name' Facility: LINK, Linker Utility Explanation: There are strong undefined symbol references after Pass 1. This message is output for each undefined symbol. User Action: Determine why the symbols are undefined and correct the condition.
UDS
undefined symbol: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR has detected an unrecognizable symbol (for example, $$name), the name of which is not defined. User Action: Remove the symbol.
UICERR
error in UIC specification Facility: AUTHORIZE, Authorize Utility Explanation: You specified a User Identification Code (UIC) incorrectly. User Identification Codes have the format [group,member] where the values for group and member may be numeric or alphanumeric. The system translates each code into a 32-bit octal string; the high-order 16 bits are the group identifier, the low-order 16 bits are the member identifier. The member identifer must be unique for each system user. In a numeric UIC, the group identifier may have an octal value between 1 and 37776. The member identifier may have an octal value between 0 and 177776. You can omit leading zeros when specifying a numeric identifier. In an alphanumeric UIC, the group and member identifiers may have between 1 and 31 characters, of which at least one must be alphabetic. Alphabetic characters are the letters A-Z, and the underscore and dollar sign symbols. User Action: Correct the specification of the UIC, according to the syntax rules explained above.
UID_INV
resource manager/transaction identifier contains non-hex characters Facility: LMCP, Log Manager Control Program Explanation: The user has entered a hexadecimal resource manager or transaction identifier containing invalid hexadecimal characters. User Action: Enter the hexadecimal resource manager or transaction identifier in the format xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx, where x is a hexadecimal character 0-F.
UID_LENGTH
resource manager/transaction identifier has invalid length Facility: LMCP, Log Manager Control Program Explanation: The resource manager or transaction identifier entered does not satisfy the required length of hexadecimal characters. The log identifier should contain 32 hexadecimal characters plus four dashes. User Action: Enter the resource manager or transaction identifier with the correct length using the format xxxxxxxx-xxxx-xxxx- xxxxxxxxxxxx, where x is a hexadecimal character 0-F.
UKNFACILITY
unknown facility code specified Facility: VAXTPU, VAX Text Processing Utility Explanation: You specified a facility code that does not match any established action routine. User Action: Establish the facility's action routine before attempting to use it.
UME
unmatched end command: 'string' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: An .END command (for example, .END NOTE) is detected, but the associated beginning command (.NOTE) is not. User Action: Insert the associated beginning command.
UNABLCREVA
unable to create virtual address space Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNABLE
unable to create file
Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command CREATE
cannot be created for one of the following reasons:
o The device or directory does not exist.
o The volume is write-locked or the user does not have write
access to it.
o The volume is full or has insufficient contiguous space to
complete the request.
User Action: Correct the situation and reenter the command.
UNABLE
unable to create parameter file
Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command WRITE cannot
be created for one of the following reasons:
o The device or directory does not exist.
o The volume is write-locked or the user does not have write
access.
o The volume is full.
User Action: Correct the situation and reenter the command.
UNABLE
unable to open file Facility: SYSGEN, System Generation Utility Explanation: The file specified in the SYSGEN command USE cannot be found or opened. User Action: Reenter the command specifying the correct file specification.
UNARYOPER
operand combination 'operator' 'data-type' unsupported Facility: VAXTPU, VAX Text Processing Utility Explanation: The specified operator does not support the specified data type. User Action: Use only supported data types with the operator.
UNASEFC
unassociated event flag cluster Facility: SYSTEM, VMS System Services and PTD, Pseudo Terminal Explanation: An image called a system service specifying an event flag number in a common cluster with which it is not associated. User Action: Check for a programming error. Verify the event flag numbers specified in system service calls, and verify that the required request to associate with the cluster completed successfully.
UNDEFINEDPROC
undefined procedure call 'name' Facility: VAXTPU, VAX Text Processing Utility Explanation: You have called an undefined procedure. User Action: Check the spelling of the procedure name.
UNDEFLINK
undefined link Facility: LAT, LAT Facility Explanation: You specified a link that does not exist on the local node. User Action: Use the LATCP command SHOW LINK to see which links exist on the local node.
UNDEFOUTPUT
line 'line-number': Output parameter/qualifier 'name' is not defined Facility: CDU, Command Definition Utility Explanation: CDU encountered an undefined OUTPUT parameter /qualifier. All OUTPUT parameters/qualifiers must be previously defined. User Action: Edit the CLD file so that all OUTPUT parameters /qualifiers are defined.
UNDEFSYM
undefined symbol Facility: MACRO, VAX MACRO Assembler Explanation: A local label is referred to but not defined in a local label block; or, if GLOBAL is disabled, a symbol is referred to but not defined in the module or specified in an .EXTERNAL directive. User Action: Define the local label or symbol or specify the symbol in an .EXTERNAL directive.
UNDEFSYNTAX
line 'line-number': Syntax 'syntax-name' is not defined Facility: CDU, Command Definition Utility Explanation: CDU encountered an undefined syntax name during a SYNTAX assignment. All syntax names must be previously defined. User Action: Edit the CLD file so that all names in SYNTAX assignments are defined.
UNDEFTYPE
line 'line-number': Type 'type-name' is not defined Facility: CDU, Command Definition Utility Explanation: CDU encountered an undefined type name during a TYPE assignment. All type names must be previously defined. User Action: Edit the CLD file so that all names in TYPE assignments are defined.
UNDEFXFRAD
undefined transfer address Facility: MACRO, VAX MACRO Assembler Explanation: The .END directive specified a transfer address that is not defined in the module or specified in an .EXTERNAL directive. User Action: Define the transfer address or delete it from the .END directive.
UNDEXP
undefined exponentiation User PC 'location' Facility: MTH, Mathematics Facility Explanation: An expression contained exponentiation that cannot be mathematically evaluated, for example, 0.**0. The result is the reserved operand, minus zero. User Action: Use the traceback information or the PC displayed in the message to locate the error in your program and correct the math expression.
UNDFIL
file has been not opened by DCL - check logical name Facility: CLI, Command Language Interpreter (DCL) Explanation: A DCL command READ, WRITE, or CLOSE specified a file that is not currently opened or for which no logical name is assigned. User Action: Reenter the command; specify the name of an opened file. Or use the DCL command OPEN to open the file before attempting to read or write it.
UNDKEY
'state' key 'key-name' is undefined Facility: CLI, Command Language Interpreter (DCL) Explanation: You attempted to use the SHOW/KEY or the DELETE/KEY command to show or delete the definition of a key that is not defined. User Action: None.
UNDOPTION
undefined option flag is set Facility: SORT, Sort/Merge Utility Explanation: You can set only those option flags used by SORT /MERGE. All other bits in the longword are reserved and must be zero. User Action: Correct your specification file.
UNDSYM
undefined symbol - check validity and spelling Facility: CLI, Command Language Interpreter (DCL) Explanation: A character string beginning with an alphabetic character is encountered in a context where the command interpreter evaluates expressions and automatically attempts symbol substitution. The character string is not defined as a local symbol for the current command level or as a global symbol. User Action: Verify that the symbol is defined and reenter the command. If the error occurred in a command procedure, correct the procedure to ensure that the symbol is defined locally or globally, as required before the statement that caused the error.
UNDTERNAM
undefined terminal name Facility: SMG, Screen Management Facility Explanation: The requested terminal definition is not found in the caller's private copy of Termtable or the system copy Termtable. User Action: If you intended to use a private terminal definition, make sure that TERMTABLE.EXE exists in your private directory and that the logical name TERM$TABLOC points to it. If you expected your terminal to be defined in the system Termtable, check with your system manager.
UNDTERNOP
undefined terminal - couldn't access private terminal table Facility: SMG, Screen Management Facility Explanation: The requested terminal definition is not found in the caller's private copy of Termtable or the system Termtable. The caller's private Termtable could not be accessed, either because it did not exist or because RMS could not open the file. User Action: If you intended to use a definition from your private Termtable, make sure that TERMTABLE.EXE exists in your private directory and that the logical name TERM$TABLOC points to it. Make sure that you have read access to the file.
UNDTERNOS
undefined terminal - couldn't access system terminal tables Facility: SMG, Screen Management Facility Explanation: The requested terminal definition is not found in the caller's private Termtable or the system Termtable. The system Termtable is unavailable. User Action: The system Termtable should be mapped as a global section and therefore should always be available. Consult your system manager.
UNDTERTYP
undefined terminal type Facility: SMG, Screen Management Facility Explanation: The definition for the requested terminal type is not found in the caller's private copy of Termtable or the system Termtable. User Action: If you intended to use a private definition, make sure that TERMTABLE.EXE exists in your private directory and that the logical name TERM$TABLOC points to it. If you expected your terminal definition to exist in the system Termtable, consult your system manager.
UNDWIDCLA
undefined widget class specified Facility: VAXTPU, VAX Text Processing Utility Explanation: A widget class integer that is not known to VAXTPU was specified to the CREATE_WIDGET built-in procedure. User Action: Define a widget class using the DEFINE_WIDGET_CLASS built-in procedure before attempting to call CREATE_WIDGET.
UNECLIERR
unexpected CLI error Facility: LIB, Library Facility Explanation: The CLI returned an error status that is not recognized. This error could be caused by use of a nonstandard CLI. User Action: If this error occurs while using the DCL Command Language Interpreter, submit a Software Performance Report (SPR). Unexpected characters after end of command Facility: EDT, EDT Editor Explanation: The command you entered ends with a string of one or more characters that is not part of the command. The rest of the command is valid. User Action: Reenter the command removing the invalid characters from the end of the command line.
UNEXPECTED
installation terminated due to unexpected event. Facility: VMSINSTAL, Install Procedures Explanation: An unexpected event has ended the installation of VMSINSTAL. See accompanying messages for more information. User Action: If you can determine and resolve the problem, reinstall the product. Otherwise, contact the Digital Services Group. Unexpected Interrupt - CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx' Facility: VAXport, VAXport Driver Explanation: The port driver attempts to reinitialize the port; after 50 failed attempts, it marks the device off line. User Action: Call the Digital Services Group to check the port hardware.
UNEXPERR
unexpected error Facility: MONITOR, Monitor Utility Explanation: An unexpected hardware or software error condition occurred. To obtain more information, examine the accompanying linked message. User Action: Correct the condition causing the failure, if possible, and reenter the MONITOR request. Otherwise, submit a Software Performance Report (SPR).
UNEXPERR
unexpected exception Facility: VAXCLUSTER, VAXcluster Facility Explanation: A hardware exception occurred during bootstrap execution. User Action: Run diagnostics to check for hardware errors.
UNEXPERR
unexpected interrupt Facility: VAXCLUSTER, VAXcluster Facility Explanation: An unknown interrupt occurred during bootstrap execution. User Action: Try the operations again. If the problem persists, run diagnostics to check for hardware errors.
UNEXPIOINT
unexpected UNIBUS adapter interrupt Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNIMP
the specified DECthreads feature is not implemented Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: You attempted to use a feature that is not implemented in the version of DECthreads that you are running. This error can occur when a program developed on a system running a new version of DECthreads is executed on a system that is running an old version of DECthreads. User Action: Use a later version of DECthreads that supports the feature or do not attempt to use the feature with an old version of DECthreads.
UNINITEXC
uninitialized exception raised Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The EXC_HANDLING.H package, which provides portable exceptions for the C language, has attempted to raise an exception that has not been initialized. User Action: Study the error messages to determine the program location where the uninitialized exception is being raised. Use the exception_init macro defined in the EXC_HANDLING.H package to initialize the exception.
UNINITVAR
uninitialized variable Facility: VAXTPU, VAX Text Processing Utility Explanation: You have tried to use an unspecified variable. User Action: Check the spelling of the variable. You may assign a value to the variable by placing it on the left-hand side of an assignment statement.
UNIVSTAR
UNIVERSAL=* option is ignored unless /NOEXECUTABLE specified Facility: LINK, Linker Utility Explanation: The UNIVERSAL=* option has been specified in the options file when producing a shareable image output file. This option is no longer valid when producing image files, although it is accepted when generating only a symbol table (.STB) output file. User Action: If you desire a shareable image output file, then you must specify all universal symbols explicitly. Otherwise, if you only need a symbol table file, then specify /NOEXECUTABLE to suppress image file output.
UNKADAP
unknown adapter type encountered Facility: SYSGEN, System Generation Utility Explanation: An internal error occurred when SYSGEN tried to parse an adapter name. User Action: Check the command line entered.
UNKCLASS
unknown device class found, 'device-class-value' Facility: ERF, Error Log Utility Explanation: An entry with an unknown or unsupported device class is encountered. User Action: Use the UNKNOWN_ENTRIES keyword with the /INCLUDE qualifier to obtain the Report (SPR).
UNKCPU
unknown CPU type encountered Facility: SYSGEN, System Generation Utility Explanation: You specified an unknown CPU type with the SYSGEN command SHOW/ADAPTER. User Action: Retry specifying a different CPU type.
UNKCPU
unknown or unsupported processor Facility: VAXCLUSTER, VAXcluster Facility Explanation: The system is not supported as a satellite node with this version of the VMS operating system. User Action: Refer to the VMS Software Product Description (SPD) for supported configurations for VAXclusters and check which versions of the VMS operating system support your processor.
UNKDEV
unknown device type Facility: INIT, INITIALIZE Command and MOUNT, Mount Utility Explanation: The device type specified is unknown or invalid. User Action: Verify the device name (or logical name if a logical name is specified), and reenter the command with the correct device name.
UNKENTRY
unknown entry type, 'entry-type value' Facility: ERF, Error Log Utility Explanation: An entry with an unknown or unsupported entry type is encountered. User Action: Use the UNKNOWN_ENTRIES keyword with the /INCLUDE qualifier to obtain the Report (SPR).
UNKESCAPE
unknown escape sequence read Facility: VAXTPU, VAX Text Processing Utility Explanation: TPU does not know how to process the escape sequence. User Action: Use only supported terminals with TPU.
UNKESCSEQ
unknown escape sequence received from DECtalk Facility: DTK, DECtalk Facility Explanation: You passed an escape sequence to a DTK$ input routine that it is unable to understand. User Action: Submit a Software Performance Report (SPR).
UNKKEYWORD
an unknown keyword has been used as an argument Facility: VAXTPU, VAX Text Processing Utility Explanation: You have specified an unrecognizable item in place of a valid keyword. User Action: Execute the built-in procedure SHOW (KEYWORDS) for a list of valid keywords.
UNKMSG
unknown message header type Facility: REM, Set Host Facility Explanation: A system internal error has occurred. User Action: Submit a Software Performance Report (SPR).
UNKNFAIL
internal VAXTPU failure, unknown reason Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal error occurred in the VAXTPU software. User Action: Submit a Software Performance Report (SPR).
UNKNOPR
unknown operator Facility: OPCOM, Operator Communication Process Explanation: A DCL command REQUEST or REPLY specified an invalid operator name; the keyword is invalid. No request message is sent. User Action: Reenter the DCL command REQUEST or REPLY and specify a valid operator name.
UNKNOWNCLEARINGHOUSE
the clearinghouse does not exist Facility: DNS, Distributed Name Service Clerk Service Explanation: The DNS clerk attempted to contact a clearinghouse that does not exist in the namespace. This can occur when the DNS clerk caches are out of date or when the replica set of a given directory is out of date. User Action: None. The DNS clerk will try to contact other clearinghouses to satisfy the request.
UNKNOWN_TAG
'reference-string' is an unknown tag in statement 'number' Facility: FDL, Create/FDL Utility Explanation: No value or an incorrect value was used for the STORED_SEMANTICS secondary attribute. User Action: Use the correct value.
UNKNPRQ
unknown Inter-processor Request Message Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNKOBJECT
unknown object in SMI call Facility: SMI, System Management Integrator/Server Explanation: This message indicates an internal error. The server does not recognize the object. User Action: Ensure that all the nodes in the environment contain the correct versions of SMISERVER and SYSMAN. If no problems are found, submit a Software Performance Report with the exact sequence of SYSMAN commands leading to the error.
UNKOPCODE
unknown opcode Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal error occurred in the VAXTPU software. User Action: Submit a Software Performance Report (SPR).
UNKPKTFMT
unknown packet format, entry 'number' skipped Facility: ERF, Error Log Utility Explanation: An entry with an unknown or unsupported record format was encountered. User Action: Submit a Software Performance Report (SPR).
UNKREPLY
unknown reply received from DECtalk Facility: DTK, DECtalk Facility Explanation: You passed an escape sequence to a DTK$ input routine that it could not parse correctly. User Action: Submit a Software Performance Report (SPR).
UNKRSTRT
unknown restart code Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNKTYPE
unknown data type Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal error occurred in the VAXTPU software. User Action: Submit a Software Performance Report (SPR).
UNKTYPE
unknown device type, 'device-type value' Facility: ERF, Error Log Utility Explanation: An entry with an unknown or unsupported device type is encountered. User Action: Use the UNKNOWN_ENTRIES keyword with the /INCLUDE qualifier to obtain the Report (SPR).
UNKWNDESC
unknown descriptor type Facility: VAXTPU, VAX Text Processing Utility Explanation: A descriptor in the descriptor array has an unknown data type. User Action: Use a valid data type.
UNLKVOL
error unlocking volume set Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to unlock the volume set to allow allocation. An accompanying message provides additional information. User Action: Correct the condition that caused the error, then dismount and remount the volume set.
UNLOCKED
'filename' unlocked Facility: SET, SET Facility Explanation: The file has been successfully unlocked. User Action: None.
UNLOCKED
'filespec' unlocked Facility: Shared by several facilities Explanation: The file specified by a DCL command UNLOCK is unlocked. User Action: None.
UNLOCKERR
error unlocking 'filename' Facility: SET, SET Facility Explanation: An error occurred when the file is being unlocked. This message is issued with an accompanying message. User Action: Take corrective action based on the accompanying message.
UNPRIKW
unrecognized primary keyword in statement 'number'<CRLF>' reference- text' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: A keyword was misspelled. User Action: Edit the FDL file to correct the spelling and try again.
UNPROPARM
unprocessed parameters Facility: CLI, Command Language Interpreter (DCL) Explanation: A command contained more parameters than are currently supported. User Action: Reenter the command; specify only the maximum number of parameters.
UNPROQUAL
unprocessed qualifiers Facility: CLI, Command Language Interpreter (DCL) Explanation: The message indicates that qualifiers present with the command were ignored. The operating system does not normally display this message. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition. If either the /SHOW or the /CROSS_REFERENCE qualifier is specified without /LIST, reenter the command with the /LIST qualifier.
UNPROQUAL
unprocessed qualifiers Facility: CLI, Command Language Interpreter (DCL) and MACRO, VAX MACRO Assembler Explanation: This message is associated with a status code returned from the command interpreter's result parse routine. The message indicates that qualifiers present with the command were ignored. The operating system does not normally display this message. If this error occurred as a result of a macro assembler operation either the /SHOW or the /CROSS_REFERENCE qualifier is specified without the /LIST qualifier. The MACRO assembler does not process the source file or produce an object module. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition. If either the /SHOW or the /CROSS_REFERENCE qualifier is specified without /LIST, reenter the command with the /LIST qualifier.
UNQUAKW
unrecognized qualifier keyword in statement 'number'<CRLF>'reference-text' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: A keyword was misspelled. User Action: Edit the FDL file to correct the spelling and try again.
UNRCMD
unrecognized command 'command' Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The command entered is not a valid SHOW CLUSTER command. User Action: Enter a valid command or enter the HELP command for a list of valid commands.
UNRCMP
unrecognized component 'text' Facility: NCP, Network Control Program Explanation: A component is not known to the node. The 'text' part of this message contains the component identification. User Action: Review the command description and reenter your command with the correct component.
UNREACHABLE
node 'node-name' not reachable Facility: LAT, LAT Facility Explanation: A LAT connection attempt to a specified node and service failed because the node offering the service is unreachable. User Action: Locate the node and determine what is preventing connections from occuring.
UNREACHABLE
remote node is not currently reachable Facility: SYSTEM, VMS System Services Explanation: An attempt is made to initiate a DECnet-VAX logical link connection. The specified node exceeded routing requirements, that is, the path to the node contains too many intermediate nodes. User Action: This condition will persist until there is a change in the network topology. Notify your system manager. Refer to the VMS Networking Manual for additional information.
UNREACHABLE
unreachable code Facility: VAXTPU, VAX Text Processing Utility Explanation: This code will never be executed. The compiler might remove this code to optimize performance. User Action: Remove the unreachable code. Unrecognized command Facility: EDT, EDT Editor Explanation: EDT does not recognize or support the command entered. The command may have been incorrectly specified. User Action: Check the command syntax and reenter the command. Unrecognized command option Facility: EDT, EDT Editor Explanation: The command you entered includes an invalid option /qualifier. User Action: Reenter the command specifying a valid option /qualifier. Unrecognized SCA Packet Facility: VAXport, VAXport Driver Explanation: The VAXport driver closes the port-to-port virtual circuit to the remote port. If the virtual circuit is already closed, the port driver inhibits datagram reception from the remote port. User Action: Submit a Software Performance Report, including the error log file that contains this entry and the crash dumps from both the local and remote systems.
UNRECSTA
unrecognized statement Facility: SMG, Screen Management Facility Explanation: The Termtable compiler encountered a statement that it does not recognize. User Action: Check your definition. Make sure you have spelled keywords correctly and that statements appear only in valid sequences.
UNRECSTMT
unrecognized statement Facility: MACRO, VAX MACRO Assembler Explanation: The operator is not an opcode, directive, user- defined opcode, previously defined macro, or macro in a library. User Action: Change the operator to a valid opcode, directive, or macro; or define the macro.
UNRELVOL
volume is not part of volume set being mounted Facility: MOUNT, Mount Utility Explanation: You specified a volume to be mounted that is not part of a volume set. User Action: Either mount the specified volume separately or specify the /BIND qualifier with the DCL command MOUNT.
UNRFORCOD
unrecognized format code Facility: LIB, Library Facility Explanation: Unrecognized format code User Action: Examine the format string for invalid format code. The format string may be supplied in the logical name or it can be hard-coded.
UNRFUN
unrecognized function or option Facility: NCP, Network Control Program Explanation: Either the verb or component requested a feature that is unsupported or is unrecognized. User Action: Consult the documentation for the supported functions and operations.
UNRKEY
keyword is an unrecognized keyword Facility: LIB, Library Facility Explanation: This message is associated with a status code returned from the Run-Time Library. The indicated keyword is not recognized. User Action: Correct the program and specify a valid keyword.
UNRKEY
unrecognized field or class name 'class-name' Facility: SHOW CLUSTER, Show Cluster Utility Explanation: The field or class name entered is not valid in any Report (SPR). User Action: Enter a valid field or class name, or enter the HELP FIELDS or HELP CLASSES command for a list of valid field or class names.
UNRPTY
unrecognized parameter type 'text' Facility: NCP, Network Control Program Explanation: A parameter type specified in your command is incorrect and therefore unrecognizable by the network management software. The 'text' part of the message identifies the unrecognizable parameter. User Action: Review the command description and reenter your command with the correct parameter.
UNSAFE
drive unsafe Facility: SYSTEM, VMS System Services Explanation: The drive malfunctioned and cannot be used. User Action: Check the status of the device and repeat the request. If the failure persists, notify the system manager.
UNSECKW
unrecognized secondary keyword in statement 'number'<CRLF>'reference-text' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: A keyword was mispelled. User Action: Edit the FDL file to correct the spelling and try again.
UNSOLICIT
response not solicited Facility: SYSTEM, VMS System Services Explanation: A message is received that is not requested from a local process. This may be an information exception or a control message from a remote user. User Action: Process the message
UNSTLEV
the /INPUT file has an unsupported MONITOR file structure level Facility: MONITOR, Monitor Utility Explanation: The input recording file is a valid MONITOR file with a file structure that is not supported by the current version of MONITOR. User Action: Use the monitor convert command to update the recording file to the current structure level.
UNSUPRTCPU
unsupported CPU Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNSVRS
version of listener on executor is not supported Facility: NCP, Network Control Program Explanation: The network management listener (NML) did not respond with a valid version number. The executor cannot be accessed by network management. User Action: None. You cannot connect to the node until it is upgraded to a supported version.
UNTERMARG
unterminated argument Facility: MACRO, VAX MACRO Assembler Explanation: The string argument is missing a delimiter or the macro argument is missing an angle bracket. User Action: Add a delimiter or an angle bracket to the string argument.
UNTERMCOND
unterminated conditional Facility: MACRO, VAX MACRO Assembler Explanation: A conditional assembly block is not terminated by the .ENDC directive. The assembler inserted the .ENDC directive before the .END directive. User Action: Add the .ENDC directive to the conditional assembly block.
UNWIND
unwind currently in progress Facility: SYSTEM, VMS System Services Explanation: This status code is used as a call argument for condition handlers called during the search of the call stack during an unwind operation. The operating system does not normally display this message. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
UNWINDING
unwind already in progress Facility: SYSTEM, VMS System Services Explanation: A condition handler is called during an unwind operation and attempted to issue an unwind request. The operating system does not normally display this message. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
UNXINTEXC
unexpected interrupt or exception Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UNXPCTSTS
unexpected status detected. Expected 'status'. Found: Facility: Shared by several facilities Explanation: An error is detected by a system service. A subsequent message explains the reason for the error. User Action: See the description of the accompanying VMS RMS message in this manual.
UNXSIGNAL
unexpected signal name in ACP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
UPDATE
patch with eco level 'nn' ignored due to update qualifier Facility: PATCH, Patch Utility Explanation: The Patch Utility ignored the patch associated with this ECO level because you used the /UPDATE qualifier and did not include this particular ECO level in the qualifier's value list. User Action: Add the ECO level to the qualifier's value list; retry if you want this ECO to be applied.
UPDATED
file 'filename' is already updated. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL is attempting to update a system text file, but the file has already been updated successfully. User Action: None.
UPDURTRAV
index update during traverse illegal Facility: LBR, Librarian Subroutine Package Explanation: The routine that you specify in the routine- name argument cannot contain any calls to either LBR$DELETE or LBR$INSERT_KEY. User Action: Remove any embedded calls to either LBR$DELETE or LBR$INSERT_KEY before calling the routine.
UPI
UPI not set when sharing and BIO or BRO set Facility: RMS, VMS Record Management Services Explanation: VMS RMS permits file sharing when block I/O access (BIO or BRO) is specified and the file-sharing option UPI is specified also. The user program must provide all required interlocks. User Action: Verify that the call to the VMS RMS service is coded correctly.
URE
unrecoverable error processing record 'ln' on page 'pn' of input file 'filename' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: An irrecoverable I/O error occurred, terminating the processing at the specified edit line (ln) and page number (pn) of the input file. This is a DSR internal error. User Action: Submit a Software Performance Report (SPR).
URR
unrecognized request: 'n' Facility: RUNOFF, DIGITAL Standard Runoff Explanation: DSR detected an unrecognizable internal failure request. This indicates DSR internal error. User Action: Reprocess the file. If the error occurs again, submit a Software Performance Report (SPR).
USCALL
target of CALL not found - check spelling and presence of label Facility: CLI, Command Language Interpreter (DCL) Explanation: The destination label of a CALL statement could not be found. To be a valid destination, the label must be followed by the SUBROUTINE statement. User Action: Make sure that the CALL statement in your command procedure is using the correct label, or that the subroutine label exists and is followed by the SUBROUTINE statement.
USEANS
auto-answer file will be used. Facility: VMSINSTAL, Install Procedures Explanation: You specified the auto-answer option when you started VMSINSTAL. The recorded answers will be used for the installation. User Action: You do not have to answer prompts and questions displayed by the product. If you want to record new answers, delete the answer file and install the product with the auto- answer option.
USE_ERROR
requested operation is inappropriate for the specified object Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: The state or type of an object is inappropriate for the operation; for example, the operation attempts to unlock a mutex that is not locked. User Action: Determine which routine caused the error and consult the documentation to learn which object states are appropriate for the routine.
USEFLORES
use of floating reserved operand Facility: OTS, General Purpose Facility and LIB, Library Facility Explanation: A program accessed a reserved floating operand. This message is associated with a status code returned by the Run-Time Library. User Action: Use the traceback information to locate the statement that caused the error and correct your program.
USERDSABL
user 'username' cannot receive new mail Facility: MAIL, Mail Utility Explanation: You have attempted to send mail to a user who has been disallowed from receiving mail. User Action: None.
USERQST
request 'number' from user 'user-name' Facility: OPCOM, Operator Communication Process Explanation: This is a user message to the operator; a response is required. User Action: Wait for the operator response.
USERSPEC
invalid user specification 'user-name' Facility: MAIL, Mail Utility Explanation: While sending a mail message to a list of users, you specified an invalid user name. User Action: Ensure that your list contains valid user names and retry the operation.
USERVAL
user validation error Facility: INPSMB, Input Symbiont Explanation: The user name and password specified in a batch job entered from a card reader are not authorized on the system according to the user authorization file. User Action: Consult your system manager.
USEUDFEN2
undefined environment number 'number' referenced in psect 'string' offset 'hexadecimal-number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An undefined environment is referenced in a module. User Action: Ensure that all referenced environments are defined.
USEUDFENV
undefined environment 'string' referenced in psect 'string' offset 'hexadecimal-number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An undefined environment is referenced in a module. User Action: Ensure that all referenced environments are defined.
USEUDFLSY
undefined module-local symbol 'symbol name' referenced in psect 'string' offset 'hexadecimal-number' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An undefined module-local symbol is referenced in a module. User Action: Ensure that all referenced module-local symbols are defined.
USEUNDEF
undefined symbol 'symbol-name' referenced in psect 'psect-name' offset 'address' in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An undefined symbol is referenced in a module. User Action: Define the symbol.
USEUNDEF2
undefined symbol 'symbol-name' referenced in debug or traceback record in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: An undefined symbol is referenced in a debug or traceback record. User Action: Define the symbol.
USGOSUB
target of GOSUB not found - check spelling and presence of label Facility: CLI, Command Language Interpreter (DCL) Explanation: The destination label of a GOSUB statement could not be found. User Action: Make sure that the GOSUB statement in your command procedure is using the correct label, or that the subroutine label exists.
USGOTO
target of GOTO not found - check spelling and presence of label Facility: CLI, Command Language Interpreter (DCL) Explanation: The label of a GOTO command could not be found in the current command file. User Action: Correct the command file by ensuring that the correct label exists.
USRINPERR
user input routine returned error status Facility: LBR, Librarian Subroutine Package Explanation: A user-supplied input routine returned a nonsuccess status to LBR$OUTPUT_HELP. User Action: Determine the reason for the failure in the input routine.
USRTFR
image 'image-name' has no user transfer address Facility: LINK, Linker Utility Explanation: An executable image does not contain a transfer address. User Action: Define a transfer address for the image.
USZ
invalid user buffer size Facility: RMS, VMS Record Management Services Explanation: The size specified in the user record buffer size field is invalid. The buffer size must be in the range of 1 to 65,535. User Action: Verify that the call to the VMS RMS service is coded correctly.
V2COMP
parameter not applicable on V2.0 DECnet executor node Facility: NCP, Network Control Program Explanation: A given request could not be converted into a Version 2.0 NICE message when connected to a Version 2.0 network management listener (NML). User Action: Remove the invalid parameter from the command line.
VA_IN_USE
virtual address already in use Facility: SYSTEM, VMS System Services Explanation: A PTD$CREATE request specified a buffer address that is already being used by another PTD$CREATE request or by another system memory management facility such as SYS$CRMPSC. This message can occur when the main image or a sharable image is based. An image is based if a linker options file is used to specify a base virtual address at which the image should be loaded or if certain language constructs are used that produce nonrelocatable code. User Action: Allocate a new region of virtual memory to be used for I/O buffers, then reissue the PTD$CREATE request specifying the new region.
VALERR
specified value is out of legal range Facility: Shared by several facilities Explanation: A value is specified that is not within legal range. User Action: Respecify a value within legal range.
VALPRI
value required on primary in statement 'number' Facility: FDL, Create/FDL Utility, FDL, Edit/FDL Utility Explanation: A primary was specified that requires a value, but none was given. User Action: Supply a value for the primary.
VALREQ
missing qualifier or keyword value - supply all required values Facility: CLI, Command Language Interpreter (DCL) Explanation: A value must be specified for the qualifier or keyword. User Action: Reenter the command and supply a value to the qualifier or keyword.
VALTOOBIG
value too large for field Facility: AUTHORIZE, Authorize Utility Explanation: The value you specified for a qualifier is too large. User Action: See the VMS Authorize Utility Manual for information about qualifier value sizes. Enter a smaller value for the qualifier.
VALUE
set to maximum Facility: SYSGEN, System Generation Utility Explanation: A SYSGEN command SET is entered to set a parameter to a value that is greater than the allowable maximum. The SYSGEN utility reduces the value to the allowable maximum. User Action: None.
VALUE
set to minimum Facility: SYSGEN, System Generation Utility Explanation: A SYSGEN command SET is entered to set a parameter to a value that is less than the allowable minimum. The SYSGEN utility increases the value to the permissible minimum. User Action: None.
VARITH
vector arithmetic fault, summary=xx, mask=xx, PC=location,
PSL=xxxxxxxx
Facility: SYSTEM, VMS System Services
Explanation: A vector operate instruction, executing within
the context of the current context, has resulted in a vector
arithmetic trap. The message indicates an exception condition
and is followed by a register and stack dump to help locate the
error.
The summary item is a longword mask, the bits of which, when set,
signify the following vector arithmetic exception conditions:
o Bit 0 = floating underflow
o Bit 1 = floating divide by zero
o Bit 2 = floating reserved operand
o Bit 3 = floating overflow
o Bit 5 = integer overflow
The mask item is a longword, the bits of which (0 through 15)
correspond to the VAX vector registers (V0 through V15). When set,
a bit indicates that an element of the associated vector register
was involved in an operation that caused one or more of the vector
arithemetic exceptions reported in the summary item.
The message also includes the Program counter (PC) of the vector
instruction which caused the exception to be reported (note that
this instruction is not always that that caused the exception),
and the processor status longword (PSL) at the time the exception
was reported.
User Action:
One or more of the following debugging strategies may help you
determine which calculations resulted in the reported error or
errors:
o Recompile the source with the /DEBUG, /NOVECTOR, /CHECK=BOUNDS
qualifiers; relink using the /DEBUG and /MAP qualifiers; and
run the resulting scalar image with the /DEBUG qualifier. A
scalar arithmetic exception should occur at the calculation
that caused the original vector arithmetic exception.
o Recompile the source using the /DEBUG, /LIST, and /VECTOR
qualifiers; relink using the /DEBUG and /MAP qualifiers; and
run the resulting image with the /DEBUG qualifier. Use the
SET VECTOR_MODE SYNCHRONIZED or the SYNCHRONIZE VECTOR_MODE
debugger command to guarantee that all exceptions resulting
from vector operations be delivered before the execution of the
next scalar instruction. Step through the program, inspecting
the contents of those vector registers that are involved in
each vector operation.
When a vector operate instruction causes an floating-point
exception in a vector element, the exception result is encoded
into the corresponding element of the destination register.
When the destination vector register is the target of an
EXAMINE/FLOAT debugger command, the debugger displays the
decoded exception message in the associated vector element.
When a vector operate instruction causes an integer overflow in
a vector element, the corresponding element of the destination
register contains a value that is larger than 32 bits. When
the destination vector register is the target of an EXAMINE
debugger command, inspect each element for a value larger than
2[32].
VASFUL
virtual address space is full Facility: SYSTEM, VMS System Services Explanation: The virtual address space is full. User Action: Reboot and increase the amount of allowable virtual address space. If this message is associated with a vector disabled (VECDIS) status code, insufficient process virtual address space exists to allow the current process's mainline vector state to be saved.
VASOVF
system virtual address space limit exceeded Facility: SYSBOOT, System Bootstrap Facility Explanation: The combination of SYSGEN parameters used to specify various capacities within the operating system have pushed the size of the operating system address space over the limit allowed by the VAX architecture. User Action: Reduce one or more parameters which contribute to the virtual address space size required by VMS: VIRTUALPAGECNT, BALSETCNT. By using AUTOGEN to set these values for your system, you will avoid selection of parameter combinations that cause system space to overflow its architectural boundaries. VAXport is going off line Facility: VAXport, VAXport Driver Explanation: The VAXport driver halts port operations. User Action: Restore power to the port hardware. VAXport is reinitializing Facility: VAXport, VAXport Driver Explanation: The VAXport reinitializes the port and restarts port operations. User Action: None.
VBNERROR
'filespec' has duplicate blocks 'n' through 'n' Facility: BACKUP, Backup Utility Explanation: The specified blocks of the specified file were present more than once in the input save set. Data in the save set may be corrupted. User Action: Examine the file for corruption and reconstruct as necessary. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility; in this case, submit a Software Performance Report (SPR).
VBNMAPFAIL
virtual block map failure Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
VBNMISSING
'filespec' has missing blocks 'n' through 'n' Facility: BACKUP, Backup Utility Explanation: The specified blocks of the specified file were missing from the input save set. Data in the blocks is lost. User Action: Examine the file for corruption and reconstruct as necessary. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility; in this case, submit a Software Performance Report (SPR).
VBNPASTEOF
'filespec' has blocks 'n' through 'n' past end of file Facility: BACKUP, Backup Utility Explanation: The specified blocks of the specified file were present in the input save set although they follow the end of file block. Data in the save set may be corrupted. User Action: Examine the file for corruption and reconstruct as necessary. If this error occurs during a disk-to-disk (copy) operation, it indicates a software error in the Backup Utility; in this case, submit a Software Performance Report (SPR).
VCALNORCV
expected vector alignment exception not received Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered a hardware error while testing a vector processor's ability to generate memory management exceptions. User Action: Run diagnostics for VAX Vectors, or contact the Digital Services Group.
VCLIM
LAT circuit limit reached Facility: LAT, LAT Facility Explanation: The maximum number of allowable LAT circuits has been reached. User Action: Retry the operation when a circuit becomes available.
VCSESLIM
session limit for LAT circuit reached Facility: LAT, LAT Facility Explanation: A LAT connection attempt failed because the connection between the local node and the destination node already has the maximum number of sessions allowed. User Action: Attempt a connection to another node offering the same service or wait until a session becomes available.
VECALIGN
access violation, reason mask = xx, virtual address = location, PC = location, PSL = xxxxxxx Facility: SYSTEM, VMS System Services Explanation: The current process has issued a VAX vector memory access instruction that has attempted an operation on an improperly-aligned vector element. The VAX architecture requires that vector operands to vector memory access instructions be naturally aligned in memory. Longwords must be aligned on longword boundaries; quadwords must be aligned on quadword boundaries. This message indicates an exception condition and is followed by a register and stack dump to help locate the error. The reason mask is a longword whose lowest three bits, if set, indicate that the instruction caused a length violation (bit 0), referenced the process page table (bit 1), attempted a read/modify operation (bit 2), was a vector operation on an improperly-aligned vector element (bit 3, always set), or was a vector instruction reference to an I/O space address (bit 4). User Action: Examine the PC and virtual address displayed in the message. The virtual address is an address in the same page as that address to which the access was attempted. Check the program listing to verify that the vector operands to vector memory instructions are naturally aligned.
VECCTXERR
error encountered during vector context testing Facility: UETP, User Environment Test Package Explanation: The vector processor device test encountered an error initiating vector context testing. This error is received in relation to a previously displayed error condition or might be due to a vector hardware problem. User Action: If the condition causing the problem can be identified, correct the condition and rerun the test. If the error persists, submit a Software Performance Report. If no condition can be identified, run diagnostics for VAX vectors or contact the Digital Services Group.
VECDIS
vector disabled fault, code=xx, PC = location, PSL = xxxxxxx
Facility: SYSTEM, VMS System Services
Explanation: The current process has issued a vector instruction
which requires that an idle vector processor become active. Under
normal circumstances, this event is not reported to a system user.
However, if the vector processor was originally disabled due to
some error involving the current process, the VECDIS message is
issued in association with one of the following messages:
o BADCONTEXT-The vector state of the mainline routine is corrupt
and cannot be restored.
o CPUNOTACT-The VAX system contains no vector-present processor
on which to schedule the current process.
o EXQUOTA-The VMS operating system cannot allocate sufficient
space to save the vector state of the mainline routine because
the process in which the routine is executing has exceeded
process paging file quota.
o INSFMEM-Insufficient nonpaged dynamic memory exists to turn the
current process into a vector consumer.
o INSFWSL-The VMS operating system cannot allocate sufficient
space to save the vector state of the mainline routine because
the working set limit of the process in which the routine is
executing is too low.
o MCHECK-The vector processor has been disabled due to the
detection of a hardware errort.
o NOPRIV-An ACL on the vector capability has denied a user mode
program access to the vector processor.
o VASFUL-The VMS operating system cannot allocate sufficient
space to save the vector state of the mainline routine because
the address space (P0 space) of the process in which the
routine is executing is full.
User Action: See the description of the associated status code for
additional information on the error.
VECEMULTR
testing to be performed on vector emulator Facility: UETP, User Environment Test Package Explanation: No vector processors were found on the system but the vector emulator facility was found to be installed. Testing will be conducted on the vector emulation facility. User Action: None.
VEC_FLOOVEMAT
floating overflow in the vector math library Facility: MTH, Mathematics Facility Explanation: At least one overflow condition occurred during the execution of a vectorized math routine. This message results from an incorrect call to the math library and usually indicates that an argument is too small or too large. The result returned is a reserved operand, minus zero. User Action: Locate where the program has used arguments that are out of range for the math routine in question.
VEC_FLOUNDMAT
floating underflow in the vector math library Facility: MTH, Mathematics Facility Explanation: At least one underflow condition was detected during the execution of a vectorized math procedure and the caller enabled for floating underflow traps. This message results from an incorrect call to the vectorized math library. Refer to the discussion of the LIB$FLT_UNDER procedure in the VMS Run-Time Library Routines Volume. The result returned is zero. User Action: Locate where the program has used arguments that are out of range for the math routine in question.
VECFULL
privileged vector limit of 42 exceeded Facility: SYSTEM, VMS System Services Explanation: This severe error message is associated with a status code returned from a system service request. The privileged vector limit of 42 is exceeded. User Action: Remove unnecessary vectors and relink.
VECINUSE
vector in use Facility: SYSGEN, System Generation Utility Explanation: The interrupt vector address that is specified in a SYSGEN command CONNECT is being used by another device. User Action: Change the vector address in the device driver and reenter the SYSGEN command CONNECT.
VEC_INVARGMAT
invalid vector argument to math library Facility: MTH, Mathematics Facility Explanation: One of the vector math procedures is called with an invalid argument. The result returned is a reserved operand, minus zero. User Action: Locate the vectorized math procedure call that caused the error and correct the argument.
VEC_LOGZERNEG
vectorized logarithm of zero or negative value Facility: MTH, Mathematics Facility Explanation: The vectorized LOG or DLOG math procedure is called with at least one zero or negative value. The result returned is a reserved operand, minus zero. User Action: Locate the call(s) to the vectorized procedure that caused the error(s), and correct the zero or negative argument(s).
VEC_SQUROONEG
vectorized square root of negative value(s) Facility: MTH, Mathematics Facility Explanation: A vectorized math procedure is called to evaluate the square root of at least one negative number. The result returned is a reserved operand, minus zero. User Action: Locate the call to the library procedure that returned the error. Correct the program so that all arguments are nonnegative.
VECTOR
testing to be performed on xxx vector processors Facility: UETP, User Environment Test Package Explanation: The vector processor device test detected the presence of xxx vector processors installed and enabled on the host system User Action: None.
VEC_UNDEXP
undefined vector exponentiation Facility: MTH, Mathematics Facility Explanation: An expression contained at least one vector exponentiation that cannot be mathematically evaluated, for example, 0**0. The result returned is a reserved operand, minus zero. User Action: Locate the error in your vectorized program and correct the expression.
VER
error in version number Facility: RMS, VMS Record Management Services Explanation: The version number specified in a file specification contains invalid syntax, for example, nonnumeric characters or a value larger than 32,767. User Action: Correct the syntax of the file specification. Reenter the command or correct the program, as necessary.
VERBNOTFND
verb 'verb-name' not found in command tables Facility: CDU, Command Definition Utility Explanation: The verb you tried to delete is not defined in the CLD file. User Action: Ensure that the syntax is correct and try to delete the .CLD file again.
VERIFYERR
verification error for block 'n' of 'filespec' Facility: BACKUP, Backup Utility Explanation: During a compare or verify operation, the data in the specified block of the specified file did not agree with the input file. If other file activity is occurring on the volume, the error may result because another user modified the file during the backup procedure. User Action: Note that the copies are inconsistent.
VERS_MISMATCH
version mismatch for log file format - operation aborted Facility: LMCP, Log Manager Control Program Explanation: The log header version is different from the one coded in LMCP. User Action: Check the definition of SYS$JOURNAL. If it is correct, submit a Software Performance Report (SPR) describing the conditions leading to the error and include a BACKUP save set containing the output of the DCL DUMP command for the log file.
VETOED
participant vetoed commitment Facility: DDTM, DECdtm Transaction Manager Explanation: The transaction aborted because a resource manager could not commit the transaction. User Action: Determine why the resource manager could not commit the transaction and correct the error.
VFC
record too short to fill fixed part of VFC record Facility: CONVERT, Convert Utility Explanation: There are fewer bytes in the input record than are required for the fixed portion of the VFC output record. User Action: Either make the fixed control portion of the output record smaller, or do not use the /FIXED_CONTROL option. Virtual Circuit Timeout Facility: VAXport, VAXport Driver Explanation: The VAXport driver closes the virtual circuit that the local CI port opened to the remote port. This closure occurs if the remote node is running CI Microcode Version 7 or higher, and the remote node failed to respond to any messages sent by the local node. User Action: This error is normal if the remote system halted, crashed, or is shut down. This error may mean the local node's PASTIMOUT SYSGEN parameter is set too low, especially if the remote node is running privileged user-written software. VMB-F-Bootfile not contiguous Facility: VMB, Virtual Memory Boot Explanation: The file [SYSEXE]SYSBOOT.EXE is located but is not contiguous. User Action: The disk you are attempting to bootstrap cannot be bootstrapped. Obtain another copy of the system disk. VMB-F-Failed to initialize device Facility: VMB, Virtual Memory Boot Explanation: Encountered an error in the load path while VMS was trying to initialize the boot device. User Action: Try initializing again. If this fails, call Field Service. VMB-F-I/O error reading boot file Facility: VMB, Virtual Memory Boot Explanation: An uncorrectable read error occurred while the file [SYSEXE]SYSBOOT.EXE was being read. User Action: Try rebooting the disk. If subsequent attempts fail, obtain another copy of the system disk. VMB-F-Nonexistent drive Facility: VMB, Virtual Memory Boot Explanation: The specified drive number does not exist. User Action: Specify an appropriate device unit to the console program, or use a different console bootstrap command procedure. VMB-F-Unable to locate BOOT file Facility: VMB, Virtual Memory Boot Explanation: The file [SYSEXE]SYSBOOT.EXE could not be found. User Action: You are attempting to bootstrap a volume that does not contain a VMS binary system. Attempt to reboot using an appropriate disk volume. VMB-F-Unexpected exception Facility: VMB, Virtual Memory Boot Explanation: An unexpected exception occurred while the primary bootstrap (VMB.EXE) was being executed. This condition probably indicates a corrupted SYSBOOT.EXE file or a hardware failure. User Action: Determine the source of the error, and either obtain a new copy of the system disk or call the Digital Services Group. VMB-F-Unexpected machine check Facility: VMB, Virtual Memory Boot Explanation: An unexpected machine check occurred while the primary bootstrap (VMB.EXE) was being executed. This condition probably indicates a corrupted SYSBOOT.EXE file or a hardware failure. User Action: Determine the source of the error, and either obtain a new copy of the system disk or call the Digital Services Group.
VOIALREXI
voice-ID already exists for this device Facility: DTK, DECtalk Facility Explanation: A user tried to create a new voice identifier for a DECtalk device when one already exists. This is normal in a modular environment. The existing voice identifier is returned. User Action: None. Make sure you do not delete a voice identifier that you did not create.
VOLALRMNT
another volume of same label already mounted Facility: MOUNT, Mount Utility Explanation: Shared, group, and system volumes that are mounted concurrently must have unique volume labels. The request to mount a volume that has the same label as a volume already mounted failed. User Action: Mount the volume as a private volume, if it does not have to be shared; or wait until the conflicting volume has been dismounted. You can determine the status and ownership of the conflicting volume with the DCL command SHOW DEVICES/FULL/MOUNTED.
VOLIDENT
label = 'volume-label', owner = 'user-name', format = 'volume- format' Facility: MOUNT, Mount Utility Explanation: This informational message identifies an incorrectly specified volume after the INCVOLLABEL and NOHOMEBLK errors in a MOUNT request. User Action: None. If the volume protection allows access to the volume, reenter the DCL command MOUNT.
VOLINSET
'device-name' is already part of a volume set Facility: BACKUP, Backup Utility Explanation: The specified volume is already bound to a volume set. The volume cannot be used as a save set disk. User Action: Retry the operation using a properly initialized Files-11 Structure Level 2 volume.
VOLINSET
volume is already part of another volume set Facility: MOUNT, Mount Utility Explanation: The volume specified in the DCL command MOUNT/BIND is part of another volume set. User Action: Check the device name specified. Either use another volume or initialize this one.
VOLINV
volume is not software enabled Facility: SYSTEM, VMS System Services Explanation: The volume valid bit is not set for the volume. All physical and logical I/O operations will be rejected until the bit is set. User Action: Check for a programming error. Verify that the volume is mounted and loaded. Check to see that the power is on before retrying the program.
VOLMOUNT
the volume 'volume-name' is already mounted Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility ignored a MOUNT command because the volume is already mounted. User Action: None.
VOLNAME
volume 'volume-name' in Facility: MOUNT, Mount Utility Explanation: This message is optionally issued with the MOUNTDEV message. It includes the volume name of the volume being mounted. User Action: None.
VOLOERR
must override owner identifier field in VOL1 label on 'device-name' Facility: MOUNT, Mount Utility Explanation: The owner identifier field of the VOL1 label must be overridden to allow access to the tape. The OWNER_ID option of the MOUNT/OVERRIDE command is used to interchange magnetic tapes between VMS and other Digital operating systems. User Action: Reenter the MOUNT command and include the /OVERRIDE=OWNER_ID option.
VOLSETSTS
change of status for volume set 'volume-set-name' Facility: MOUNT, Mount Utility Explanation: MOUNT encountered a condition that resulted in a change of state for the specified volume set. Accompanying messages describe the nature of the change. User Action: Take corrective action based on the accompanying messages.
VOLSHDWMEM
mounting a shadow set member volume; volume write locked Facility: MOUNT, Mount Utility Explanation: This informational message indicates that the volume being mounted is a former shadow set member. To prevent accidental destruction of data, this volume is being mounted write-locked. User Action: To allow write access to this volume, dismount the volume and remount it with the /OVERRIDE=SHADOW_MEMBERSHIP qualifier.
VOLSTATUS
change of status for volume 'volume-name' Facility: MOUNT, Mount Utility Explanation: MOUNT encountered a condition that resulted in a change of state for the specified volume. Accompanying messages describe the nature of the change. User Action: Take corrective action based on the accompanying messages.
VOLUME_FULL
volume is full (insufficient space for the request) Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility is unable to copy a file because the volume had insufficient space. User Action: RT-11 only supports contiguous files, therefore there must be a free space on the volume as large as the file you are trying to copy. Use the DIRECTORY /ALL command to see where the unused areas on the volume are. By deleting unneeded files which are adjacent to unused areas it, might be possible to create a large enough space. Also, if you use the COPY command to copy a file to the same volume, you can move files around and make larger free areas.
WACKQEMPTY
NETACP - ack wait queue empty Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WAITERR
error waiting for RMS operation to complete Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while waiting for RMS. User Action: This is only possible if EXCHANGE is interrupted by a Ctrl/Y. Repeat the command and let it complete without interruption.
WAITIDLEBCB
attempted wait on idle buffer Facility: BACKUP, Backup Utility Explanation: A software error occurred in the Backup Utility. User Action: Submit a Software Performance Report (SPR).
WANTOSEND
do you want to send anyway (Y/N, default is N)? Facility: MAIL, Mail Utility Explanation: One or more of the addresses were unavailable. User Action: Type Y if you want to send your message to the available addresses.
WARNING
parsed with warnings Facility: FDL, Create/FDL Utility Explanation: This message accompanies the other warning-level messages. User Action: The FDL file parsed successfully; you may either correct the cause of the warning or continue.
WARNISUE
completed with warnings Facility: LINK, Linker Utility Explanation: The link completed, but warnings were issued. User Action: None.
WASECC
successful transfer; no data check Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned by I/O functions. A data check operation is not performed. The function is a read operation that is completed successfully by applying one or more ECC corrections. The specified data check, however, is not performed. User Action: Note the condition. Modify the source program, if necessary, to detect and respond to the condition.
WBE
error on write behind Facility: RMS, VMS Record Management Services Explanation: An error occurred during a VMS RMS operation for which write behind is specified. User Action: The status value (STV) field of the RAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
WCBFCBMNG
WCB/FCB correspondence broken Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WCC
invalid wildcard context (WCC) value Facility: RMS, VMS Record Management Services Explanation: The wildcard context value in the NAM block (an input file-processing option) contains an invalid value. User Action: Verify that the call to the VMS RMS service is coded correctly and that the NAM block is not inadvertently modified between VMS RMS service calls.
WCSCORR
WCS error correction failed Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WDW_MAXPREV
too many previous records in window Facility: SEARCH, SEARCH Command Explanation: SEARCH could not create enough buffer space to hold all the records in a window. Only records before the match are significant; SEARCH does not need to store records that follow the match. User Action: Specify a smaller window, or ask your system manager to have your paging file quota increased.
WDW_MAXPRM
too many window parameters Facility: SEARCH, SEARCH Command Explanation: The /WINDOW parameter is not specified correctly. User Action: Reenter the command using the correct syntax.
WER
file write error Facility: RMS, VMS Record Management Services Explanation: An error occurred during a VMS RMS write operation. User Action: The status value (STV) field of the RAB contains a system status code that provides more information about the condition. Take corrective action based on this status code.
WFR
.RESTORE not in same file as .SAVE/.SAVEALL: "additional locational information" Facility: RUNOFF, DIGITAL Standard Runoff Explanation: You cannot issue a .RESTORE directive for a .SAVE directive from within a require file if that .SAVE directive occurred in a higher level file or another require file. User Action: Change the order of directives so that the .REQUIRE directive is issued between the .SAVE and .RESTORE directives.
WIDMISMATCH
parameter 'numbers' class, 'class', unsupported Facility: VAXTPU, VAX Text Processing Utility Explanation: The wrong type of widget has been passed to a VAXTPU built-in procedure. Usually, the procedure can only accept a simple text widget. User Action: Correct your code and try again.
WILDCONCAT
wildcard specification cannot be concatenated Facility: Shared by several facilities Explanation: A number of files to be concatenated cannot be specified with wild cards. User Action: Respecify the files without using wildcards.
WILDOVTVER
wildcard version required for output file Facility: Shared by several facilities Explanation: A wildcard version must be specified on an output file. User Action: Correct the command specifying the wildcard version.
WILUSERMS
output will be performed by RMS later Facility: SMG, Screen Management Facility Explanation: Normally, the screen is updated at the end of every output operation. If, however, the 'device-name' is actually a file or an unknown terminal, then this message is given at the time output would have been sent to the screen. User Action: Use the SMG$SNAPSHOT routine to receive your output.
WINDNOTMAPPED
the window is not mapped to a buffer Facility: VAXTPU, VAX Text Processing Utility Explanation: You attempted to manipulate a window that is not on the screen. User Action: Use the built-in procedure MAP to associate the window with a buffer on the screen.
WINDNOTVIS
built-in procedure cannot operate on an invisible window Facility: VAXTPU, VAX Text Processing Utility Explanation: The built-in procedure that you are attempting to use (for example, POSITION) can only use visible windows. The window that you used as an argument is not visible because it is occluded by other windows. User Action: Remap the window to the screen to make it visible again.
WINEXISTS
a viewport has already been associated with the display
Facility: SMG, Screen Management Facility
Explanation: A viewport exists. That is, a viewport has already
been associated with the virtual display.
User Action: Follow these steps:
1. Use the viewport that is already associated with the virtual
display.
2. Delete the existing viewport before you create the new
viewport.
3. Use other viewport routines to change or move the existing
viewport.
WINK
a wink is detected on the phone line Facility: DTK, DECtalk Facility Explanation: A wink (a possible timeout) is detected on the phone line. The caller may have hung up the phone. User Action: None.
WINTRUNCFIT
viewport truncated to fit Facility: SMG, Screen Management Facility Explanation: The viewport specification will not completely fit within the virtual display. The viewport is truncated to fit within the virtual display. User Action: None.
WKQERR
work queue management routine error Facility: EVL, Event Logger Explanation: One of the work queue management routines returned an error. This indicates a software error or a VMS system configuration problem. User Action: Check the maximum virtual memory allowed for the process and the timer element quota. There should be one timer element for each sink node in use, plus two.
WLD
invalid wildcard operation Facility: RMS, VMS Record Management Services Explanation: A call to one of the VMS RMS services $CREATE, $ERASE, $ENTER, $OPEN, and $RENAME specified a wildcard in one or more components of a file specification. No wildcards are allowed in these services. User Action: Correct the source program. Verify that the call to VMS RMS is coded correctly. To perform a wildcard file delete service, you must code a loop that searches for files based on wildcard specifications and deletes the files individually.
WLDNOTALWD
wildcard user specs not allowed Facility: AUTHORIZE, Authorize Utility Explanation: Wildcard characters are not allowed in the user specification for the command you are using. User Action: Reenter your command without using wildcard characters.
WLK
device currently write locked Facility: RMS, VMS Record Management Services Explanation: The hardware device specified for a VMS RMS operation is write-locked for protection, and write-access is attempted. User Action: Verify the status of the hardware device; reset the write-lock switch, if necessary. Notify the system operator if the error cannot be corrected. Work file failed to close Facility: EDT, EDT Editor Explanation: EDT is unable to close its work file. User Action: After determining the reason why EDT cannot close its work file, correct the problem. Work file failed to open Facility: EDT, EDT Editor Explanation: EDT is unable to open its work file. User Action: After determining the reason why EDT cannot open its work file, correct the problem. Work file overflow Facility: EDT, EDT Editor Explanation: You exceeded EDT's limit on the size of its work file. The limit is 65,535 blocks. User Action: Use the CLEAR command to delete a buffer when it is no longer needed. This precaution will also help to reduce the size of the work file on systems with small disks.
WORK_DEV
work file 'filespec' must be on random access local device Facility: SORT, Sort/Merge Utility Explanation: Work files must be specified for random access devices that are local to the CPU on which the sort is being performed (that is, not on node in a network). Random access devices are disk devices. User Action: Specify the correct device. Working Facility: EDT, EDT Editor Explanation: This message is displayed when the command operation requires more than a minimum amount of time to complete. EDT is responding to your command. User Action: None.
WORKING
customer defined text Facility: LAVC, Local Area VAXcluster Explanation: The local area VAXcluster network failure analysis has determined that this network component is working. User Action: If the network component is indeed working, no user action is required. However, if this message displays when the network component is not working, have the system manager or network manager look into the network problem. In such a case, the network description does not accurately represent the physical network. Review the defined network components by calling SYS$LAVC_DEFINE_NET_COMPONENT. Review the defined network path descriptions by calling SYS$LAVC_ DEFINE_NET_PATH. Correct any problems as necessary.
WPL
error detected while writing prolog Facility: RMS, VMS Record Management Services Explanation: An I/O error occurred while VMS RMS is writing a file's prolog area. User Action: Depending on the operation, the status value (STV) field in the FAB or RAB contains a system status code that provides additional information about the condition. Take corrective action based on this status code.
WRIRSPMSG
error writing system service response message Facility: JBC, Job Controller Explanation: The job controller encountered an error responding to a $GETQUI, $SNDACC, $SNDJBC, or $SNDSMB system service. The accompanying message provides additional information. User Action: Take action based on the accompanying message.
WRISMBMBX
error writing symbiont mailbox Facility: JBC, Job Controller Explanation: The job controller encountered an error communicating with a symbiont process. The accompanying message provides additional information. User Action: Take action based on the accompanying message. Write file could not be closed Facility: EDT, EDT Editor Explanation: EDT opened the output file and copied the text specified with the WRITE command into that file. However, for some reason at the system level, EDT cannot close that file. User Action: Correct the problem indicated by the accompanying message. Write file could not be created Facility: EDT, EDT Editor Explanation: EDT could not create the output file with the file specification you supplied with the WRITE command. This error can be caused by problems in the file name itself (either it has too many characters or an invalid character). Other causes include problems in the directory specification, if you used one (either the directory does not exist, you do not have access to it, or the directory specification format is incorrect). This message could also mean that there is a problem with the file system, such as insufficient disk space. User Action: After determining the cause of the problem, correct it.
WRITEACT
ACTIVE system parameters modified by process ID 'pid' Facility: SYSGEN, System Generation Utility Explanation: This message is written to the operator's console when a WRITE ACTIVE operation is done from SYSGEN. This message is a monitoring aid for the system manager. User Action: None.
WRITEATTR
error writing attributes for 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to write the file attributes of the specified file. The accompanying message provides additional information. User Action: Correct the condition that caused the error and reenter the command.
WRITEBACK
error writing backup date for 'device-name' file ID ('file-id')
Facility: BACKUP, Backup Utility
Explanation: The Backup Utility encountered an error during an
attempt to update the backup date of the specified file. The
accompanying message provides additional information. If other
file activity is occurring on the volume, the error is probably
caused because another user deleted the file during the backup
procedure.
User Action: If necessary, correct the condition that caused the
error and reenter the command.
WRITEBLOCK
error writing block 'n' of 'filespec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered an error during an attempt to write the specified block of the specified file. The accompanying message provides additional information. User Action: Examine the file for corruption; reconstruct the file as necessary.
WRITEBOOT
error writing boot block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: The Analyze/Disk_Structure Utility encountered an error during an attempt to write a dummy bootstrap block to virtual block 1 of the index file [000000]INDEXF.SYS;1 on the specified relative volume. The accompanying message provides additional information. User Action: The specified volume probably cannot be used as a system volume for a VAX-11 processor model that requires access to the bootstrap block during a bootstrap operation.
WRITECHECK
write error detected during check on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility received an error while checking a write operation. User Action: The media has bad areas and should probably be discarded or reformatted.
WRITECHECKREC
write check error recovered on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while checking a write on the volume, but the operation succeeded on a retry. User Action: The file is written successfully, but the user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent.
WRITECUR
CURRENT system parameters modified by process ID 'pid' into file 'filespec' Facility: SYSGEN, System Generation Utility Explanation: This message is written to the operator's console when a WRITE CURRENT operation is done from SYSGEN. This message is a monitoring aid for the system manager. User Action: None.
WRITE_ERR
error writing 'filespec' Facility: CONVERT, Convert Utility and CONVERT, Convert/Reclaim Utility Explanation: This message will be accompanied by an RMS error message that explains the error. User Action: Correct the error described in the RMS error message and try again.
WRITEERR
error while writing output Facility: ACCOUNTING, Accounting Utility Explanation: During a VMS RMS operation, an error is encountered while writing a file. Filespec is the file specification of the file being written. User Action: Determine that the file is open and that you have write privilege. If the error is reproducible, notify your system manager.
WRITEERR
error writing 'filespec' Facility: Shared by several facilities Explanation: During a VMS RMS operation, an error is encountered while writing a file. If this error occurred during a macro assembly operation, the assembler encountered an I/O error when writing to the output object module or listing file; 'filespec' is the file specification of the file being written. User Action: Determine that the file is open and that you have write privilege. If this is a macro assembly error, retry the assembly. If the error is reproducible, notify your system manager.
WRITEERR
error writing 'filespec' Facility: SET, SET Facility Explanation: A problem has occurred while writing to a file or a directory. User Action: Take corrective action based on the accompanying message.
WRITEERR
error writing 'filespec' Facility: VAXTPU, VAX Text Processing Utility Explanation: The output file cannot be written. An accompanying VMS RMS message should indicate the reason for the error. User Action: Follow the recovery procedure for the accompanying RMS message.
WRITEERR
error writing library Facility: LBR, Librarian Subroutine Package Explanation: An error occurred while writing the cached disk blocks of the library file. User Action: If the resulting library file is corrupt, submit a Software Performance Report (SPR).
WRITEERRREC
write error recovered on volume 'volume-name' Facility: EXCHANGE, Exchange Utility Explanation: The Exchange Utility encountered an error while writing the volume, but the operation succeeded on a retry. User Action: The file is written successfully, but the user should watch the volume for further signs of deterioration. Discard or reformat the volume if errors are frequent.
WRITEFILE
error writing event file 'file-id' Facility: EVL, Event Logger Explanation: An error occurred while writing an event record to a file. All events destined for that sink will be discarded. This message displays the file name. User Action: Take corrective action based on the accompanying message.
WRITEHEADER
file ('file-id') 'filename' file header write error
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: An error was encountered during an attempt to write
the specified file header to the index file, [000000]INDEXF.SYS;1,
on the specified relative volume. The accompanying message
provides additional information.
User Action: If the specified file header is currently in use, the
file can no longer be accessed by the operating system. It must be
deleted and reconstructed from backup media. If the file header is
not in use, no action is necessary because the operating system
will not attempt to use the file header.
WRITEHOME
error writing home block, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to write the home block to the specified virtual block of the index file, [000000]INDEXF.SYS;1, on the specified relative volume. The accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system using one of the alternate home blocks, but the user should consider copying the volume to fresh media.
WRITEIBMAP
error writing index file bitmap, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to write the index file bit map to the specified virtual block of the index file, [000000]INDEXF.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system, but you should copy the volume to fresh media or reconstruct the volume from backup media.
WRITEJNLACE
error writing journal ACE for 'filespec' file ID 'file-id' Facility: BACKUP, Backup Utility Explanation: BACKUP could not write out the journal Access Control Entry for the specified file. User Action: Determine why the ACL could not be written. This could be due to a corrupted ACL or some other hardware or software related error. Correct the problem if possible and retry the BACKUP operation.
WRITELOCK
volume is write locked Facility: MOUNT, Mount Utility Explanation: This informational message indicates that the DCL command MOUNT found the volume to be write-locked. User Action: None, unless you wish to write on the volume. In that case, you must write-enable the drive, and dismount and mount the volume.
WRITEMON
error writing event to monitor process 'sink-name' Facility: EVL, Event Logger Explanation: An error occurred while writing an event record to a monitor program. The link will be reestablished to the monitor process. This message displays the name of the monitor program. User Action: Take corrective action based on the accompanying message.
WRITENABLE
write enable volume 'n' on 'device-name' Facility: BACKUP, Backup Utility Explanation: The Backup Utility requires that the specified volume of an output save set be write-enabled. User Action: Note that the Backup Utility will write on the volume, ensure that a suitable volume has been mounted, and write- enable the volume. If the utility is executing as an interactive job, reply "YES" to the prompt on SYS$COMMAND. If the utility is executing as a batch job, use the DCL command REPLY to signal completion.
WRITERRS
excessive error rate writing 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility encountered numerous write errors in the specified save set. The save set medium is probably unusable. User Action: Retire the save set medium.
WRITESBMAP
error writing storage bitmap, VBN 'n', RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to write the storage bit map to the specified virtual block of the storage bit map file, [000000]BITMAP.SYS;1, on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system, but you should copy the volume to fresh media or reconstruct the volume from backup media.
WRITESCB
error writing storage control block, RVN 'n' Facility: ANALDISK, Analyze/Disk_Structure Utility Explanation: An error was encountered during an attempt to write the storage control block to virtual block 1 of the storage bit map file, [000000]BITMAP.SYS;1 on the specified relative volume. An accompanying message provides additional information. User Action: The volume probably can be mounted by the operating system, but the user should copy the volume to fresh media or reconstruct the volume from backup media.
WRITESCB
write error on storage control block; volume is write locked Facility: MOUNT, Mount Utility Explanation: An I/O error occurred while the volume is being mounted; the volume has been write-locked to protect its integrity. User Action: Check the hardware and retry the program.
WRITLCK
volume on 'device-name' is write locked write lock error Facility: SYSTEM, VMS System Services Explanation: The volume cannot be written because the hardware write-lock switch is set on the drive or the device is software write-locked. User Action: Release the write-lock switch and retry the program.
WRNERS
compilation warnings in module 'module-name' file 'filename' Facility: LINK, Linker Utility Explanation: The specified module has compilation warnings. User Action: Correct the module and relink.
WRONGACMODE
operation attempted from insufficiently privileged access mode Facility: SYSTEM, VMS System Services Explanation: The process had insufficient privileges to execute the requested operations. This is an error in the user program. User Action: Correct the error in the program.
WRONGACP
wrong ACP for device Facility: SYSTEM, VMS System Services Explanation: This message is associated with a status code returned from the IO$_MOUNT ACP QIO function. The ACP specified is the wrong one for the file structure being mounted. User Action: Check the ACP specified in the DCL command MOUNT /PROCESSOR; verify what structure you are trying to mount.
WRONGDATASET
records could not be found in the data set Facility: VAXTPU, VAX Text Processing Utility Explanation: An internal error occurred in the VAXTPU software. User Action: Submit a Software Performance Report (SPR).
WRONGMUTEX
wrong mutex specified in condition wait Facility: CMA, DECthreads (Multithreading Run-Time Library) Explanation: A thread attempted to wait for a condition variable that already has at least one thread waiting, and that thread has specified a different mutex. DECthreads requires that all threads concurrently waiting for a condition variable specify the same mutex. User Action: Design your code so that each condition variable represents a particular state of shared data that is protected by a given mutex.
WRONGOWNER
file ('file-id') 'filename' inconsistent extension file header owner
UIC
Facility: ANALDISK, Analyze/Disk_Structure Utility
Explanation: The file owner UIC recorded in an extension file
header for the specified file does not agree with the UIC recorded
in the primary header.
User Action: None. The utility corrects the extension file header.
WRONGSTATE
invalid transaction state for requested event Facility: SYSTEM, VMS System Services Explanation: The transaction is in the wrong state for the attempted operation. User Action: If this message is returned by the $ABORT_TRANS or $END_TRANS service, correct the error in the program. Otherwise, submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the output of the LMCP DUMP command for the local transaction log file and the output of the DCL DUMP command for the same log file.
WRONGVOL
'date and time', Device 'device-name' contains the wrong volume. Mount verification in progress Facility: OPCOM, Operator Communication Process Explanation: The volume in the drive is not the original volume. User Action: Replace the original volume in the drive and cancel the mount verification.
WRONGVOL
device 'device-name' contains the wrong volume Facility: MOUNT, Mount Utility Explanation: The specified volume does not match the volume in the drive. User Action: Correct the volume name and retry the operation.
WRONGVOL
'save-set-spec' is not the next volume in the set Facility: BACKUP, Backup Utility Explanation: The volume mounted as a continuation volume of a multivolume save set is not the successor of the previous volume of the save set. Volumes must be processed in the order of their creation. User Action: Locate and mount the correct continuation volume.
WRONUMARG
wrong number of arguments Facility: DTK, DECtalk Facility Explanation: A DTK$ routine is called with too many or too few arguments. User Action: Change the code to call the routine with the correct number of arguments.
WRONUMARG
wrong number of arguments Facility: PPL, Parallel Processing Facility Explanation: Too many or too few arguments are specified in the call. User Action: Recode the program using the correct number of arguments.
WRONUMARG
wrong number of arguments Facility: Shared by several facilities Explanation: An STR$ routine is called with an incorrect number of arguments. User Action: Check the argument list in the call. High-level language programmers who have not issued a call directly to an STR$ routine should submit a Software Performance Report with supporting documentation, including the system traceback listing.
WRONUMARG
wrong number of arguments Facility: SMG, Screen Management Facility Explanation: An SMG routine is called with less than the number of required arguments or too many arguments. User Action: Correct the code to call the routine with the proper number of arguments.
WRONUMARG
wrong number of arguments Facility: STR, String Manipulation Facility Explanation: A String Facility entry is called with an incorrect number of arguments. User Action: A user who calls the String Facility directly should check the argument list in the call. High-level language programmers who have not issued a call directly to a String Facility routine should submit a Software Performance Report with supporting documentation, including the system traceback listing.
WRTEVT
error writing events to sink node receiver Facility: EVL, Event Logger Explanation: An error occurred while writing information over a logical link to an event receiver. The link will be reopened and the operation will be retried. This error may be due to a VMS system or network configuration problem. User Action: Take corrective action based on the accompanying message.
WRTFIL
updating image file 'filespec' Facility: PATCH, Patch Utility Explanation: The specified image file is updated to include the previous patch. User Action: None.
WRTHOMBLK
I/O error writing home block Facility: MOUNT, Mount Utility Explanation: An I/O error occurred writing the home block of a volume during the MOUNT/BIND operation. User Action: Check that the hardware is functioning properly. Reinitialize the disks and retry the operation.
WRTINVBUF
ACP attempted to write an invalid buffer Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WRTINVHDR
ACP attempted to write an invalid file header Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WRTPGSBAK
write pages back - inconsistent database Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.) WS default and quota raised to PHD +MINWSCNT Facility: SYSBOOT, System Bootstrap Facility Explanation: The default size of the working set has been increased to equal the sum of the working set count (which is the count of fluid working set pages), plus the process header. User Action: None.
WSLENOVAL
working set list entry not valid Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WSLPAGCNT
working set list page count error Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WSLVANVAL
working set list virtual adr has nonvalid PTE Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WSLXVANMAT
working set list entry does not match VA Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
WSSIZEERR
working set size less than pages in use Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
XAB
invalid XAB or XAB not accessible at location Facility: RMS, VMS Record Management Services Explanation: The XAB specified in the XAB field of the FAB, or in the NXT field of another XAB, pointed to an XAB that either is not writable by the caller or contains an invalid block length field. User Action: The status value (STV) field of the FAB provides the address of the XAB in error. Verify that the call to the VMS RMS service is coded correctly.
XNF
required XAB not found Facility: RMS, VMS Record Management Services Explanation: A VMS RMS request required an XAB which is not specified. For example, the ROP option, ETO is specified, but no EABTRM is supplied. User Action: Verify that the call to the VMS RMS service is coded correctly.
XORERRS
'n' errors recovered by redundancy group in 'save-set-spec' Facility: BACKUP, Backup Utility Explanation: The Backup Utility successfully recovered from uncorrectable read errors in the specified save set the specified number of times by using the redundancy information. User Action: None. However, if the number of errors appears excessive, consider retiring the save set medium at a convenient time.
XQPERR
Error detected by file system XQP Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
YES
yes Facility: VAXTPU, VAX Text Processing Utility Explanation: Prototype affirmative response. User Action: None.
YESNO
please enter YES or NO. Facility: VMSINSTAL, Install Procedures Explanation: VMSINSTAL asked a question that must be answered YES or NO. User Action: Answer the question again, specifying YES or NO. You can abbreviate these answers as Y or N, respectively.
ZEROLEN
zero length record encountered, entry 'n' skipped Facility: ERF, Error Log Utility Explanation: A null entry was encountered. User Action: Submit a Software Performance Report (SPR).
ZEROLINK
zeroed counters for link 'link-name' Facility: LAT, LAT Facility Explanation: LATCP has reset the counters for the specified link to zero. User Action: None.
ZERONODE
zeroed counters for node 'node-name' Facility: LAT, LAT Facility Explanation: LATCP has reset the counters for the specified node to zero. User Action: None.
ZEROPAGE
Zero page table entry from swap map Facility: BUGCHECK, System Bugcheck Explanation: The VMS software detected an irrecoverable, inconsistent condition. After all of physical memory is written to a system dump file, the system will automatically reboot if the BUGREBOOT system parameter is set to 1. User Action: Submit a Software Performance Report (SPR) that describes the conditions leading to the error. Include a BACKUP save set containing the system dump file and the error log file active at the time of the error. (Use the /IGNORE=NOBACKUP qualifier with the BACKUP command that produces the save set included with the SPR.)
ZEROSERVICE
zeroed counters for service 'service-name' Facility: LAT, LAT Facility Explanation: LATCP has reset the counters for the specified service to zero. User Action: None.