ISPF Errors with "Non Standard" Logmode

[George, Bill]

I've been 'playing' with different logmodes to find one I am comfortable
with.
I've notice a problem however. When ever I set a size that would display
more characters than a Logmode 5 would (27 x 132 = 3564), ISPF does not
recognize a cursor position beyond the 3564th character.

That is, if I where in an edit session and I entered or changed a character
beyond this point, say in row 40 of a 43 X 132 display, I receive an "**
ISPF screen output error - code = 32 **" error. If I were just attempting
to page up from that cursor position to place that line at the top of the
screen (Scroll=CSR) the display would page the full page as if it thinks the
cursor is on the command line.

Would this be an ISPF issue or an issue with my 3270 display emulator
(Bluezone by Renex)?

Thanks
Bill George

[Metz, Seymour]

Log/List Function keys Colors Environ Workstation Identifier Help

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ~SSSSSSSSSSSSSSSSSSSSSSSSSSS...
SSSSSSSSSSSSSSS
ISPISMMN 1 1. Environ settings...

Command ===> ?SSSSSSSSSSSSSSSSSSSSSSSSSSS-

Options Print Graphics

Enter "/" to select option Family printer type 2

Command line at bottom Device name . . . .

/ Panel display CUA mode Aspect ratio . . . 0

/ Long message in pop-up

Tab to action bar choices

Tab to point-and-shoot fields General

/ Restore TEST/TRACE options Input field pad . . N

/ Session Manager mode Command delimiter . ;

Jump from leader dots

/ Edit PRINTDS Command

/ Always show split line

Enable EURO sign

Terminal Characteristics

Screen format 1 1. Data 2. Std 3. Max 4. Part

Terminal Type 6 1. 3277 2. 3277A 3. 3278 4. 3278A

5. 3290A 6. 3278T 7. 3278CF 8. 3277KN

9. 3278KN 10. 3278AR 11. 3278CY 12. 3278HN

13. 3278HO 14. 3278IS 15. 3278L2 16. BE163

17. BE190 18. 3278TH

Log/List Function keys Colors Environ Workstation Identifier Help

S ~SSSSSSSSSSSSSSSSSSSSSSSSSSSS ISPF Settings
SSSSSSSSSSSSSSSSSSSSSSSSSSSS... SS
I ISPENVA ISPF ENVIRON Command Settings

C Command ===>

More: -

O

Terminal Tracing (TERMTRAC)

Enable . . . 3 1. Enable terminal tracing (ON)

2. Enable terminal tracing when a terminal error

is encountered (ERROR)

3. Disable terminal tracing (OFF)

DDNAME . . . ISPSNAP (DDNAME for TERMTRAC ON, ERROR, or DUMP.)

Terminal Status (TERMSTAT)

Enable . . . 1 1. Yes, invoke TERMSTAT immediately

2. Query terminal information

3. No

F1=Help F2=Split F3=Exit F7=Backward F8=Forward

F9=Swap F12=Cancel F13=Help F14=New F15=End

T F16=Return F17=Rfind F18=Rchange F19=Up F20=Down

F21=SwapList F22=Left F23=Right F24=Cretriev

?SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS-

Terminal Type 6 1. 3277 2. 3277A 3. 3278 4. 3278A

5. 3290A 6. 3278T 7. 3278CF 8. 3277KN

9. 3278KN 10. 3278AR 11. 3278CY 12. 3278HN

13. 3278HO 14. 3278IS 15. 3278L2 16. BE163

