Prevent N80513 error message by changing Logmode for application Logon in SOLVE:Access
search cancel

Prevent N80513 error message by changing Logmode for application Logon in SOLVE:Access

book

Article ID: 125750

calendar_today

Updated On:

Products

SOLVE:Access Session Management SOLVE

Issue/Introduction

Solve Access is used to login to CICS in Model3 Mode. A logon procedure is also in use.
Some users need to login with Model2, but the logon attempts are currently failing with
N80513 BIND PARAMETERS SCREEN SIZE MISMATCH - SESSION REFUSED 

The ability to change the Logmode for logging on to CICS from model3 to model2 is needed for this situation.

This is the Session in the sessionlist. 

SLVSYS1------------------------ MAI : Session --------------------------------- 
Command ===> Function=Logon 

Session ID .......... CICS1 
Logon Request ....... CICS1 &USERID/&USERPW;CICS Test Install (CICLG1) 

Jump Keys ( Valid Keys : F1-F24, PA1-PA3, ATTN ) 
Forward Keys ...... 
Reverse Keys ...... 
MAI Menu Keys ..... ATTN PA2 
Swap Keys ......... F21 
Screen Print Key 
SIS Menu Key ...... 

Session Characteristics 
Wait if Inactive? N (Y=Wait for application to start) 
Restart at end? ... N (Y=Restart session) 
Fast Jump? ........ N (Y=Jump can ignore unentered data) 
Compress? ......... Y (Y=Compress outbound datastreams) 
Logmode ........... M3SNAQ (Overriding mode table entry name)
<==== This is Model3 Logmode 
Node Name ......... (Overriding virtual terminal name) 
Script Name/Parms CICTUN (Session script details) 
F1=Help F2=Split F3=Cancel 
F9=Swap 


It is possible to see what model the user has defined with &zlogmode, but not possible to change the logmode with NCL from M3SNAQ to Model2….. 

Model3 is generally used because of Model4 or 5 Users, where Cicspanels are crashes. But there is a need to change the logmode to model 2 to allow for logon of MOD2 users.

Can this be done via the  logon script?
Is there another way?

 

Environment

Release: SLACCS00200-5.0-SOLVE:Access-Session Management

Resolution

There is no way to change the logmode via the logon script.

Please examine the destination application to see if modifications can be made there to facilitate this.