Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
Re: Wakeup userid - what is it?
(piggyback)
Bertram Moshier wrote: Larry S wrote:I would like to also point out that the password for any user can be easily discovered by simply examining the MAINT userid's "USER DIRECT" file. If you know the password for the MAINT userid, you know the password for ALL userids. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Wakeup userid - what is it?
Yes, WAKEUP. On Thu, Apr 20, 2023, 17:04 Larry S <larryschacher@...> wrote: Is there a password for the WAKEUP user? |
Re: Wakeup userid - what is it?
Hello Dave, Thank you for your additional and extremely information.? It makes accessing and using the VM easier. Bert On Thu, Apr 20, 2023, 06:42 Dave Wade <dave.g4ugm@...> wrote:
|
Re: Wakeup userid - what is it?
¿ªÔÆÌåÓýBert, You can shut the machine down from MAINT or OPERATOR by ¡°SMSG WAKEUP SHUTDOWN¡± => yes I looked at the source to figure this out. If you then logon to the wakeup VM it starts as a normal VM and you can edit the files. The whole machine is implemented as REXX EXECs so all the source is on your ¡°A¡± disk. The format of the WAKEUP file is documented in the end of the $WAITF EXEC To restart type ¡°wakeprof¡± and then ¡°#cp disc¡± Dave ? From: [email protected] <[email protected]> On Behalf Of Bertram Moshier
Sent: Thursday, April 20, 2023 4:21 AM To: [email protected] Subject: Re: [h390-vm] Wakeup userid - what is it? ? Hi Bob, ? Thank you for your reply.? I'm looking forward to the HELP file. ? 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. ? Is the source code for WAKEUP on user's minidisks? ? Bert ? On Wed, Apr 19, 2023, 10:36 Bob Bolch <Bob@...> wrote:
|
Re: Wakeup userid - what is it?
Hello Dennis! Thank you so very much for your reply! Bert On Thu, Apr 20, 2023, 00:20 Dennis Boone <drb@...> wrote: ?> Thank you for your reply.? I'm looking forward to the HELP file. |
Re: Wakeup userid - what is it?
Hi! Where is the source code for WAKEUP?? I apologize, in advance, should you already answer this question.? Bert On Thu, Apr 20, 2023, 00:39 Dennis Boone <drb@...> wrote: The current-ish IBM documentation for WAKEUP includes some sample exec |
Re: Wakeup userid - what is it?
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 |
Re: Wakeup userid - what is it?
On Wed, Apr 19, 2023 at 08:21 PM, Bertram Moshier wrote:
After all, there must be someway to exit to CMS so one can modify the WAKEUP TIMES file.Here's one way to do it: logon maint force wakeup link wakeup 191 397 mr acc 397 z edit wakeup times z rel z ( det autolog wakeup wakeup exec wakeprof logoff Cheers, Rene FERLAND, Montreal |
Re: Wakeup userid - what is it?
Hi Bob, Thank you for your reply.? I'm looking forward to the HELP file. 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. Is the source code for WAKEUP on user's minidisks? Bert On Wed, Apr 19, 2023, 10:36 Bob Bolch <Bob@...> wrote:
|
Re: Wakeup userid - what is it?
WAKEUP is one of the many variants, commonly in use starting in VM/370, of a server machine which starts?various tasks according to a schedule. It uses a control file named?WAKEUP TIMES. Each line in the file contains a command to be executed, and when to execute it. I will try to cobble a HELP file entry together, in the next few days, describing the format of each entry.?? Bob Bolch On Wed, Apr 19, 2023 at 10:47?AM Bertram Moshier <herc370390vm@...> wrote:
|
Re: Wakeup userid - what is it?
On Wed, Apr 19, 2023 at 05:12:04PM +0200, Bernd Oppolzer via groups.io wrote:
Hello Bertram,That sounds like "cron" ( but different ) in the Unix-like world. Brian |
Re: Wakeup userid - what is it?
Hello Bertram,
toggle quoted message
Show quoted text
when I worked with VM in the 1990s, we had several server machines running disconnected which did some work depending on certain events (time of day, incoming RDR files, incoming SMSG, IIRC). The service machine was set up using a REXX with an endless loop; the REXX called a program (a MODULE) called WAKEUP or YWAKEUP, which was instructed to wait until certain events occur; it then put the machine in an inactive state and returned (with a certain RC), when some of the events specified occured. The REXX could then examine the RC and react on the event (for example, read the RDR file and process it or implement the command given by the SMSG or do some work at a certain time of day). We used these machines to do different remote processing, for example: transfer files to remote locations, collect plot files and send them to the plotter after a certain amount of time (looking if there is some possibility to optimize paper usage) etc. etc. WAKEUP or YWAKEUP, IMO, was a module which was part of the VM distribution at that time. But the server machines had different names, depending on the specific task (GKSPLOT, MAILER, ...). They all used the WAKEUP module. The machines were all AUTOLOGged normally during system startup. If they didn't run, we started them manually by using LOGIN ... they DISCONNECTED soon after doing their initialization work. I recall writing some of the control REXX procedures for these machines, but I don't have them any more. HTH, kind regards Bernd Am 19.04.2023 um 16:46 schrieb Bertram Moshier: Hello, |
Wakeup userid - what is it?
Hello, I'm trying to find information about the WAKEUP user.? After logging into WAKEUP and trying the "help" command, I'm left not understanding it. I looked through the text files for VM/CE and found: 19. Build WAKEUP server ID and add entry to autolog it in AUTOLOG1's PROFILE EXEC. ? ? This server issues commands at specified times during the day, week, month, or year.?? This isn't helpful in using it (at least for me). I would appreciate help in finding information on this user / program. Thank you. ? |
Re: CMS cashed during an HX of a REXX program
¿ªÔÆÌåÓýFolks, From what I remember, and its been a while, whilst BREXX accepts NUMERIC DIGITS statements but anything above 16 is ignored. Dave ? From: [email protected] <[email protected]> On Behalf Of Bertram Moshier
Sent: Friday, April 14, 2023 9:37 AM To: [email protected] Subject: Re: [h390-vm] CMS cashed during an HX of a REXX program ? Yeah, but should CMS die so badly it can't continue?? If REXX incorrectly maintained its allocated memory, shouldn't it be REXX to die and not all of CMS? ? I see two issues:? REXX has an allocation of memory issue and CMS shouldn't let a REXX program crash it. ? Bert On Thu, Apr 13, 2023, 10:34 Dennis Boone <drb@...> wrote:
|
Re: CMS cashed during an HX of a REXX program
Yeah, but should CMS die so badly it can't continue?? If REXX incorrectly maintained its allocated memory, shouldn't it be REXX to die and not all of CMS? I see two issues:? REXX has an allocation of memory issue and CMS shouldn't let a REXX program crash it. Bert On Thu, Apr 13, 2023, 10:34 Dennis Boone <drb@...> wrote: ?> DMSFRE161T INVALID DMSFRET CALL FROM F9041A, ERROR NUMBER 6. |
Re: CMS cashed during an HX of a REXX program
You have a good point about the numeric digits 10000, but should it cause CMS to abend bad enough to stop completely? Bert On Thu, Apr 13, 2023, 10:17 Joe Monk <joemonk64@...> wrote:
|
Re: CMS cashed during an HX of a REXX program
DMSFRE161T INVALID DMSFRET CALL FROM F9041A, ERROR NUMBER 6.> DMSABN152T SYSTEM ABEND 0F8 CALLED FROM F9041A WHILE 'UFDBUSY' = 02. > CP ENTERED; DISABLED WAIT PSW '00020000 60F8F730' Er, so, REXX tried to allocate storage for that, and it apparently failed to get it, but didn't notice, then tried to return the storage? De |
Re: CMS cashed during an HX of a REXX program
Of course its going to crash. numeric digits 10000? really? you want 10000 places of?precision? the normal setting is 9. so this statement "IF A//1000 = 0 THEN DO" causes a math calculation with 10000 places behind the decimal point.Why? Joe On Thu, Apr 13, 2023 at 10:05?AM Bertram Moshier <herc370390vm@...> wrote:
|