ISPF TERMINAL CHARACTERISTICS
14 BIT ADDRESSING = ON
16 BIT ADDRESSING = OFF
EXTENDED COLOR = ON
EXTENDED HIGHLITING = ON
DBCS = OFF
PRIMARY SCREEN SIZE - PARTITIONED MODE
SCREEN SIZE = 1,920 - x'00000780'
SCREEN DEPTH = 24 - x'00000018'
SCREEN WIDTH = 80 - x'00000050'
ALTERNATE SCREEN SIZE - PARTITIONED MODE
SCREEN SIZE = 4,960 - x'00001360'
SCREEN DEPTH = 62 - x'0000003E'
SCREEN WIDTH = 80 - x'00000050'
PARTITION SCREEN SIZE - PARTITIONED MODE
SCREEN SIZE = 0 - x'00000000'
SCREEN DEPTH = 0 - x'00000000'
SCREEN WIDTH = 0 - x'00000000'
PRIMARY SCREEN SIZE - NON-PARTITIONED MODE
SCREEN SIZE = 1,920 - x'00000780'
SCREEN DEPTH = 24 - x'00000018'
SCREEN WIDTH = 80 - x'00000050'
ALTERNATE SCREEN SIZE - NON-PARTITIONED MOD
SCREEN SIZE = 4,960 - x'00001360'
SCREEN DEPTH = 62 - x'0000003E'
SCREEN WIDTH = 80 - x'00000050'
ISPF TERMINAL BUFFER INFORMATION
TERMINAL BUFFER ADDR = x'0002ACB8'
TERMINAL BUFFER SIZE = 6,944 - x'00001B20'
PHYSICAL SCREEN SIZE = 4,960 - x'00001360'
PARTITION ARRAY ADDR = x'00019638'
GTTERM INFORMATION
RETURN CODE = x'00000000'
PRIMARY ROW = 24 - x'00000018'
PRIMARY COL = 80 - x'00000050'
ALTERNATE ROW = 62 - x'0000003E'
ALTERNATE COL = 80 - x'00000050'
ATTRIBUTE BYTE = x'000000C9'
EBCDIC TERMINAL
EDS TERMINAL
GTSIZE INFORMATION
RETURN CODE = x'00000000'
ROWS = 62 - x'0000003E'
COLUMNS = 80 - x'00000050'
VTAM ACCESS METHOD
***

When you do this, what do you get for the screen geometry? You might also
check your logmode.

Shmuel (Seymour J.) Metz

[Paul Hanrahan]

maxdata and maxpiu in vtam perhaps? i fixed a bug like this in VM once when
the command processor and terminal i/o subsystems didn't afree on 3290's
being allowed to provide 160 characters. if it's maxdata or piu then more
than just the cursor would be a problem .... the screen would probably look
incomplete. I'd opt for an ISPF problem over a vtam problem.

Paul H

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu]On Behalf Of
George, Bill
Sent: Wednesday, April 18, 2001 12:02 PM
To: ISP...@listserv.nd.edu
Subject: ISPF Errors with "Non Standard" Logmode

[George, Bill]

Thanks.
FYI - All the data on the screen is visually OK, even at 62 X 160.

Bill

[Paul Hanrahan]

Hi:

I sent an inquiry to a senior systems programmer who used to be an IBM field
rep. I remember a 3290 with ISPF in each of four quadrants and each logical
screen defined as a 327X terminal but I don't remember the details.

Paul H

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu]On Behalf Of
George, Bill

[Metz, Seymour]

What is in TSOKEY00 and in the MODEENT for your logmode? What are the
results of an ISPF terminal query from option 0?

Shmuel (Seymour J.) Metz

> -----Original Message-----
> From: George, Bill [SMTP:bill....@EDS.COM]

[Metz, Seymour]

A 3290 is normally attached to a block of four addresses. If it's split four
ways then you just define it to the software as four 3270s. If you want to
be able to split it under software control (explicit partitions), then the
logmode must have the query bit set and your ISPF screen format must be 4
(Part). I don't know of any terminal simulator that looks like a 3290.

Shmuel (Seymour J.) Metz

[George, Bill]

Seymour

Terminal Characteristics

Screen format 1 1. Data 2. Std 3. Max 4. Part

Terminal Type 3 1. 3277 2. 3277A 3. 3278 4. 3278A

5. 3290A 6. 3278T 7. 3278CF 8. 3277KN

Here is the output from TERMSTAT

ISPF TERMINAL CHARACTERISTICS
14 BIT ADDRESSING = ON
16 BIT ADDRESSING = OFF
EXTENDED COLOR = ON
EXTENDED HIGHLITING = ON
DBCS = OFF
PRIMARY SCREEN SIZE - PARTITIONED MODE

SCREEN SIZE = 1,920 - X'00000780'
SCREEN DEPTH = 24 - X'00000018'
SCREEN WIDTH = 80 - X'00000050'

ALTERNATE SCREEN SIZE - PARTITIONED MODE

SCREEN SIZE = 6,600 - X'000019C8'
SCREEN DEPTH = 50 - X'00000032'
SCREEN WIDTH = 132 - X'00000084'

PARTITION SCREEN SIZE - PARTITIONED MODE

SCREEN SIZE = 0 - X'00000000'
SCREEN DEPTH = 50 - X'00000032'
SCREEN WIDTH = 132 - X'00000084'

