English French Notes Complete/Exclude is not the same **** VALUE IS GREATER THAN 255 CHARACTERS (SEE SUBNODES FOR DATA) *** %ZTER caused an error: %DSM-E-ET, Error occurred in %ZTER, GLOBAL SEARCH Global reference: Non-existing global. Bad Routine Bad Date/Time Bad Option No Description (%ZTLOAD) Restricted Device QUEUE INFORMATION MISSING - NOT QUEUED Queueing not allowed to device -- NOT QUEUED Sorry--that time is restricted! Output is never allowed from this option! No Description (REQ~%ZTLOAD) Inactive: Interrupted Taskman Waiting Logons Inhibited No Signons Allowed Required link to is down. Waiting to balance the load. Main Loop Taskman Job Limit Reached Placed on JOB List Placed on C List Startup Interrupted While Running Startup Hang TM-DELAY Startup jobs Restart Setup The following required ^%ZOSF nodes are undefined: Taskman is the wrong type in taskman site parameters. Inspected INVALID OUTPUT DEVICE Task's volume set not listed in index. Task's volume set not listed in file. Task's volume set can't accept tasks. Task's volume set has no link access. Task has no destination UCI listed. Task's UCI does not exist here. Task's entry routine does not exist here. Task's destination UCI failed check. Put On The IO List Your task # rejected because: XQA* Too many hops Ready to Move as task number BAD DESTINATION UCI Link Wait NO LINK ACCESS TO VOLUME SET Stopped while waiting for Link Link Error Caused by the manager. is the wrong type of volume set for TaskMan. ZTLEFT= Taskman NOT Started Don't start TaskMan with the SHARE privilege access not authorized You lack the system privilege to start TaskMan. duplicate name The following error has prevented TaskMan from starting: TaskMan SUBMIT/NOPRINT/NOLOG/USER=TASKMAN/QUEUE=TM$ NOTE THAT THE SYSTEM IS IN A 'SIGNOFF' STATE, WHICH PROBABLY EXPLAINS WHY TASKS ARE NOT RUNNING!! TASKMAN IS ALREADY RUNNING YESyes^NOno ARE YOU SURE YOU WANT TO RESTART TASKMAN? NO// Restarting... Taskman NOT Restared Answer YES to restart TaskMan. TaskMan must be running in each library uci on the system for tasks to run. One TaskMan per library uci should be enough for all but the busiest sites. The System Status option and the Monitor TaskMan option can help determine whether a TaskMan is running on this volume set. If you are still uncertain how to respond, answer NO and consult your documentation or your support ISC. TaskMan restarted! Checking Task Manager's Environment. Checking Taskman's globals... Checking the ^%ZOSF nodes required by Taskman... ') is missing! All ^%ZOSF nodes required by Taskman are defined! Checking the links to the required volume sets... The link to volume set is present! There are no volume sets whose links are required! Checks completed...Taskman's environment is okay! Here is the information that Taskman has: Operating System: Volume Set: Cpu-volume Pair: TaskMan Files UCI and Volume Set: Log Tasks? Default Task Priority: Task Partition Size: Submanager Retention Time: Min Submanager Count: Taskman Hang Between New Jobs: TaskMan running as a type: TaskMan is using VAX DSM enviroment: TaskMan is using ' for load balancing Logons Inhibited?: Taskman Job Limit: Max sign-ons: Current number of active jobs: appears to be down! SUBMIT/NOPRINT/NOKEEP/QUEUE=TM$ SUBMIT/NOPRINT/NOLOG/QUEUE=TM$ ZTMGRSET Version HELLO! I exist to assist you in correctly initializing the current account. I think it is . Should I continue anyway? N// Can't determine the OS type. Exiting ZTMGRSET. Need a Patch number to load. Patch number to load: I will now rename a group of routines specific to your operating system. Which MUMPS system should I install? NOT A VALID CHOICE Now to load routines common to all systems. Installing ^%Z editor Setting ^%ZIS('C') Want to rename the FileMan routines: No// - Use autostart to do ZTMB don't resave as STUSER. ZL @FROM ZS @TO Now, I will check your % globals. TASK'S^14.4^ FAILED ACCESS ATTEMPTS LOG^3.05^^ PROGRAMMER MODE LOG^3.07^^ MGR_SUB_ NO-OPTION TaskMan now in 'WAIT STATE' Are you sure you want to stop TaskMan? NO// Answer YES to shut down all Task Managers on current the volume set. TaskMan NOT shut down. Shutting down TaskMan. SMAN(NODE) Should active submanagers shut down after finishing their current tasks? NO// YESyesNOno Please answer YES or NO. SSUB(NODE) Okay! LAST UPDATED Live : Checking Taskman. Current $H= RUN NODE= Taskman is late by shutting down not running. Checking the Status List: Node weight status The Status List is Checking the Schedule List: Taskman has of them First task is seconds late. Checking the IO Lists: Last TM scan: Last Dev: There are no tasks waiting for devices. is not available, is allocated, is AVAILABLE, one task Checking the Job List: are no tasks waiting for Not responding Out Of Service Checking the Task List: currently running. Sub-Managers told to Wait. On node are no free Sub-Manager(s). BWait SUB-MANAGERS ARE NOT STARTING. Enter monitor action: UPDATE// Mode set to Enter to update the monitor screen. Enter ^ to exit the monitor. Enter E to inspect the TaskMan Error file. Enter P to see taskman parameters. Enter R to see busy Resource slots. Enter S to see a system status listing. Enter ? to see this message. Enter ?? to inspect the tasks in the monitor's lists. In the wrong account. Resource Slot: This will move the complete text of the routines selected to the MGR account of the system being moved to. If you send a large number of routines you may run out of disk space on the target system. send what routines! You're in Then... Starting to send! as task # in UCI: To which Volume Set (2-7 letters or * for all) to send routines? THIS IS THE SAME SYSTEM!! Auto-load or Manual: Manual// Enter UCI to unload into: >>ROUTINES WILL NOW BE SENT TO AS TASK # accessed by uci,volume: REMEMBER YOU MUST LOAD THE ROUTINES IN MANUALLY AT THE OTHER CPU WITH 'D IN^%ZTMOVE' F I=1:1 S R=$O(^UTILITY($J,R)) Q:R'?1AP.ANP ZL @R W $J(R,10) S ^[MGR,SYSM]%ZTSK(ZTSK,I,0)=R F J=1:1 S T=$T(+J) Q:T= transfered from >>ROUTINES WILL NOW BE SENT TO THIS MACHINE AS TASK # ZTMOVE of routines to CANNOT SEND TO ' Error exit Delete Task After Loading? No such task number exists. Not a 'ZTMOVE' task! READY TO BE LOADED INTO ' F J=1:1:N ZR S R=^%ZTSK(ZTSK,J,0) X ZTL ZS @R ZR X ZTL ZS @R D ERROR^%ZTMS HALT Sub $ETRP ZTMS$ stopped because of an error Stopped because of an error Caused by the submanager while trapping an error. an unknown task. Caused by the submanager. Caused by the submanager while preparing Caused by submanager after Caused by Stopped by User No Lock C No Lock JOBQ No Lock IO IO TIME No routine at destination rescheduled for busy device BTask Started Running 1 General error Job asked to stop No Lock Discarded Because Incomplete Got PRINTS FIRST LINES (A)lpha, (D)ate ,(P)atched, OR (S)ize ORDER: A// Include line 2? FIRST LINES PRINT FIRST LINE LIST: SIZE RANKING: Enter Return to continue REVERSE DATE ORDER: Patched routines Routine Print: Want to start each routine on a new page: Yes// Enter Yes to start each routine on a new page. No for the old way. Want line numbers: No// Enter Yes to have line numbers, O for offset numbers, No for no line numbers. YyNnOo NO routines selected. ROUTINE LIST Display Patches for Selected Routines No routines were selected. Installed Patch Listing Processing routines... Total Patches = Total Routines = Enter RETURN to continue or '^' to exit: Installed Patches for Selected Routines Patch # ROUTINE DELETE routines to DELETE, OK: NO// List of routines to DELETE ** TROUBLE ** - ** CALL IRM NOW! ** RECORDING THAT AN ERROR OCCURRED --- Sorry 'bout that --Interrupt Acknowledged NOPEN>^XUS RECORDING THAT AN ERROR OCCURED --- Waiting --Interupt Acknowledged This routine will rename the correct routine to ZU for you. Don't know what to do. #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### #################### ####################