开云体育

We ran a Hasp workstation.? Not sure if there's an equivalent, or the tool referenced i

There was an NJ38 software in the files section you may want to try it. Rahim

I have up and running MVS38j and VM370 6PExt and appear to be working correctly.? Next I want to connect VM370 to MVS38j so the VM370 system could send jobs and get prints back. I have studied the

I am trying to connect MVS38j via nje38 to VM370 via RSCS.? No joy. Has any be able to do this and if so any tips. thank /tc

The point I was trying make in my last comment (and in general) is that native MVS date processing is "in character" for it — in other words, utterly unfriendly!? :-) This conversation wandered off

Hello Drew, Am 31.07.2022 um 02:23 schrieb Drew Derbyshire <swhobbit@...>: I feel the discussion deteriorated somewhat to gentle teasing having left the occasional digression discussions

I sometimes use the yyyy-mm-dd, for example that is my external date stamp for MVS hardcopy log. None of these date comments apply to the original post; as shown at the beginning of the thread,

Marco Antoniotti wrote: [...] The international (world over) standard (or at least it's SUPPOSED to be!) is ISO 8601, which is indeed YYYY-MM-DD, was chosen for precisely that reason: easy sorting: *

There is a international standard for such matters when run on *.nix and Windows. Now I have forgotten exactly for Windows but for Linux it is the Locate defaults set for the system in use and here

Hello Vince Am 30.07.2022 um 14:44 schrieb Vince Coen <vbcoen@...>: At least in Germany, it's not / but . as separator. This is most helpful to know if 10/12/1999 was meant as 10th of December,

In that case they use the *nix standard in place of the other two standards namely : DD/MM/CCYY??? - UK and many others MM/DD/CCYY??? - USA CCYY/MM/DD?? -? Every where else but is used in

The Fujitsu assembler had an &SYSDATE format of YY.MM.DD which I found much less confusing than the &SYSDATE of IBM assemblers... Cheers, Greg

Hi interesting conversation. Just to make it more interesting, many years ago, I switched to "Japanese" date formats (I don't know whether they are actually Japanese, but I remember reading so

" It's eight o'clock in Los Angeles. It's nine o'clock in Denver. It's 10:00 in Chicago. And in Baltimore, it's 6:42. Time for the 11o'clock report …" — George Carlin I think we have seriously

I'm American, and have been using 24 hour time for a few decades. I've worked with several systems that required entering times in 24 hour format. Once I got used to it, it made more sense to me than

The MVS Time SVC not only converts from timer units to hundredths of seconds, it then converts binary to packed decimal. I finally put a loop in the code: * Get both times * Compare hundredths of

Quite succinct and true. Why would I use 24 hour times? That, like the Julian date, gives me a chance to blow a conversion. -ahd-

Coz they is American :)

Why don't you use 24 hour times????????? wrote:

A bit pf trivia ... Long ago and far away, I worked at Link Flight Simulation of the Singer Company; we ran MVS/SP on an IBM 4341. There, on the week of 8 June 1984, an operator blew the Julian date