PARTITION SCREEN SIZE - PARTITIONED MODE

SCREEN SIZE = 0 - X'00000000'
SCREEN DEPTH = 0 - X'00000000'
SCREEN WIDTH = 0 - X'00000000'

PRIMARY SCREEN SIZE - NON-PARTITIONED MODE

SCREEN SIZE = 1,920 - X'00000780'
SCREEN DEPTH = 24 - X'00000018'
SCREEN WIDTH = 80 - X'00000050'
ALTERNATE SCREEN SIZE - NON-PARTITIONED MODE
SCREEN SIZE = 6,600 - X'000019C8'
SCREEN DEPTH = 50 - X'00000032'
SCREEN WIDTH = 132 - X'00000084'
ISPF TERMINAL BUFFER INFORMATION
TERMINAL BUFFER ADDR = X'0002C110'
TERMINAL BUFFER SIZE = 9,240 - X'00002418'
PHYSICAL SCREEN SIZE = 6,600 - X'000019C8'
PARTITION ARRAY ADDR = X'00018638'
GTTERM INFORMATION
RETURN CODE = X'00000000'
PRIMARY ROW = 24 - X'00000018'
PRIMARY COL = 80 - X'00000050'
ALTERNATE ROW = 50 - X'00000032'
ALTERNATE COL = 132 - X'00000084'
ATTRIBUTE BYTE = X'000000C9'

EBCDIC TERMINAL
EDS TERMINAL
GTSIZE INFORMATION

RETURN CODE = X'00000000'
ROWS = 50 - X'00000032'
COLUMNS = 132 - X'00000084'
VTAM ACCESS METHOD

Thanks
Bill

[Paul Hanrahan]

Hi:

Glad Seymour was listening in. My friend hasn't answered yet.

Paul

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu]On Behalf Of
George, Bill
Sent: Wednesday, April 18, 2001 1:24 PM
To: ISP...@listserv.nd.edu
Subject: Re: ISPF Errors with "Non Standard" Logmode

[Metz, Seymour]

That looks good. What about TSOKEY00?

Shmuel (Seymour J.) Metz

> -----Original Message-----
> From: George, Bill [SMTP:bill....@EDS.COM]
> Sent: Wednesday, April 18, 2001 1:24 PM
>

> Terminal Characteristics

[George, Bill]

Sorry, but I don't know where to find that?
I'm rather ignorant of network or MVS parms (if this is a parm of one of
these)
Semi-new CICS SP I am

Can you point me?

Bill

-----Original Message-----
From: Metz, Seymour [mailto:sm...@NSF.GOV]
Sent: Wednesday, April 18, 2001 10:52 AM
To: ISP...@listserv.nd.edu
Subject: Re: ISPF Errors with "Non Standard" Logmode

[Metz, Seymour]

TSOKEY00 is in your parmlib concatenation. Check with whoever is responsible
for TSO and VTAM at your shop before you touch it. You can use the MVS
operator command D IPLINFO to find what LOADxx member was used for the IPL,
and from there you can find the parmlib concatenation, e.g.,

SYS1.PAERMLIB
CPAC.PARMLIB
SYS1.IBM.PARMLIB

[George, Bill]

SCRSIZE=1920,BUFRSIZE=3016,HIBFREXT=102544,LOBFREXT=30160,
USERMAX=250,CONFTXT=NO,RECONLIM=10

-----Original Message-----
From: Metz, Seymour [mailto:sm...@NSF.GOV]
Sent: Wednesday, April 18, 2001 12:20 PM
To: ISP...@listserv.nd.edu
Subject: Re: ISPF Errors with "Non Standard" Logmode

[Metz, Seymour]

Looks more than adequate. Maybe the problem really is on the PC side. But
just for laughs, what happens if you increase SCRSIZE?

Shmuel (Seymour J.) Metz

> -----Original Message-----
> From: George, Bill [SMTP:bill....@EDS.COM]

> Sent: Wednesday, April 18, 2001 4:11 PM
>
> SCRSIZE=1920,BUFRSIZE=3016,HIBFREXT=102544,LOBFREXT=30160,
> USERMAX=250,CONFTXT=NO,RECONLIM=10

[George, Bill]

Being in the position I am, it would be hard for me to "just for grins" have
the MVS group change an MVS parm. Wish I could tho.

Thanks
Bill

