PROG750
Frank Swarbrick
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
>>>
The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
David Purdy
In Redbook SG24-4689 (August 1999) page 22:
If you attempt to connect from PCOMM through a firewall to a CS/NT or s CS/2 gateway providing a TN2370/5250 service, you might get a PROG750 in the OIA of the session Screen. This problem has now been fixed but requires you to install a modified DLL. Connection from PCOMM through a firewall directly to a host systems does not have this problem.
In http://www.vm.ibm.com/service/rsu/tcip510.html
701RSU
PK27201
UK19084
TCPIP
PROG750 TN3270 WHEN LOGOFF FROM VM
LOGO CMD LINE
All I found on a Sunday night, dude.
David
-----Original Message-----
From: Frank Swarbrick <frank.s...@EFIRSTBANK.COM>
To: IBM-MAIN <IBM-...@bama.ua.edu>
Sent: Sun, May 30, 2010 6:09 pm
Subject: PROG750
Where can I find out what PROG750 means for a TN3270 session?
Thompson, Steve
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Behalf Of Frank Swarbrick
Sent: Sunday, May 30, 2010 9:09 PM
To: IBM-...@bama.ua.edu
Subject: PROG750
Where can I find out what PROG750 means for a TN3270 session?
<SNIPPAGE>
Frank:
All I can find has to do with problems with a printer. There is an APAR,
but I don't know if it applies to you: PQ56834: PROG750 ON TELNET
CLIENT
There is a RED Book:
http://www.redbooks.ibm.com/redbooks/pdfs/sg244689.pdf but I don't know
that this would actually apply. I would like to think that any of these
from 2007 and earlier you would already have. But if memory serves me
correctly, you are migrating from VSE to z/OS, so you may have some
older software out on your devices...
Also, you say TN3270. What TN3270 software are you using? It may be that
your ISV needs to provide a fix.
Regards,
Steve Thompson
Frank Swarbrick
'Incorrect command received'.
Makes "sense". It's definitely a 3270 emulator issue with our "screen
scraping" product. This is our first day on z/OS in production and
while there were some other issues this is one i've been working on for
four hours. Think I'm getting a handle on it, in any case.
Thanks!
Frank
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
On 5/30/2010 at 8:48 PM, in message <9e61a.19602...@aol.com>,
<Rbo...@AOL.COM> wrote:
> Here's a link to some. I've also included others which include ones
from
> the link:
>
> _http://publibz
>
.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23?SHELF=EZ2HW125&DT=1
> 9940419144012_
>
(http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23?SHE
> LF=EZ2HW125&DT=19940419144012)
>
> Input Inhibit Indicators
>
> Input Inhibited (Columns 9-17) This message accompanies the X in
column 9,
> and explains why input is inhibited.
>
>
>
> X Time is required for the host system to perform a function.
> X SYSTEM The host system has locked your keyboard. See if a
message
> appears. Wait, or press Reset.
> X nnn Machine Check Messages. The terminal is not configured
correctly
> or is malfunctioning.
> Xnnn Communication Check Messages. The communications link is
broken or
> malfunctioning.
> X You requested a Local Copy, but the printer configured for the
> terminal session is not working. The keyboard locks (keystrokes
queued)
> while this
> symbol is displayed.
>
> X You requested a Local Copy, but the printer configured for
that
> logical terminal is in use.
> X -f You requested a function that is not supported. Press Reset
and
> select a valid function.
> X > You entered more data in a field than is allowed. Press Reset
and
> correct the entry.
> You tried to alter data in a protected field. Press Reset.
>
> X -fX You are not authorized to perform this function. Press Reset
and
> try a valid function.
> X PROGnnn Program Check Messages. A program error has occurred.
> X -S You attempted to enter a graphic character that is not
available.
> This character may not be in the Base Character Set. Press Reset. Do
not
> select the symbol that caused the indicator to appear.
> X '+? You tried to enter an invalid character to be used with a
> Diacritic key sequence. Press Reset and try a valid sequence.
>
> X NUM You entered a keystroke other than numerics (0-9), a minus
sign, a
> period, a comma, or DUP in the 3270 numeric lock field. (3270
session)
> X ?+ You pressed the Response Time Monitor (RTM) key when the RTM
> function is not enabled. Press Reset. (3270 session)
> X < All columns are entry field columns. Enter data to the end
of the
> field. (5250 session)
> X You must enter the data in this field. (5250 session)
>
> X II Operator input error occurred. (5250 session)
>
>
> Machine Check messages
>
>
> Some 68n messages may appear as either Communication or Machine
checks.
> The explanations for 68n codes also apply to 68n codes.
>
> For other Machine messages not listed, refer to the IBM 3270
Information
> Display System: Reference Summary .
>
>
> 201 A parity error was detected.
>
> 207 The workstation failed to respond to a POLL from the control
unit.
>
> 209 The communication failed between the control unit and the
> workstation. Take a PCSMON data-trace and consult your system
administrator.
>
>
>
> 240 The wotkstation is disconnected.
>
> 241 The host system has ended communications with the display
station.
>
> 601 Missing attribute.
>
> 604 Invalid translation table.
>
> 606 Internal error.
>
> 610 CNOS (C
hange Number of Session) failed. The cause may be as
follows.
>
> · In the specified partner node, there is a session which has the
same
> Local LU name as that in the specified WorkStation Profile.
> · Link of partner node is not active. (Even if link of terminal and
> adjacent node is active, sometimes link of partner node and adjacent
node
> could
> be inactive.)
> · Fully qualified partner LU name is invalid.
> · Partner LU rejected the communication allocation request because
it
> could not start TP (LU6.2 Change Number of Sessions) immediately.
>
> · Because the maximum number of local sessions for partner LU is 0,
the
> local LU cannot have a session.
> · Partner node is configured for the single session(not the parallel
> session).
> · Before APPC allocated communication, an unexpected session active
> protocol error occurred.
>
>
>
> 612 APPC internal error
>
> · The number of parallel LU-LU sessions reached maximum.
> · Insufficient internal memory buffer for APPC, new communication
cannot
> be allocated.
>
>
>
> 615 The workstation receives negative response of Initial Response
> Packet.
>
> 620 Unknown request.
>
> 631 Message received with Begin Command Chain set.
>
> 632 Message received without Begin Command Chain set. .
>
> 633 No more data available.
>
> 634 More data available.
>
> 635 High-priority request received.
>
>
> 636 More structured fields available.
>
> 640 Invalid message destination.
>
> 641 Buffer space exhausted.
>
> 642 Message received from unknown origin.
>
> 650 Unsupported function.
>
> 660 Unknown SPI function code.
>
> 670 Invalid keystroke-type received.
>
> 671 Invalid keystroke value-received.
>
>
> 68n 68n These messages have the same meaning as their 68n
counterparts.
> Please refer to COMM Messages.
>
> 690 The coaxial cable is not connected to the communication
adapter, or
> the control unit is not powered on.
>
> 691 The communication adapter is defective or not installed.
>
> 692 The 3x74 control unit is not configured with DFT support.
>
>
> 693 The control unit is not configured for SNA Communication
protocol.
>
> 694 The control unit is not configured for non-SNA Communication
> protocol.
>
> 697 The control unit does not support the Slow Device and Extended
AEDV
> Status function.
>
> 698 OIA indicator array full.
>
> 699 OIA indicator is incorrect, while loading the program symbols.
>
> Communication Check messages
>
>
> COMM messages are communication reminders that indicate status or
error
> conditions.
>
> Some 68n messages may appear as either COMM or MACH checks. The
> explanations for COMM 68n codes also apply to MACH 68n codes.
>
> For COMM messages that are not listed, please refer to the IBM 3270
> Information Display System: Reference Summary.
>
>
> 16 The network name specified for your PC is already in use by
another PC
> on your LAN.
>
> 501 The 3274 or 3174 control unit is not on line to the host
system. With
> a Home3270 connection, the DSR (Data Set Ready) signal from the
modem or
> other connection-device is not present.
>
>
> 504 There is no telephone connection with the host; you must dial
the
> host to establish the connection. With a Home3270 connection, the CD
> (Carrier
> Detect) signal from the modem or other connection-device is not
present.
> (3270 session)
> The workstation is waiting for null XID from host to establish the
ADLC
> connection. (5250 session)
>
> 505 The host system is not operating or, if you have a leased SDLC
> connection, the link may be inoperative. (3270 session)
>
> The workstation receives null XID and the ADLC link goes into
> negotiation stage. (5250 session)
>
> 510 The PU is not active; the host has not activated the display
station.
> (3270 session)
>
The negotiation between the host and workstation has completed, and
the
> workstation is waiting for the acknowledge of VPD data. (5250
session)
>
>
> 518 A PIU (segment) was received out of sequence.
> 519 A data block was received that exceeded the size of the PIU.
>
>
> 645 The workstation failed to find a NetWare server.
>
> 646 LAN via Netware for SAA: The connection with the NetWare server
> failed.
> SNA Node is not started for LAN, SDLC, CommPort or Twinaxial
connection.
> LUA3270 via SNA Server: Microsoft SNA Server has not started.
>
> 647 The workstation failed to find the specified NetWare server.
>
> 648 The workstation failed to attach to the specified NetWare
server.
>
>
> 649 The workstation failed to get the specified resources from the
> NetWare server.
>
> 650 An internal error occurred between workstation and NetWare
server.
>
> 651 Initializing FMI for NT Client
>
> 652 The local node failure is reported by WDMOD.DLL for NT Client
>
> 653 The maximum number of sessions configured for this user has
been
> exceeded or user does not have access to the LU name or POOL name
> configured
> for this session.
>
>
> 654 TN3270E protocol only. This connection cannot be established
because
> the specified LU name is already associated with another Telnet
session, or
>
> it is not known to the server, or it is incompatible with the
requested LU
> type (terminal/printer mismatch, etc). Make sure the correct
TerminalType
> or TerminalTypeString is specified in the workstation profile and
the
> correct LU name is specified in the Telnet3270 advanced customization
> window.
>
>
> 655 Waiting for Telnet option-negotiation from the 3270 server host
(3270
> session). Waiting for Telnet option-negotiation from the Telnet5250
server
> (5250 session).
>
> 656 Initializing the TCP/IP Socket interface for Telnet3270 (3270
> session). Starting SNA server for LUA3270 via SNA Server (3270
session).
> Initializing the TCP/IP Socket interface for Telnet5250 (5250
session).
>
> 657 Resolving Telnet3270 server host-domain name (3270 session).
> Resolving Telnet5250 server host-domain name (5250 session).
>
>
> 658 Initializing the TCP connection for Telnet3270 (3270 session).
> Initializing the TCP connection for Telnet5250 (5250 session).
>
> 659 The Telnet3270 TCP connection has been cut off (3270 session).
The
> Telnet5250 TCP connection has been cut off (5250 session).
>
> 661 Searching for the next available LU or Pool Name on the
Microsoft SNA
> Server.
>
> 680 The workstation is offline from the LAN during initialization.
>
>
> 681 The LAN adapter failed to initialize correctly.
>
> 682 The LAN adapter failed to open.
>
> 683 The LAN adapter DHB (send-buffer) size could not be determined.
>
> 684 The SAP on the LAN adapter failed to open.
>
> 685 The link-station connection failed.
>
> 686 The LAN gateway is not active or you specified its address
> incorrectly.
>
>
> 687 The session with the LAN gateway is currently not active.
>
> 688 The workstation is disconnected from the LAN.
>
> 689 A TRANSMIT or RECEIVE command from the LAN failed.
>
> 695 The workstation is off line from the control unit.
>
> Program Check messages
>
> In order to resolve Program Check PROG 7nn problems, press Reset and
try
> the operation again. If the problem persists, note the PROG message
number
> and consult your system administrator.
>
> For other PROG messages not listed, refer to the IBM 3270
Information
> Display System: Reference Summary .
>
> PROG 701 PC/3270 internal memory allocation failed while loading
the
> Program Symbols.
>
> PROG 705 An SNA message was received out of sequence.
>
>
> PROG 706 An SNA message was received with incorrect chaining.
>
> PROG 707 An SNA message was received with incorrect
bracketing.
>
> PROG 708 An SNA message was received before Data Traffic was
started.
>
> PROG 709 An SNA message was received that violated half-duplex
protocol.
>
> PROG 711 An SNA BIND command was received when the logical terminal
was
> already bound to a different session.
>
> PROG 713 An SNA BIND command was received when the logical terminal
was
> already bound to the same session..
>
>
> PROG 714 An SNA message was received before the session was bound.
>
> PROG 715 An SNA message was received before the session was
activated.
>
> PROG 716 An SNA BIND command was received with an incomplete
parameter
> list.
>
> PROG 717 An SNA BIND command that specified incorrect FM or TS
profiles
> was received.
>
> PROG 718 An SNA BIND command that specified an incorrect primary
protocol
> was received.
>
>
> PROG 719 An SNA BIND command that specified an incorrect secondary
> protocol was received.
>
> PROG 720 An SNA BIND command that specified an incorrect common
protocol
> was received.
>
> PROG 723 An SNA BIND command that specified an incorrect LU type was
> received.
>
> PROG 724 An SNA BIND command that specified an incorrect screen
size was
> received.
>
> PROG 725 An SNA BIND command that specified cryptography was
received.
>
>
> PROG 726 An SNA inbound message was rejected. (3270 session)
>
> PROG 726 While checking security, an error occurred. (5250 session)
>
>
> · Partner LU rejected the specified user ID or password.
> · Partner LU rejected the communication allocation request, because
it
> could not start the TP (DDM Synchronous Conversations).
> · Before APPC allocated the communication, an internal SNA protocol
error
> occurred.
> · Because of a temporary failure, the partner node deactivate the
session
> while allocation.
>
>
>
> User Response:
>
> · When you mistakenly type the user ID or password, the Logon panel
is
> displayed again. Type it again.
> · If you execute the IPL for AS/400 after the session is built, this
> message is displayed. When retry for the link level ends normally,
the
> Sign-on
> panel appears. Wait until it appears.
> · For other cases, disconnect the communication, and then connect it
> again.
>
>
>
> PROG 727 An outbound message was destroyed.
>
> PROG 728 A read command error has occurred for one of the following
> reasons:
>
> · The SNA message carrying a read command did not contain a change
> direction indicator (CDI).
> · Either an end-of-chain indicator (ECI) or the end-of-bracket
indicator
> (EBI) was on.
>
>
>
> PROG 729 A READ PARTITION command was received while the
workstation was
> in retry state.
>
> PROG 731 An SNA BIND command that specified invalid inbound RU size
and
> pacing count was received.
>
> PROG 732 An SNA BIND command that specified invalid outbound RU
size and
> pacing count was received.
>
> PROG 735 An exception was detected while compressing or
decompressing
> RUs.
>
> PROG 750 An invalid 3270 command was received.
>
>
> PROG 751 A START FIELD EXTENDED, MODIFY FIELD, or SET ATTRIBUTE
order
> that specified an invalid character set was received.
>
> PROG 752 A SET BUFFER ADDRESS, REPEAT TO ADDRESS, or ERASE
UNPROTECTED TO
> ADDRESS order that specified an invalid address was received.
>
> PROG 753 One or more of the following conditions occurred:
>
> * A READ MODIFIED, READ MODIFIED ALL, or READ BUFFER command that
also
> contained data was received.
>
>
> * A REPEAT TO ADDRESS or GRAPHIC ESCAPE order that specified an
invalid
> character set was received.
>
> * A START FIELD EXTENDED, MODIFY FIELD, or SET ATTRIBUTE order that
> specified an invalid attribute value or character set was received.
>
> PROG 754 One of the following commands was received without
required
> parameters:
>
> * SE
T BUFFER ADDRESS
> * REPEAT TO ADDRESS
> * ERASE UNPROTECTED TO ADDRESS
> * START FIELD
> * START FIELD EXTENDED
>
> * MODIFY FIELD
> * SET ATTRIBUTE
> * GRAPHIC ESCAPE
>
> PROG 755 Invalid character code was received.
>
> PROG 756 A WRITE STRUCTURED FIELD command was received with an
invalid
> structured field.
>
> PROG 757 Load PS Structured Field error: an invalid Load PS Type
was
> specified.
>
> PROG 758 A SET REPLY MODE command was received with an invalid
mode.
>
> PROG 759 A WRITE STRUCTURED FIELD command was received with an
invalid
> structured field length.
>
>
> PROG 760 A WRITE STRUCTURED FIELD command was received with
reserved
> fields not zero.
>
> PROG 761 A WRITE STRUCTURED FIELD command was received with invalid
> partition identifier.
>
> PROG 762 A CREATE PARTITION STRUCTURED FIELD command was received
with
> invalid parameter.
>
> PROG 764 Load PS STRUCTURED FIELD error: An invalid slot number was
> specified.
>
> PROG 765 Load PS STRUCTURED FIELD error: An invalid code point was
> specified.
>
>
> PROG 766 Load PS STRUCTURED FIELD error: Length or format of the PS
data
> is invalid.
>
> PROG 767 A CREATE PARTITION STRUCTURED FIELD command was received
with
> invalid parameter.
>
> PROG 768 Load PS STRUCTURED FIELD error: Error in Load PS extension
> field.
>
> PROG 769 Load PS STRUCTURED FIELD error: Non-zero was specified in
> reserved area.
>
> PROG 771 A WRITE STRUCTURED FIELD command was received with an
invalid
> STRUCTURED FIELD command.
>
>
> PROG 780 Internal message was received with incorrect direction.
>
> PROG 797 SO was received. But SO/SI are not paired correctly.
>
> PROG 798 SO/SI or GRAPHIC ESCAPE was received in DBCS field.
>
> PROG 799 One or more of the following conditions occurred:
>
> * Address points second byte of DBCS character.
>
> * Invalid character attribute in DBCS sub-field.
>
> * Invalid STOP address.
>
> * General DBCS error.
>
>
> Where can I find out what PROG750 means for a TN3270 session?
>
>>>
----------------------------------------------------------------------
Phil Smith III
>That is the manual. Cool, thanks. Looks like my issue is 750
>'Incorrect command received'.
Yes, it basically means a bad 3270 data stream. Get a datastream trace and take it apart (no, that won't be fun if you haven't done it before, alas; I do know someone with good tools for doing so if it comes to that, but I doubt he'd do it for free).
...phsiii
Chris Mason
A stimulating question!
The first thing to say is that this was also posed on the CICS list but - despite
an unexplained hint in the "solution" - this concerns the 3270 in general and so
is probably best dealt with in the IBM-MAIN list.
So that's the first point since this error code belongs to the 3270 topic in
general and not just TN3270.
Being finicky, another aspect I can deal with straight away is that it is strictly
inappropriate to imply that a TN3270 emulator - for this concerns a TN3270
client emulator - operates a "session" but rather a TN3270 *connection*
which can be concatenated to a real SNA *session* at a TN3270 server.[1]
I thought I remembered from long ago using a regular 3270 manual for these
codes but I just could not remember which one it was. I thought it might have
been the "3174 Establishment Controller Functional Description", of which the
GA23-0218-11 can be found in the IBM pages:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/cn7a7003/
However, the closest you can get in this manual is "APPENDIX1.5.1 Operator
Information Area Symbols", "Do Not Enter (Input Inhibited), Locations 9
through 17:":
<quote>
PICTURE 163
Program Check
A programming error was detected in the data received by the controller. This
symbol is accompanied by up to three digits, nnn, that define the probable
cause of the problem.
</quote>
"PICTURE 163" appears roughly as "[X PROGnnn]".
I can find nowhere in the manual a description of what these "up to three
digits", specifically 750, might be. Probably this is where, long ago, when I
used to make sure that "flesh and blood" versions of the latest manuals I
might possibly need were to hand, that I found the other "3270" manual that
actually divulged what the codes might mean. None of the manuals I was
inspired to check, ephemeral versions of which exist in the bit-sphere, helped!
Dead end!
Then I remembered that "Google was my friend" - and could have been your
friend - and tried "PROG 750 3270" - with actually the same substantive result
using "PROG 750 TN3270".
This yielded the following as the first - PROG 750 3270 - or the second - PROG
750 TN3270[2] - hit:
http://publib.boulder.ibm.com/infocenter/hodhelp/v9r0/index.jsp?
topic=/com.ibm.hod9.doc/doc/troubleshoot/oia.html
<quote>
Understanding the OIA
Program messages (columns 9-17) (3270, CICS, and 5250)
This message accompanies the X in column 9 and explains why input is
inhibited.
...
X Prog xxx There is an error in the data stream sent from the host. The xxx
defines the probable cause of the problem.[3]
...
Prog 750
A 3270 command was received that is not valid.
...
</quote>
"Host On-Demand", who'd 'a' thought it?
So, the first character of data outbound to the - in your case - TN3270 client
3270 display emulator, the command character, is not correct.
There are actually very few command characters from which to choose.
Finally I found a use for the "3174 Establishment Controller Functional
Description" manual:
<quote>
| Table 2-1. Write and Erase Command
Codes |
|_________________________________ ________________
_________________ ________ __________|
| | Local | Remote | | |
| | Attachment | Attachment | ASCII
| |
| Command | EBCDIC (Hex) | EBCDIC (Hex) | (Hex) |
Graphic |
|_________________________________|________________|______________
___|________|__________|
| Write | 01 | F1 | 31 | 1 |
|_________________________________|________________|______________
___|________|__________|
| Erase/Write | 05 | F5 | 35 | 5 |
|_________________________________|________________|______________
___|________|__________|
| Erase/Write Alternate | 0D | 7E | 3D |
= |
|_________________________________|________________|______________
___|________|__________|
| Erase All Unprotected | 0F | 6F | 3F | ?
|
|_________________________________|________________|______________
___|________|__________|
| Write Structured Field | 11 | F3 | NA | 3
|
|_________________________________|________________|______________
___|________|__________|
| Table 2-10. Read Command Codes |
|_______________________ ____________ ___________ ___________
___________|
| | L Units | R Units | | |
| | EBCDIC | EBCDIC | ASCII | |
| Command | (Hex) | (Hex) | (Hex) | Graphic |
|_______________________|____________|___________|___________|____
_______|
| Read Buffer | 02 | F2 | 32 | 2 |
|_______________________|____________|___________|___________|____
_______|
| Read Modified | 06 | F6 | 36 | 6 |
|_______________________|____________|___________|___________|____
_______|
| Read Modified All | 6E | 6E | 3E | : |
| (SNA only) | | | | |
|_______________________|____________|___________|___________|____
_______|
</quote>
So, unlike the misplaced alarms raised by one of your responders, this is not at
all going to be a difficult matter to resolve. The problem lies with the very first
character which TN3270 maps to the beginning of at outbound 3270 data
stream at the point of failure. The only "tools" you'll need are your eyes and
your brain - which come at no extra charge!
-
At this point I checked all the other responses in more detail and - lo and
behold! - Bob Botsis identified the manual I was talking about above -
promptly downloaded for future reference. It just might have helped if he'd
given the title and the minimal URL so I'd have spotted it on my initial scan.
Also giving all the codes was a bit of "overkill" since that obscured his
success!!!
3174 Establishment Controller Status Codes, GA27-3832-08
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23
Note - to Bob really - if you skip everything after the internal manual number
or section number, everything *after* and including the question mark, you
can often get the URL on one line.
Chris Mason
[1] Alternatively the TN3270 server - as in an OSA ICC - could be emulating a
pre/non-SNA 3270 controller and an SNA session may not actually be involved.
Actually I noticed that the 3174 manual pretends a "session" is involved when
discussing error codes although that is not necessarily the case, so I expect
we have to just live with the potential ambiguities of this sort of approximate
terminology.
[2] The first doesn't count for obvious reasons!
[3] And at least this text was written before it became fashionable to hide
a "problem" behind the word "issue" - or worse, "issues". I could just imagine
that today "... probable cause of the problem" would become "... probable
cause of the issue" - yuk!
Incidentally I always feel a little uncomfortable with the expression "probable
cause", famous as far as I am concerned in its use in network management
architecture. A quick look in Wikipedia explains why! I was once logically
arrested in California and the "probable cause" was the officer's speeding
detector!
On Sun, 30 May 2010 20:08:50 -0600, Frank Swarbrick
<frank.s...@EFIRSTBANK.COM> wrote:
>Where can I find out what PROG750 means for a TN3270 session?
>
>--
>
>Frank Swarbrick
>Applications Architect - Mainframe Applications Development
>FirstBank Data Corporation - Lakewood, CO USA
>P: 303-235-1403
----------------------------------------------------------------------
Ed Finnell
In a message dated 5/31/2010 9:51:21 A.M. Central Daylight Time,
chris...@BELGACOM.NET writes:
A stimulating question!
The first thing to say is that this was also posed on the CICS list but -
despite
an unexplained hint in the "solution" - this concerns the 3270 in general
and so
is probably best dealt with in the IBM-MAIN list
>>
Somewhere along the way I put in a Checklist to reassemble custom modetabs
and USSTABs.
One thing to try might be a shipped logmode in ISTINCLM. If you can get
past the Network Solicitor ===>logon applid(CICSTEST) LOGMOD(D4C32xxC) or
something you can live with.
Mike W Stayton
See "IP Diagnosis" for details
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1C590/2.1.4.5.2
CTRACE COMP(SYSTCPDA) OPTIONS((FULL TELNET(23, DETAIL) ))
Change 23 to the telnet server port. Add any additional selection
keywords.
Sample output:
TCP
Source Port : 23 (telnet) Destination Port: 4159 ()
Sequence Number : 3477007056 Ack Number: 1122097700
Header Length : 20 Flags: Ack Psh
Window Size : 32750 CheckSum: 58BA E7BD Urgent Data
Pointer: 0000
Telnet: 1111
0000 HDR 3270 data stream Send Sense Sequence: 3
0005 OUT Erase/Write F5C3 Restore Reset
0007 1 1 SBA 4040 Row: 1 Col: 1
000A 1 1 RA 404040 Row: 1 Col: 1 Char: 40
000E 1 1 SBA 4040 Row: 1 Col: 1
0011 1 1 SF E8 P D White
0013 1 2 080 "------------------------------- TSO/E LOGON
-----------------------------
0063 2 2 SBA C150 Row: 2 Col: 1
0066 2 1 SF E8 P D White
0068 2 2 080 "
00B8 3 2 SBA C260 Row: 3 Col: 1
00BB 3 1 SF E8 P D White
00BD 3 2 080 "
010D 4 2 SBA 5B60 Row: 23 Col: 1
0110 23 1 SF E8 P D White
0112 23 2 079 "PF1/PF13 ==> Help PF3/PF15 ==> Logoff PA1 ==>
Attention PA2 ==>
0161 24 1 SBA 5CF0 Row: 24 Col: 1
0164 24 1 SF E8 P D White
0166 24 2 078 "You may request specific help information by entering
a '?' in any entry
01B4 24 80 SBA C3F3 Row: 4 Col: 4
.
.
.
Orders: 95, Size: 229, Data: 96, Size: 873
Print Screen from Row 1 to 24
===============================================================================
@------------------------------- TSO/E LOGON
----------------------------------
@
@
@Enter LOGON parameters below: @RACF LOGON parameters:
Mike Stayton
z/OS Communications Server
919 254-5057 T/L 444
m...@us.ibm.com
Client success extends to the way we anticipate what our clients want,
need and dream of ... Sam J Palmisano
Event if you're on the right track, you'll get run over if you just sit
there -- Will Rogers
From:
Phil Smith III <li...@AKPHS.COM>
To:
IBM-...@bama.ua.edu
Date:
05/30/2010 11:26 PM
Subject:
Re: PROG750
Sent by:
IBM Mainframe Discussion List <IBM-...@bama.ua.edu>
Chris Mason
Regarding the possible influence of mode table entries:
PROG750 concerns the initial command byte in the outbound 3270 data
stream - the "Erase/Write" In Mike Stayton's trace sample[1]. I wondered if it
might be possible that the presentation services field in some mode table
entries could, in effect, say that only a subset of possible commands would be
used. An example might be that the "Erase/Write Alternate" command is
somehow forbidden if the penultimate byte in the presentation services field is
not a particular value. Well, this isn't the case. If the mode table entry is such
that there is no provision for two sets of presentation space dimensions, only
one set of dimensions is used whether the "erase/write" command
is "Erase/Write" or "Erase/Write Alternate".
Thus I don't see any possible error due to the presentation services field of
the mode table entry.
Regarding the possible influence of Unformatted System Services (USS) table
message definitions:
It is indeed possible to "make a mess" with an USS table, whether or not the
TN3270 server is involved. This is because messages built with the BUFFER
operand of the USSMSG macro need to specify a valid 3270 data stream from
beginning to end - not that the end offers any special considerations.
However, if what you had before worked as desired, you need to ask what
changed. Also, you'd be very well aware of whether it was an USS message of
something - presumably - CICS was doing by noting the stage in the TN3270
connection that the problem arose.
Did you have any other effect in mind ?
Chris Mason
[1] Which, of course makes it very easy to find and, presumably, since the
trace is kind enough to *interpret* the data stream, the trace would be
obliged to throw its hands in the air and, in effect, say something on the lines
of "New one on me, mate!" but probably expressed dryly as "Unknown
command byte".
On Mon, 31 May 2010 11:47:00 EDT, Ed Finnell <Efinn...@AOL.COM> wrote:
>
>In a message dated 5/31/2010 9:51:21 A.M. Central Daylight Time,
>chris...@BELGACOM.NET writes:
>
>A stimulating question!
>
>The first thing to say is that this was also posed on the CICS list but -
>despite
>an unexplained hint in the "solution" - this concerns the 3270 in general
>and so
>is probably best dealt with in the IBM-MAIN list
>
>>>
>Somewhere along the way I put in a Checklist to reassemble custom
modetabs
>and USSTABs.
>One thing to try might be a shipped logmode in ISTINCLM. If you can get
>past the Network Solicitor ===>logon applid(CICSTEST) LOGMOD(D4C32xxC)
or
>something you can live with.
----------------------------------------------------------------------
Linda Mooney
I use Attachmate Extra and can produce a PROG750 easily. I have a bunch of sessions defined, several for each of my LPARS, some with specific sized screens within the emulator. I typically use log tso,s3270r4q to log on. If I happen to do that on a session I have defined in the emulator as a fixed screen size of any other screen size, I get the PROG750. Our logmode table is set up to default to a mod2 screen size, but accepts any setting at logon for which there is a entry.
HTH,
Linda Mooney
----- Original Message -----
From: "Frank Swarbrick" <frank.s...@EFIRSTBANK.COM>
To: IBM-...@bama.ua.edu
Sent: Sunday, May 30, 2010 8:00:22 PM GMT -08:00 US/Canada Pacific
Subject: Re: PROG750
That is the manual. Cool, thanks. Looks like my issue is 750
'Incorrect command received'.
Makes "sense". It's definitely a 3270 emulator issue with our "screen
scraping" product. This is our first day on z/OS in production and
while there were some other issues this is one i've been working on for
four hours. Think I'm getting a handle on it, in any case.
Thanks!
Frank
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
On 5/30/2010 at 8:48 PM, in message <9e61a.19602...@aol.com>,
<Rbo...@AOL.COM> wrote:
> Here's a link to some. I've also included others which include ones
from
> the link:
>
> _http://publibz
>
.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23?SHELF=EZ2HW125&DT=1
> 9940419144012_
>
(http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23?SHE
> LF=EZ2HW125&DT=19940419144012)
>
> Input Inhibit Indicators
>
> Input Inhibited (Columns 9-17) This message accompanies the X in
column 9,
> and explains why input is inhibited.
>
>
>
> Where can I find out what PROG750 means for a TN3270 session?
>
> --
>
> Frank Swarbrick
> Applications Architect - Mainframe Applications Development
> FirstBank Data Corporation - Lakewood, CO USA
> P: 303-235-1403
>
>
>>>>
>
>>>
----------------------------------------------------------------------
Mark T. Regan, K8MTR
�
Thanks,
�
Mark Regan
Zaromil Tisler
>Anyone know where I can lookup info about this 3270 error code, prog695?
The tn3270 client vendor does not supply any info about it nor has any
Google or IBMLink search turned up anything.
�
If it is the same code and meaning as in IBM PersComm, then maybe you can
find this description useful (found it in Help ---> Communication Check
messages):
695 The workstation is off line from the control unit.
--
Zaromil
Mark T. Regan, K8MTR
�
Thanks,
Mark Regan
________________________________
From: Zaromil Tisler <zaromil...@CHELLO.AT>
To: IBM-...@bama.ua.edu
Sent: Tue, June 1, 2010 6:18:46 AM
Subject: Re: PROG695 (Was Re: PROG750)
Frank Swarbrick
ANyway, I can't recall what I googled on yesterday, but "prog 750 3270" does indeed get some good stuff.
Anyway, while the manual implies it is an application issue (Prog 750: A 3270 command was received that is not valid.) it appears to me to be more likely that a valid 3270 command is being sent and the emulator simply isn't understanding it, or handling it properly. So it is electing to do the PROG750.
Anyway, we have some traces of both a good and bad result from the same basic sequence of events, and we've sent them to the vendor. So we shall see.
It appears that the host is sending (or the emulator is interpreting it as) two back to back 3270 streams; one being "large" (1302 bytes) and one being small (13 bytes). If it helps I will most them here (in hex, of course):
01 00 FF 02 00 00 00 00 01 00 FF F5 C1 11 4C E2 13 11 40 40 1D F0 E3 D9 C1 D2 11 40 50 1D F0 F2 F4 60 C8 D6 E4 D9 40 C2 C1 D5 D2 C9 D5 C7 1D F0 C3 C1 D3 D3 40 E3 D9 C1 C3 D2 C9 D5 C7 40 E2 E8 E2 E3 C5 D4 40 11 C2 E5 1D F8 E7 1D F8 C1 D4 C2 C5 D9 40 C4 40 C2 D6 E8 D3 C5 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 F1 F1 F1 60 F6 F0 60 F9 F0 F4 F6 11 C3 F5 1D 7C 6D 1D 7C 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 11 C5 C5 1D 7C 6D 1D 7C 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 11 C6 D5 1D 40 6D 1D F8 C4 C5 D4 C1 D5 C4 40 40 40 40 F4 F2 F1 40 F2 F9 F8 60 F1 F4 F3 F2 40 40 40 40 40 C1 D9 C1 D7 40 40 40 40 1D F0 C2 D9 C1 D5 C3 C8 40 E3 D6 40 C2 C9 D3 D3 7A 1D 40 F4 F2 F1 1D 40 C1 D9 C1 D7 40 40 1D F0 11 C7 E5 1D 7C 6D!
1D F0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 1D F0 C1 C3 C3 D6 E4 D5 E3 40 E3 D6 40 C2 C9 D3 D3 7A 1D 40 F4 F2 F1 1D 40 F2 F9 F8 60 F1 F4 F3 F2 1D F0 11 C8 F5 1D 7C 6D 1D F0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 1D F0 E6 C1 C9 E5 C5 40 C1 C3 C3 D6 E4 D5 E3 40 C3 C8 C1 D9 C7 C5 40 4D E8 61 D5 5D 7A 1D 40 D5 1D F0 11 4A 6B 1D F0 D6 D7 C5 D9 C1 E3 D6 D9 40 C9 D5 C9 E3 C9 C1 D3 E2 7A 1D F0 C1 C2 D7 1D F0 11 4B 50 1D F0 C9 D5 C4 C9 C3 C1 E3 C5 40 E2 C5 D9 E5 C9 C3 C5 4D E2 5D 40 D7 D9 D6 E5 C9 C4 C5 C4 7A 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 11 4C 61 1D 40 6D 1D F0 C2 C1 D3 C1 D5 C3 C5 40 C9 D5 D8 E4 C9 D9 E8 40 1D 40 6D 1D F0 C4 C5 D7 61 E6 C4 61 C1 E3 D4 40 C9 D5 C6 D6 40 1D 40 6D 1D F0 E3 C5 D3 C5 D7 C8 D6 D5 C5 40 E7 C6 C5 D9 40 40 1D 40 6D 1D F0 D7 C5 D5 C4 C9 D5 C7 40 C1 E4 E3 C8 E2 40 40 40 11 4F C1 1D 40 !
6D 1D F0 C1 C3 C8 40 C9 D5 D8 E4 C9 D9 E8 40 40 40 40 40 1D 40 6D 1D F
0 C8 D6 E4 D9 E2 61 D3 D6 C3 C1 E3 C9 D6 D5 E2 40 1D 40 6D 1D F0 D4 C9 E2 C3 C5 D3 D3 C1 D5 C5 D6 E4 E2 40 40 40 1D 40 6D 1D F0 E6 C9 D9 C5 40 C9 D5 C6 D6 40 40 40 40 40 40 40 11 50 D1 1D 40 6D 1D F0 C1 C4 C4 D9 C5 E2 E2 40 C3 C8 C1 D5 C7 C5 40 40 1D 40 6D 1D F0 C9 D5 E3 C5 D9 D5 C5 E3 40 E2 E5 C3 E2 40 40 40 1D 40 6D 1D F0 D5 C5 E6 40 C1 C3 C3 E3 40 C9 D5 D8 E4 C9 D9 E8 1D 40 6D 1D F0 E7 C6 C5 D9 40 E3 D6 40 C2 C1 D5 D2 40 40 40 40 11 D1 61 1D 40 6D 1D F0 C2 C1 D3 C1 D5 C3 C9 D5 C7 40 C3 C8 D2 C2 D2 40 1D 40 6D 1D F0 D3 D6 C1 D5 40 C9 D5 C6 D6 40 40 40 40 40 40 40 1D 40 6D 1D F0 D5 C5 E6 40 D3 D6 C1 D5 40 C9 D5 D8 E4 C9 D9 E8 1D 40 6D 1D F0 E7 C6 C5 D9 40 E3 D6 40 E5 D9 E4 40 40 40 40 40 11 D2 F1 1D 40 6D 1D F0 C3 C1 E2 C8 40 D9 E2 D9 E5 C5 40 C9 D5 C6 D6 40 1D 40 6D 1D F0 D3 61 E2 E3 40 C3 C8 C5 C3 D2 C2 D6 D6 D2 40 40 1D 40 6D 1D F0 D5 E2 C6 40 C9 D5 D8 E4 C9 D9 E8 40 40 40 40 40 11 D4 C1 1D 40 6D 1D F0 C3 C8 C5 C3 D2 40 D6 D9 C4 C5 D9 40 40 40 40 40 1D 40 6D 1D F0 D3 61 !
E2 E3 40 C3 C3 61 C1 E3 D4 40 40 40 40 40 1D 40 6D 1D F0 D7 C8 D6 E3 D6 40 D9 C5 D8 E4 C5 E2 E3 40 40 40 11 D5 D1 1D 40 6D 1D F0 C3 D9 C5 C4 C9 E3 40 C3 C1 D9 C4 40 C9 D5 C6 D6 1D 40 6D 1D F0 D4 C5 D9 C3 C8 C1 D5 E3 40 D5 C1 D4 C5 40 40 40 1D 40 6D 1D F0 E2 D7 C1 D5 C9 E2 C8 40 C3 C1 D3 D3 40 40 40 40 11 D6 61 1D 40 6D 1D F0 C6 C5 C5 E2 61 E2 E5 C3 E2 40 C9 D5 C6 D6 40 40 1D 40 6D 1D F0 D4 C5 D9 C3 C8 C1 D5 E3 40 E5 C5 D9 C9 C6 E8 40 1D 40 6D 1D F0 E2 E3 D6 D7 40 D7 C1 E8 D4 C5 D5 E3 40 40 40 40 11 D9 C4 1D F0 C3 D6 D4 D4 C5 D5 E3 E2 7A 1D 40 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 6D 40 40 40 40 40 40 40 40 40 11 5A C7 1D C1 40 1D F0 11 5B 60 1D 7C D3 D6 C7 40 C3 C1 D3 D3 40 C6 D6 D9 40 C1 D5 D6 E3 C8 C5 D9 40 C1 C3 C3 D6 E4 D5 E3 6F 40 4D E8 61 D5 5D 1D 7C D5 1D F0
followed by
01 00 FF 01 90 40 00 00 01 01 00 F1 C2
the "Screen" that the first stream represents looks something like this:
HOME ENTITY
USER ID: ABP
LOCATION: FBDCWS
FUNCTION: trackcall
ACCOUNT: 4212981432
CUSTNAME: 111609046
BRANCH:
AMOUNT:
SERIAL:
ACTION:
APPL:
With the PROG750 appearing in the "information area" at the bottom.
We had a similar issue with the vendor and its TN3270E protocol, so I'm thinking there might be a similar cause here. On VSE the TN3270 server only supported partial TN3270E and "backed off" to TN3270 after the LU was negotiated using TN3270E, so 99% of the traffic was not in TElnet Extended mode. We may try backing down to regular TN3270 and see if this mitigates the issue.
Thanks!
Frank
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
On 5/31/2010 at 8:50 AM, in message
<LISTSERV%20100531095...@BAMA.UA.EDU>, Chris Mason
>>>
The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.
----------------------------------------------------------------------
Frank Swarbrick
--
Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403
>>That is the manual. Cool, thanks. Looks like my issue is 750
>>'Incorrect command received'.
>
> Yes, it basically means a bad 3270 data stream. Get a datastream trace and
> take it apart (no, that won't be fun if you haven't done it before, alas;
> I do know someone with good tools for doing so if it comes to that, but I
> doubt he'd do it for free).
>
> ...phsiii
>
Chris Mason
> Anyone know where I can lookup info about this 3270 error code, prog...?
The answer to the slightly generalised question above is that the answer was
provided in this very same thread approximately 16 hours before this post and
a day before in an identically titled thread in the CICS-L list - assuming I can
manage the time codes correctly!
>...> 3174 Establishment Controller Status Codes, GA27-3832-08
>...> http://publibz.boulder.ibm.com/cgi-
bin/bookmgr_OS390/BOOKS/CN7S8001/2.23
However, as Zaromil Tisler pointed out - and as you would have been able to
work out from the manual referenced above, PROG695 does not feature -
carefully chosen words - as a 3270 status code.
However the section 1.4, "3174 Status Code Chart" includes the following:
<quote>
6XX 1xHG B1
Description: Distributed function terminal detected permanent errors.
B1 = The distributed function terminal (DFT) error log qualifier.
Alert Sent = Permanent.
Possible Cause: N/A
User Action: For a description of the qualifier, refer to your terminal
documentation concerning problem determination.
For Service Personnel Only: No action is required.
6XX 5xHG B1
Description: Distributed function terminal detected temporary errors.
B1 = The distributed function terminal (DFT) error log qualifier.
Alert Sent = Temporary.
Possible Cause: N/A
User Action: For a description of the qualifier, refer to your terminal
documentation concerning problem determination.
For Service Personnel Only: No action is required.
</quote>
This may be the origin of the contention made by our own John McKown in a
post in the thread in the CICS-L list where he states that the codes depend
on the implementation and are not generalised. Thus, in these cases, it is
necessary to "refer to your terminal documentation concerning problem
determination".
-
As regards searching for the problem, if you use "695 error 3270" in the IBM
site search, the 12th hit would be "ITSO Personal Communications V4.x
Interoperability and Problem Determination May 1995", GG24-4457-00, which
contains the following in section 11.7.3, "Special Considerations":
<quote>
Therefore you will be unable to connect to the host and Communications Error
695 (COMM 695) is displayed in the OIA.
</quote>
But I guess there's a considerable gulf between a search where you *might*
find the answer and one where you *should* find the answer - having already
been told what it is!
Chris Mason
On Tue, 1 Jun 2010 02:56:38 -0700, Mark T. Regan, K8MTR <netsfw-
ibm...@YAHOO.COM> wrote:
>Anyone know where I can lookup info about this 3270 error code, prog695?
The tn3270 client vendor does not supply any info about it nor has any Google
or IBMLink search turned up anything.
�
Thanks,
�
Mark Regan
Chris Mason
> I typically use log tso,s3270r4q to log on.
"s3270r4q" is not one of the mode table entries provided in ISTINCLM so we'll
all be in the dark over what significance it may have.
The 3174 Establishment Controller Status Codes manual
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23
is quite clear that PROG750 applies only to unrecognised *command* codes,
which is an incorrect initial outbound byte. I checked that other possible
errors in the 3270 data stream were covered by other codes and indeed they
are.[1]
If you have mismatched presentation space dimensions, say 24x80 ("model 2")
rather than 43x80 ("model 4") or vice versa, this should not faze the
3270 "client" in any way. You will observe either lack of use of the bottom
19 "rows" or "wrapping". It only gets really messy - but not troubling for the
emulator - if you have a mismatch involving 27x132 ("model 5"). If the
emulator *does* have trouble, it is at fault in not following 3270 architecture.
If you post both of the mismatching mode table entries, it may be possible to
see if there is a difference other than presentation space dimensions which
could help explain why the "command" character is rejected by the emulator.
Note, for example that in Tables 2-1 and 2-10 I posted before that the "Local"
and "Remote" codes are different.
You may also like to state how you know that you have supplied the correct
mode table entries. The case where you supply it on the "logon" command is
clear enough, but the "by default" can be tricky. Assuming you are using the
z/OS Communications Server IP TN3270 server, you use the TELNETDEVICE
statement in order to specify the name of the mode table entry, actually or by
default, unless you specify NONE - obviously not ever expected to be the
name of a mode table entry! - when the DLOGMOD operand of the "secondary"
APPL statement will apply. I have seen folk assume that the latter applies
irrespective of what the TELNETDEVICE statement specifies.
Chris Mason
[1] It was interesting to note that "WCC with Error" was code 795, the
penultimate code, when you might expect it to be 751 since the WCC byte
immediately follows the "command" byte. There is a possible, indeed likely,
explanation for the "late" appearance of a detectable WCC error which
requires a knowledge of the evolution of the "3270 byte".
On Tue, 1 Jun 2010 07:40:35 +0000, Linda Mooney
<Linda....@COMCAST.NET> wrote:
>Hi Frank,
>
>
>
>I use Attachmate Extra and can produce a PROG750 easily. I have a bunch
of sessions defined, several for each of my LPARS, some with specific sized
screens within the emulator. I typically use log tso,s3270r4q to log on. If
I happen to do that on a session I have defined in the emulator as a fixed
screen size of any other screen size, I get the PROG750. Our logmode table is
set up to default to a mod2 screen size, but accepts any setting at logon
for which there is a entry.
>
>
>
>HTH,
>
>
>
>Linda Mooney
----------------------------------------------------------------------
Don Williams
similar to IBM description of it in:
http://publib.boulder.ibm.com/infocenter/hodhelp/v9r0/index.jsp?topic=/com.i
bm.hod9.doc/doc/troubleshoot/oia.html
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Linda Mooney
In the case that I was talking about, the mismatch is with the user set definition within Attachmate and the user entered information at logon time. The version of Attachmate that I use (not in the office today so I can't check) allows the user to set mod2, mod3, mod4, mod5, and any. So, if I enter log tso,s3270r4q on an Attachmate session that is defined within Attachmate to be anything other than any or mod4, the result is a PROG750 and no TSO session. My session attempt being stopped before reaching my z/OS system. If I enter the same log command on an Attachmate screen that has been defined within Attachmate as mod4 or any, I get a mod 4 session logon.
From Frank's post, I thought it might be possible that the issue could be a mismatch like the one I described and, if so, an easy fix. I seldom use the Attachmate 'any' setting . Even though that would allow more flexibility, I don't like the way it sizes the screen. I can't fix the font size I like or the placement on my dual monitor PC that I like. I have heard that
S3270r4q is a mod 4 session with 7 color support, at least that is what it is on my system. There is an entry for s3270r2q, 2, 4 and 5 in our mode table. Using other emulators, I have seen the behavior you described - blank lines at the bottom and so forth. On a real 3279, logged on as a mod2 will also display the blank lines at the botom of the screen.
As for how I know what our default is - the Network sysprog who set it up told me so. Also, if I log on with log tso, I get a mod2 TSO session.
HTH,
Linda Mooney
----- Original Message -----
From: "Chris Mason" <chris...@BELGACOM.NET>
To: IBM-...@bama.ua.edu
Sent: Tuesday, June 1, 2010 9:21:28 AM GMT -08:00 US/Canada Pacific
Subject: Re: PROG750
Linda
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CN7S8001/2.23
Chris Mason
>Hi Frank,
>
>
>
>I use Attachmate Extra and can produce a PROG750 easily. I have a bunch
of sessions defined, several for each of my LPARS, some with specific sized
screens within the emulator. I typically use log tso,s3270r4q to log on. If
I happen to do that on a session I have defined in the emulator as a fixed
screen size of any other screen size, I get the PROG750. Our logmode table is
set up to default to a mod2 screen size, but accepts any setting at logon
 for which there is a entry.Â
>
>
>
>HTH,
>
>
>
>Linda Mooney
Chris Mason
The first 11 bytes of the trace are *not* 3270 data stream. I guess if I did
some research I could work out what it was. I expect there's some TN3270E
prefix I should check into but that will need time and RFC 2355. From byte 12
onwards is familiar territory, fairly easy to "read" - although I haven't checked
every last byte to the end!
Note also that the second "record" has two - correct - 3270 bytes,
a "write" "command" and a "write control character" (WCC).
> We had a similar issue with the vendor and its TN3270E protocol, so I'm
thinking there might be a similar cause here. On VSE the TN3270 server only
supported partial TN3270E and "backed off" to TN3270 after the LU was
negotiated using TN3270E, so 99% of the traffic was not in TElnet Extended
mode. We may try backing down to regular TN3270 and see if this mitigates
the issue.
My understanding of RFC 2355 is that it is not possible to "change" ("back
off") the flavour of TN3270 protocols without restarting the TELNET
connection. Within any one TELNET connection, you can operate at the
TN3270 level as defined prior to TN3270E, meaning "TN3270E" not agreed, or
you can operate at the TN3270E level, meaning "TN3270E" agreed.
What you may have seen is "TN3270E" being proposed but rejected and hence
not agreed as in this sequence taken from the enormously useful sets of
sequences included in section 13.4, "Examples" of RFC 2355:
<quote>
The following example shows a TN3270E-capable server and a traditional
tn3270 client establishing a connection:
Server: IAC DO TN3270E
Client: IAC WON'T TN3270E
Server: IAC DO TERMINAL-TYPE
Client: IAC WILL TERMINAL-TYPE
Server: IAC SB TERMINAL-TYPE SEND IAC SE
Client: IAC SB TERMINAL-TYPE IS IBM-3278-2 IAC SE
Server: IAC DO EOR IAC WILL EOR
Client: IAC WILL EOR IAC DO EOR
Server: IAC DO BINARY IAC WILL BINARY
Client: IAC WILL BINARY IAC DO BINARY
(3270 data stream is exchanged)
</quote>
Note that the client can utter the word "TN3270E" not because it understands
it but because it has just heard it from the server, the client can thus
*pronounce* "TN3270E" it but doesn't like the sound of it!
You may find the following useful but I rather doubt it.
<quote>
TN3270E statement
Use the TN3270E parameter statement to allow TN3270E functions to be
negotiated by Telnet. If NOTN3270E is specified, all TN3270E functions, such
as printer support and client response, are disabled.
Telnet is initialized with a value of TN3270E.
The TN3270E and NOTN3270E statements can be coded in the
TELNETGLOBALS, TELNETPARMS, or PARMSGROUP statement block. See �Rules
for Telnet parameter statements and security parameters� on page 619 for
more information
about the hierarchy of parameter values.
The NOTN3270E value is useful in the unlikely case there are a significant
number of clients that cannot tolerate negotiating for a TN3270E connection.
Most clients do not have a problem with the TN3270E specification in the
server, but, in the unlikely case that some do, specify and map NOTN3270E to
that set of clients.
</quote>
Chris Mason
C1 D7 40 40 1D F0 11 C7 E5 1D 7C 6D 1D F0 40 40 40 40 40 40 40 40 40 40
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
1D F0 C1 C3 C3 D6 E4 D5 E3 40 E3 D6 40 C2 C9 D3 D3 7A 1D 40 F4 F2 F1 1D
40 F2 F9 F8 60 F1 F4 F3 F2 1D F0 11 C8 F5 1D 7C 6D 1D F0 40 40 40 40 40
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
40 40 40 40 40 1D F0 E6 C1 C9 E5 C5 40 C1 C3 C3 D6 E4 D5 E3 40 C3 C8 C1
D9 C7 C5 40 4D E8 61 D5 5D 7A 1D 40 D5 1D F0 11 4A 6B 1D F0 D6 D7 C5 D9
C1 E3 D6 D9 40 C9 D5 C9 E3 C9 C1 D3 E2 7A 1D F0 C1 C2 D7 1D F0 11 4B 50
1D F0 C9 D5 C4 C9 C3 C1 E3 C5 40 E2 C5 D9 E5 C9 C3 C5 4D E2 5D 40 D7 D9
D6 E5 C9 C4 C5 C4 7A 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
40 40 40 40 40 40 40 11 4C 61 1D 40 6D 1D F0 C2 C1 D3 C1 D5 C3 C5 40 C9
D5 D8 E4 C9 D9 E8 40 1D 40 6D 1D F0 C4 C5 D7 61 E6 C4 61 C1 E3 D4 40 C9
D5 C6 D6 40 1D 40 6D 1D F0 E3 C5 D3 C5 D7 C8 D6 D5 C5 40 E7 C6 C5 D9 40
40 1D 40 6D 1D F0 D7 C5 D5 C4 C9 D5 C7 40 C1 E4 E3 C8 E2 40 40 40 11 4F
C1 1D 40 6D 1D F0 C1 C3 C8 40 C9 D5 D8 E4 C9 D9 E8 40 40 40 40 40 1D 40
6D 1D F0 C8 D6 E4 D9 E2 61 D3 D6 C3 C1 E3 C9 D6 D5 E2 40 1D 40 6D 1D F0
D4 C9 E2 C3 C5 D3 D3 C1 D5 C5 D6 E4 E2 40 40 40 1D 40 6D 1D F0 E6 C9 D9
C5 40 C9 D5 C6 D6 40 40 40 40 40 40 40 11 50 D1 1D 40 6D 1D F0 C1 C4 C4
D9 C5 E2 E2 40 C3 C8 C1 D5 C7 C5 40 40 1D 40 6D 1D F0 C9 D5 E3 C5 D9 D5
C5 E3 40 E2 E5 C3 E2 40 40 40 1D 40 6D 1D F0 D5 C5 E6 40 C1 C3 C3 E3 40
C9 D5 D8 E4 C9 D9 E8 1D 40 6D 1D F0 E7 C6 C5 D9 40 E3 D6 40 C2 C1 D5 D2
40 40 40 40 11 D1 61 1D 40 6D 1D F0 C2 C1 D3 C1 D5 C3 C9 D5 C7 40 C3 C8
D2 C2 D2 40 1D 40 6D 1D F0 D3 D6 C1 D5 40 C9 D5 C6 D6 40 40 40 40 40 40
40 1D 40 6D 1D F0 D5 C5 E6 40 D3 D6 C1 D5 40 C9 D5 D8 E4 C9 D9 E8 1D 40
6D 1D F0 E7 C6 C5 D9 40 E3 D6 40 E5 D9 E4 40 40 40 40 40 11 D2 F1 1D 40
6D 1D F0 C3 C1 E2 C8 40 D9 E2 D9 E5 C5 40 C9 D5 C6 D6 40 1D 40 6D 1D F0
D3 61 E2 E3 40 C3 C8 C5 C3 D2 C2 D6 D6 D2 40 40 1D 40 6D 1D F0 D5 E2 C6
40 C9 D5 D8 E4 C9 D9 E8 40 40 40 40 40 11 D4 C1 1D 40 6D 1D F0 C3 C8 C5
C3 D2 40 D6 D9 C4 C5 D9 40 40 40 40 40 1D 40 6D 1D F0 D3 61 E2 E3 40 C3
>--
>
>Frank Swarbrick
>Applications Architect - Mainframe Applications Development
>FirstBank Data Corporation - Lakewood, CO USA
>P: 303-235-1403
----------------------------------------------------------------------