开云体育

?> Thank you for your reply.? I'm looking forward to the HELP file.

I've included a WAKEUP HELP file below.

I have no idea what version of WAKEUP provided this file, and it's
nearly guaranteed to be different from whatever is in the CE.? That
said, it may be a source of clues.

?> I hope you'll consider including any commands someone can use after
?> logging onto the userid.? After all, there must be someway to exit to
?> CMS so one can modify the WAKEUP TIMES file.? I'm wondering is there
?> a way to look at the entries from the command line (or other stuff)
?> without exiting to CMS.

If you want to make your life sane, you rig your REXX or EXEC2 script to
wrangle WAKEUP to recognize a reload command sent by SMSG, and have it
reload the WAKEUP TIMES file.? In the service machine, put the file on a
read only minidisk.? That way you can link it to place the new file
there, release it, then tell the service machine to reaccess and reload.

The procedure for putting the updated file onto the service machine
mdisk is:

0. Do sane error handling as you...

1. Get an MR link to that mdisk

2. Access the mdisk

3. Copy the new file onto the target mdisk as UPD CMSUT1 or some such

4. Rename the old file out of the way; we always prepended a digit to
the filemode, and rolled older copies on down (1EXEC -> 2EXEC, EXEC ->
1EXEC, etc.)

5. Rename UPD CMSUT1 to the target fn fm

6. Release/detach the mdisk

7. Tell the service machine to refresh itself (reaccess mdisk, reread
file)

Bonus points: log files

Obviously this is easier to do if it's scripted up in REXX.

De


WAKEUP

WAKEUP is a? module designed to control? the operation of event? driven virtual
machines.? WAKEUP? may be? used to "wake? up" a virtual? machine at? a specific
time, or when some event occurs (e.g., receiving a file).

The format of WAKEUP is:
+------------+---------------------------------------------------------+
|? ? ? ? ? ? |? ? ? ?< at >? ? < HH:MM<:SS>? >? ? ?< ( options > <)>? ?|
|? ?WAKEUP? ?|? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|
|? ? ? ? ? ? |? ? ? ? ? ? ? ? ?<+<HH:>MM<:ss>>? ? ?< ( options > <)>? ?|
|? ? ? ? ? ? |? ? ? ? ? ? ? ? ?<RESET>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|
+------------+---------------------------------------------------------+

Options:

? ? ?CONS? ? ? -? Wake up on a console attention or line in the stack
? ? ?EXT? ? ? ?-? Wake up on an external interrupt
? ? ?FILE? ? ? -? Wake up at the next time in the 'wakeup times' file
? ? ?IO? ? ? ? -? Wake up on an I/O interrupt
? ? ?IUCVMSG? ?-? Wake up when a message arrives (use IUCV to receive it)
? ? ?RDR? ? ? ?-? Wake up when a file is in the reader
? ? ?SPM? ? ? ?-? Wake up when a message arrives (use SPM to receive it)
? ? ?SMSG? ? ? -? Wake up when an SMSG or VMCF SENDX transmission arrives
? ? ?VMCF? ? ? -? Wake up when a VMCF SENDX message arrives

? ? ?NOEXT? ? ?-? Prevent DEBUG entry on external interrupts
? ? ?RESEXT? ? -? Reset a previous NOEXT option
? ? ?TIME? ? ? -? Stack the time and date on exit
? ? ?QUIET? ? ?-? Don't show any informational messages
? ? ?CC? ? ? ? -? Use Clock Comparator for timing (instead of STIMER)
? ? ?NOREAD? ? -? Do not issue a read on console attention interrupt

If more than? one option is specified,? WAKEUP will return control? when any of
the? specified? events? occur.? ?Thus,? "WAKEUP +30 (RDR IUCVMSG"? will? return
control in 30? minutes, as soon as a? file arrives, or when? a message arrives,
whichever occurs first.

Normal return codes:

? ? ?0 - All TIME file records for today have been executed
? ? ?1 - VMCF or SMSG message arrived
? ? ?2 - Time (HH:MM:SS or +MM) expired
? ? ?3 - Time from timer file expired
? ? ?4 - File in the reader
? ? ?5 - Message arrived (via IUCVMSG or SPM)
? ? ?6 - Console attention
? ? ?7 - External Interrupt
? ? ?8 - I/O interrupt

An interrupt? from the? console always? causes control? to be? returned with? a
return code of 6, regardless of the options given when WAKEUP was called.? This
usually means someone has? logged on the virtual machine and? hit the ENTER (or
carriage return) key to cause the interrupt.

Interrupts from? the FILE,? IUCVMSG, VMCF,? SMSG, EXT,? and I/O? options causes
WAKEUP to put details of the interrupt on the stack.

Some error return codes

? ? ?28? - Timer file not found ("STATE WAKEUP TIMES" failed)
? ? ?100 - Explanation complete (result of 'wakeup ?')
? ? ?1xx - Error from RDCARD macro
? ? ?101 - Empty file in card reader
? ? ?103 - Unknown error from card reader
? ? ?200 - Invalid option (For example,? WAKEUP (XXX ) )
? ? ?201 - Virtual reader not operational (rdcard rc=100)
? ? ?202 - Error from spool rdr hold
? ? ?203 - Invalid hours field
? ? ?204 - Invalid minutes field
? ? ?205 - Invalid seconds field
? ? ?206 - Invalid parameter
? ? ?207 - Error reading timer file
? ? ?208 - Error from vmcf authorise
? ? ?209 - Sendx data length > 100
? ? ?210 - VMCF data transfer error
? ? ?211? ?Error writing time/datestamp to timer file
? ? ?212? ?Time parm error in timer file
? ? ?213? ?Wakeup times file not on r/w disk
? ? ?214? ?I/O or ext new psw = mine (serious internal wakeup error)
? ? ?215? ?Relative time specified with monthly/yearly
? ? ?3xx? ?IUCV error