-----Original Message-----
From: Metz, Seymour [mailto:sm...@NSF.GOV]
Sent: Wednesday, April 18, 2001 1:43 PM
To: ISP...@listserv.nd.edu
Subject: Re: ISPF Errors with "Non Standard" Logmode

[George, Bill]

Thanks for you input and time.
It IS appreciated!

[paul.ip]

Hi all,

I posted a message before asking about changing Index VTOC to OSVTOC for a SMS
DASD due to a previous DEFRAG was cancelled during execution and then a temp
dataset 'SYS1.DFDSS.DEFRAG..........DTSO01.DUMMY' left on the DASD and can't be
removed.... (Can't re-run the DEFRAG while this dataset exists)
Also, I found that the INDEX STATUS of this DASD is 'DISABLE' when I checked
undef ISMF (I have no idea it is is related to the temp dataset...)

I have got a JCL sample for ICKDSF BUILDIX command....

However, I have another concern... Obviously, the DASD is for TSO users data
storage, it is under SMS managed and the storage group has totally 4 DASDS,
which are DTSO01, DTSO02, DTSO03 and DTSO04... and they are all being frequently
accessed...

My question is...
1. If I run the ICKDSF job to change the INDEX VTOC to OSVTOC and then re-run
the DEFRAG and then change the OSVTOC back to INDEX VTOC, will it affect the
users online access the DTSO01? If yes, what is the proper step to take?
(Or the VTOC is not related to user online access data on DTSO02 since there is
a user catalog on each DASD??)

2. Is that after I change the INDEX VTOC to OSVTOC and then I re-run the DEFRAG,
the temp dataset for previuos cancelled DEFRAG then gone??

Any help is highly appreicated

[Edward E. Jaffe]

paul.ip wrote:

> I posted a message before asking about changing Index VTOC to OSVTOC for a SMS ...

[snip]

> Any help is highly appreicated

You may want to post this on another list/group. IBM-MAIN might be a
good choice. This is an ISPF list.

--
| Edward E. Jaffe | Voice: (310) 338-0400 x318 |
| Mgr., Research & Development | Fax: (310) 338-0801 |
| Phoenix Software International | edj...@phoenixsoftware.com |
| 5200 W. Century Blvd., Suite 800 | USS24J24 at IBMMAIL |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |

[Paul Hanrahan]

In the 'Settings' option they have a 'terminal type' field and
is has a device type for 3290.
I guess that means YES.

At 12:52 PM 4/18/01 -0400, you wrote:
>Donn:
>
>Where would I look to see if ISPF supported the full screen size of a 3290?
>
>Paul H.
>X-6543

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu]On Behalf Of
George, Bill

[Bob Richards]

--- "paul.ip" <pau...@BOCI.COM.HK> wrote:

snippage

> My question is...
> 1. If I run the ICKDSF job to change the INDEX VTOC to OSVTOC and
> then re-run the DEFRAG and then change the OSVTOC back to INDEX VTOC,
> will it affect the users online access the DTSO01? If yes, what is
the
> proper step to take?
> (Or the VTOC is not related to user online access data on DTSO02
> since there is a user catalog on each DASD??)

No, once the DEFRAG is done and IXVTOC is turned back on, they will be
fine.

> 2. Is that after I change the INDEX VTOC to OSVTOC and then I re-run
> the DEFRAG, the temp dataset for previuos cancelled DEFRAG then
gone??

Yes

=====
+---------------------------------+--------------------------------+
| Bob Richards | OS/390 Consultant - Chicago |
| Internet: richa...@yahoo.com | 3D Business Solutions |
+---------------------------------+--------------------------------+

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

[Leonard Woren]

Y'know, there's a reason why there are different mailing lists such
as IBM-MAIN and ISPF-L. While many of us are subscribed to most/all
of them, some people don't want to subscribe (for example) to IBM-MAIN
because of the high traffic level and their focused interest, so they
subscribe to ISPF-L only. When off-topic questions *and answers* are
posted to ISPF-L, some people unsubscribe.

Should we retire ISPF-L and send everyone over to IBM-MAIN? I think not.
So PLEASE STOP posting off-topic questions here -- use the appropriate
list. And PLEASE DON'T ANSWER off-topic questions because it just
encourages them to continue. If the off-topic questions are met with
only a deafening silence or a simple "IBM-MAIN is the appropriate list
for that question" we'll be better off.

Thank you for your cooperation.

/Leonard
ispf-l listowner

[paul.ip]

Leonard,

I am sorry for any inconvenience caused and I will not post off-topic message
to the list

Regards