IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Mixed characters not getting accepted through online screen


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
rakeshnaredlla

New User


Joined: 04 Aug 2008
Posts: 26
Location: Hyderabad

PostPosted: Sat Jan 24, 2009 3:57 pm
Reply with quote

Hi,

I have converted a cobol II program to Cobol 390. The problem I am facing here is after conversion the screen is converting the lower case data entered into upper case. Before conversion it was accepting the lower case entered. The thing happening in the cobol 390 prog is the moment the data which was entered in lower case is getting received as upper case in the map field copybook. icon_rolleyes.gif . I am not able to under how this is happening.
Please let me know how to solve this issue.

Note: The Map is same for cobol II and Cobol 390.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA

PostPosted: Sat Jan 24, 2009 7:11 pm
Reply with quote

From the CICS Programming Guide:
Quote:
6.5.5.2 Upper case translation

CICS converts lower case input characters to upper case automatically under some circumstances. The definition of the terminal and the transaction together determine whether translation occurs.

See the UCTRAN option of the PROFILE and the TYPETERM resource definitions in the CICS Resource Definition Guide for how these specifications interact.

You can suppress this translation by using the ASIS option on your RECEIVE MAP command, except on the first RECEIVE in a task initiated by terminal input. (The first RECEIVE may be either a RECEIVE MAP (without FROM) or a terminal control RECEIVE.) CICS has already read and translated this input, and it is too late to suppress translation. (Its arrival caused the task to be invoked, as explained in "How tasks are started" in topic 3.1.2.) Consequently, ASIS is ignored entirely in pseudoconversational transaction sequences, where at most one RECEIVE MAP (without FROM) occurs per task, by definition. For the same reason, you cannot use ASIS with the FROM option (see "Formatting other input" in topic 6.5.12).
It sounds like you need to get with your CICS support group to determine how the old and new transactions are defined.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts Substring number between 2 characters... DFSORT/ICETOOL 2
No new posts Reading dataset in Python - New Line ... All Other Mainframe Topics 22
No new posts Underscore was not populated to onlin... CICS 1
No new posts Trying to change copybook in online c... CICS 4
No new posts Batch call online program, EXCI task ... CICS 3
Search our Forums:

Back to Top