开云体育

Hello Mike, Am 06.12.2020 um 17:45 schrieb Mike Schwab <Mike.A.Schwab@...>: This is about the only sentence I understood. :-) The rest of your detailed explanation doesn’t make sense to me.

There is only the Editor. If you really must, you can choose between M-x evil and M-x viper You cannot do the opposite :) Of course, you can write a XEdit emulator in the Editor :) :) :) Cheers --

There's no button.... because I read the traffic by email. Worse, when a (slightly different, I suppose) message arrives, there's nothing in its text that shows what was changed. -- Jeremy Nicoll - my

Due to inter record gaps and the count block, 2 blocks of 27998 without a key will fit on a single 3390 track. Blocks of 27999 or more will be 1 block per trac.

That is a result of using the edit feature. ?I try to use it minimally but if I enter something truly incorrect, ?I make a edit. If you click on the Edited button on the far right of the message,

"2) There are overheads in a block. In a Count-Key-Data disk type (such as a 3390), a data block is preceeded by a count block and (possibly) a key block. In a physical 3390 blocks are (were) stored

I've tried various good and bad editors. I keep going back to vim. I think I tried THE editor, but it's been a while: http://Hessling-Editor.SourceForge.net/ Why look for an Emacs mode to edit JCL if

The CIA/NSA. When they get a copy of every IP message going through a few ISP hubs, sometimes the second message gets back onto the internet. I have one particular web site that keeps track of which

"1) With RECFM=FB, the block's size must be a multiple of the record length. Plainly 28332 isn't a multiple of 80." a 3390-1 has a tracksize of 56,664. 56664 / 80 = 708 records per track. 354 records

Hi I know that around here parentheses may not be appreciated, but it turns out I do. Many people here seem to work on Linux/Mac/Windows using bad editors (yep!? I *am* wearing flame-retardant

Why do I (and presumably other people too) get two copies of some messages, the latter one always seemingly starting with that [text]? -- Jeremy Nicoll - my opinions are my own.

Evidently, Assembler F was written by 3 or 4 people. ?Some comments in the source code state something like “call Joe’s parser”, “call Frank’s routine”, etc. I knew the author of

Mike, Your explanation of a PDS is the "down and dirty details" - however, we have ACCESS METHODS that are supplied to deal with all the special handling. The operating system supplies : BDAM - Basic

The track is the empty disk space. The blocksize is the physical block. VSAM writes Control Intervals (blocks) in multiples ofr 512, up to 4096. Larger control intervals are possible but are broken

Hello, Am 06.12.2020 um 06:39 schrieb jacampbellaus@... Thanks for that explanation. I’m glad to see that in the end, bytes are what really counts, even on MVS. Cylinder and track calculations

"Greg Price" <procegrog@...> writes: It's there. At least on my tk4- Update 8 system <#secure method=pgpmime mode=sign>

nope. Two things: 1) With RECFM=FB, the block's size must be a multiple of the record length. Plainly 28332 isn't a multiple of 80. 2) There are overheads in a block. In a Count-Key-Data disk type

Hello Joe, Am 06.12.2020 um 00:30 schrieb Joe Monk <joemonk64@...>: So it seems. Thanks for your explanation! :wq! PoC

Hello Jeff, Am 06.12.2020 um 00:07 schrieb Jeff Bassett <bassettj@...>: I don’t think it’s *no* use, but maybe less useful? When I want to create a dataset for some kind of tabular