This got me to wondering is there any other info you can glean from a dump of
a looping SRB? For a TCB you could look for registers in the TCB/PRB/SVRB to
get a clue of where you were recently.
Is there anywhere else you can go for this sort of info for an SRB?
If you only have a dump
Paul Gilmartin wrote:
begin extract
And I still find it strange that RECFM=VB allows a logical record with
data length of 0, but for RECFM=VBS, there is no way to construct a
logical record with data length of 0.
end extract
It is not that there is no way. I can think of one, and I suspect
that
n 9/6/2012 8:31 PM, Skip Robinson wrote:
I have never understood the fixation with rock bottom return codes. SMP/E
maintenance is so much simpler without agonizing over every uneven
cobblestone along the path.
LOL. You have provided an excellent description of, what I consider to be, the
most
On Sat, 6 Oct 2012 09:07:31 -0400, John Gilmore wrote:
Paul Gilmartin wrote:
begin extract
And I still find it strange that RECFM=VB allows a logical record with
data length of 0, but for RECFM=VBS, there is no way to construct a
logical record with data length of 0.
end extract
It is not that
To all interested in this topic, particularly, for the first topic, Norbert
Friemel (for Gilbert Saint-Flour), Phil Smith and Edward Jaffe
Would someone be so kind as to explain why the two flavours for the operation
of IND$FILE are tied to Control Unit Terminal (CUT) type and Distributed
John
Does that mean that when I use IND$FILE with a 64x128 screen it sends 8192
bytes at a time ?
I think so. But remember that those 8192 bytes must include any require 3270
protocol overhead bytes.
Assuming my analysis of the significance of *not* being able to use Write
Structured
Mike
Here is Microsoft's suggestions for increasing the speed, from 2004.
http://support.microsoft.com/kb/125881
The first point to make here is that the configuration which applies to Bill
Gates's SNA Server (BizTalk Server Host Integration Server these grandiloquent
days) is probably *not*
Elardus
When VTAM is doing a GETMAIN for more buffers, all using VTAM need to wait
for that GETMAIN to complete. Not a problem, but observable ...
The trick here is to tune the dynamic buffering parameters. You can set the
affected buffer pool to have sufficient buffers to be able to cater
On 10/6/2012 1:07 PM, Paul Gilmartin wrote:
The essence is I'm baffled. I can think of no valid
representation in a RECFM=VBS data set of a logical
record with zero data length. If I've missed something,
please enlighten me. I'd appreciate hex representations
if more understandable than
Ok John, I will bite what's a BIF ?
Scott ford
www.identityforge.com
Tell me and I'll forget; show me and I may remember; involve me and I'll
understand. - Chinese Proverb
On Oct 6, 2012, at 8:49 AM, John Gilmore jwgli...@gmail.com wrote:
Randy Hudson wrote:
begin extract
I don't
Scott,
BIF = Built-in Function
John P. Baker
President
NGSSA, LLC
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Scott Ford
Sent: Saturday, October 06, 2012 2:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is there a correspondence
On Sat, 6 Oct 2012 13:25:42 -0400, Gerhard Postpischil wrote:
On 10/6/2012 1:07 PM, Paul Gilmartin wrote:
The essence is I'm baffled. I can think of no valid
representation in a RECFM=VBS data set of a logical
record with zero data length. If I've missed something,
please enlighten me. I'd
Thanks John, haven't seen that ow before ...
Scott ford
www.identityforge.com
Tell me and I'll forget; show me and I may remember; involve me and I'll
understand. - Chinese Proverb
On Oct 6, 2012, at 2:12 PM, John P. Baker jba...@ngssallc.com wrote:
Scott,
BIF = Built-in Function
John
I'm all about cutting extraneous corners, but some corners may object by
cutting back. I looked at Ed Webb's pitch, which reads like a developer's
anthem. Ed sums up his environment this way: users exist to provide a test
load. Fair enough for his shop, and I assume for yours also. But my users
Gerhard Postpischil is of course quite right that RECFM=VBS can be
used without segment descriptors, although FORTRAN and PL/I
data-directed I/O do still use them.
I had hoped only to elucidate the historical roots of VBS, and I
suppose that in some measure I did elicit information about them. I
BIF has come to be the generic term, but the same notion has been
given different names in different statement-level procedural
languages. COBOL, for example, calls them intrinsic functions.
The idea is an important one. None of us wants to use an SLPL in
which such constructs as
y = sqrt(x) ;
Ed:
I am not sure I agree.
I swear by the return codes in SMPe Simple rule is anything above a 4
(four) needs attention.
That is as simple as you can get. I never applied maintenance on a
live running system, it was always on a sysres or DLIB(s) on a set of
disks that were mounted as
On Oct 6, 2012, at 12:07 PM, Paul Gilmartin wrote:
SNIP---
For the ultimate irony, did the FORTRAN compiler source code
input with RECFM=VBS?
-- gil
Gil:
The G1 compiler needed FB (80) I never got to tinker with the WatIV
as the project never needed the
Translators---compilers and assemblers---are usually most comfortable
with FB source-language card-image inputs.
There is much to be said for supporting VB input, since the chief
determinant of a translator's performance is the facility and
rapidity with which it eliminates insignificant blanks
On Thu, Sep 20, 2012 at 6:47 PM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
Every generation believes that it invented sex. The 4300 may mark
MVCIN becoming standard, but the instruction is much older than the
4300. The Technion had it on their 370/165 in 1972, and I believe
On Sat, 6 Oct 2012 18:53:03 -0400, John Gilmore wrote:
If I were the deity symbol-table management would be more important
than blank suppression; but, as John Cocke showed conclusively, this
is not the case. It is almost a law of nature that intellectually
interesting problems turn out in the
The evolution of mainframe facilities for handling non-standard
right-to-left text (and thus boustrophedon text too) has been gradual.
MVCIN came early on. TRTR and TRTRE are more recent. It is now
possible to perform lexical-breakout operations on right-to-left text
directly and easily. (I
Look in
John Cocke and Jacob T. Schwartz. Programming languages and their
compilers. 2nd revised edition. New York: Courant Institute of
Mathematical Sciences, New York University, 1970.
We all would have guessed [and I at least would have liked to
believe] that other issues were more
On 10/6/2012 1:03 PM, Skip Robinson wrote:
Would not APPLY CHECK have revealed the missing PTF before
any real harm had been done? If not, then never mind.
No. The APPLY CHECK would not have helped in that case. Nothing was missing and
there was nothing SMP/E could have done differently. Both
At 13:25 -0400 on 10/06/2012, Gerhard Postpischil wrote about Re:
Zero length records outlawed! (Again.):
Perhaps I'm missing something, but hex 0004 defines a null
record in V, VB, and VBS. VBS runs fine without segment
descriptor bits.
Correct (if I remember correctly).
There are 4
On Sat, 6 Oct 2012 16:36:06 -0400, John Gilmore wrote:
Gerhard Postpischil is of course quite right that RECFM=VBS can be
used without segment descriptors, although FORTRAN and PL/I
data-directed I/O do still use them.
Not as I read the document cited earlier. VB data sets have RDWs;
VBS data
On Sat, 6 Oct 2012 21:39:13 -0400, Robert A. Rosenberg hal9...@panix.com
wrote:
There are 4 types of records in a VBS block (which are identified by
the segment descriptor bits). These are start of segment (the record
continues in the next block), end of segment (this is the end of a
You appear
27 matches
Mail list logo
