开云体育

Hello Dave, Thank you for an explanation that gives solid reasons. Questions: Is there a way another user can get the TOD on the responses of CP? If not, how does one go about suggesting a

Bertram … oh and the OPERATOR ID behaves differently because its specified in DMKSYS as the SYSOPER ID and VM treats this differently. You can see this when you logon. You get times on the CP output

Yes its fine….listings below…. But of course it does depend on where DMSTIO is loaded so that patch only works for the current release of CE and you should check the instruction before patching

If you want an acid test, try WATERLOO2.aws and scan files 2 through 3 and see if it hiccoughs.? If not, then we certainly have a winner. Below is my attempt to scan it with PETAPE from WATERLOO5.aws

Hello Bertram, I followed the steps you indicated and I do observe the same behaviour as you. But that seems to come from the fact that the virtual machine is in TERM MODE VM (because of a command to

Hi, Yes on operator I do q v storage

Hello, The problem occurs after I IPL CMS. The steps are: 1) IPL CMS (e.g., /cp I cms) 2) At the prompt I do a /cp disc 3) After the PROFILE EXEC runs the user disc from the Hercules 3215 console. 4)

Dave Wade wrote: [...] FWIW, it appears that with z/VM, it doesn't load a disabled wait PSW after redefining storage either. Instead, it simply resets the system and clears storage ("Storage cleared -

Rene, It looks like when on OPERATOR with CMS loaded, and you change store it does not report Disabled Wait Loaded. I am not sure if it should. I’ll check on the base software. Dave Sent: Thursday,

What is the issue exactly? Because, on VM/370 CE, I can use cp define storage fine on the OPERATOR virtual machine: CP executes the command and the virtual storage is changed accordingly. Just

Bertram, Well OPERATOR is a funny beast. Many things behave differently, or usually behave differently. Its generally the first logged on user so it receives certain messages which can interfere with

Dave, Thank you very much. I hesitated to report a bug here because of my last experience. I discovered an issue with the CP Define Storage command when issued by the OPERATOR userid. A person said

Bertram, Its ok to just put it on here. There is a GITHUB site but not sure who owns it. https://github.com/s390guy/vm370 Dave Sent: Thursday, April 4, 2024 10:54 AM To: [email protected] Subject:

Hello, How does someone report a bug to VMCE (CP, CMS, RSCS, etc.)? I looked but couldn't find the location. Thank you, Bertram Moshier WB8ERT

Mark, OK so we don’t have the source to PETAPE only the mods that were made to DMSTAP. Not sure which of those tapes they are on, but I think they are there. Not sure at what point VMFPLC2 appeared,

When on MAINT remember its has all classes assigned, so on MAINT "Q STOR" behaves differently to other users.... .. if you do "Q STORE" you get the real system storage, if you do "Q V STORE" you get

I found the following reference to PETAPE's challenges due to IBM changes to CMS TAPE command. http://vm.marist.edu/~vmshare/browse.cgi?fn=FUTURE&ft=MEMO&args=PETAPE#hit Append on 06/27/90 at 09:49 by

Apparently, there are three storage values: the one in the Hercules configuration file, the one specified in DMKSYS, and the one in the VM directory. On MAINT, q stor gives the value in DMKSYS, and q

Hello! Correct. Mine also contains the accessory settings that we've discussed on this list before. ----- Gregg C Levine gregg.drwho8@... "This signature fought the Time Wars, time and again."

Hello! Um no that's the MAINT id that I always use. There are others in the list of valid ones, but that's the only one that I've gotten to work. ----- Gregg C Levine gregg.drwho8@... "This