开云体育

Looks like your CMS saved segment is bumping up against another segment. See https://IBM.com/support/pages/apar/II04761

Anyone ever seen anything like this and knows what it means, and how to fix? I receive it even if I define storage at 8m all the way to 16m. acc 198 z DMSLIO109S VIRTUAL STORAGE CAPACITY EXCEEDED.

I'm not sure, and I prefer not to describe what little I do know of the internal configuration due to security. Suffice to say a configuration got reset during a power related reboot (I honestly don't

Hello! Drew? I know you don't, (that is work for them), but what did happen this time? ----- Gregg C Levine gregg.drwho8@... "This signature fought the Time Wars, time and again." And this

If you're trying to log into the LCM+L VM/SP machine and can't, the Highs Elves of the LCM+L are aware of the problem; they working on it. It may take a couple weeks due to an Elf central to the

Kevin explained in the OS360 group: "MVT, unlike OS/VS systems, doesn't maintain a local offset from the TOD clock; that is, every SET command tries to set the clock directly, not just an offset.?

Yep, I run with it in all my images.? You showed it to me years ago when I had issues sharing 2314s.

Strange... Isn't TODENABLE just to allow the guest to *set* the TOD clock? Anyone can read it. Do you actually need to set it? Heh... I remember around 1999-2000 on a P390 (actually an Integrated

Jeff Snyder wrote: [...] Does your Hercules configuration file specify the LEGACYSENSEID option? * https://sdl-hercules-390.github.io/html/hercconf.html#LEGACYSENSEID -- "Fish" (David B. Trout)

I tried testing this on VM/ESA and ran into some problems. When defining the guest in USER DIRECT, I gained the TODENABLE option, however I lost REALTIMER and ISAM, which the manual for VM/SP says are

The year 1955 cannot be represented in a TOD clock using the MVT epoch of 1960, so - although the wording is odd - it doesn't surprise me that it won't accept it. But I don't remember how the TOD

Hi Chris, It looks like that gets us outside MVT's sanity check range: | 00 IEE116A TOD CLOCK INVALID- REPLY WITH SET PARAMETERS | R 00,'CLOCK=01.01.01,DATE=55.066,AUTO=N' | IEE600I REPLY TO 00 IS;

Do you mean with IND$FILE? If so, the answer is yes. ASCII. You may watch this video: https://www.youtube.com/watch?v=U-kFCsiqB0c (sorry if it is a little long) Cheers, Rene FERLAND, Montreal

Hello Rene, Thank you for your message and information. Question: On REDIT and WINMMG can I upload them via the built in wc3280 and CMS method? Are they binary or ASCII or ??? BTW, How do you transfer

In 2008, Robert O'Hara wrote a small Windows program to achieve that purpose. It is called VMconsole.exe. It is essentially a modified telnet client. You connect to VM/370 using it with a command like

Jeff, It looks most odd, as the time is also corrupted. What happens if you change the order of the reply thus:- R 0,'DATE=55.066,CLOCK=01.01.01,AUTO=N' (that's the format in my notes for MVT). Chris

Hi Uwe.? Using 28 years set the date back to 1995, which should have fit within MVT's sanity check for dates.? When I did that, MVT thought it was 1955.? I'm afraid if I go back any further, I

Tony, Unfortunately, this option is not available to VM/SP5.? However, I have a VM/ESA image available to me, I may try looking over there and see if this is an option.? I'm afraid that if I get too

Hi Fish, thanks for the input.? Unfortunately, this approach has a couple drawbacks that limit its usability for me: 1.? When submitting the jobs in the fashion you describe, they are not presented

Jeff- Have you tried to set the VM date set back 56 years? A multiple of 28 and sets the date back before 2000 for MVT. -Uwe