|
View previous topic :: View next topic
|
| Author |
Message |
sri_gans
New User
Joined: 03 Nov 2007
Posts: 10
Location: Chennai
|
|
|
|
Hi All,
Currently i have been required for migrating ISPF panels which is in the Japanese langugae to English. The objective of this migration should be Business users/End users need to access the ISPF panels in Japanese but the administrators ( System programmers ) need to access the same panels in English and if required in japanese. ( The OS version is OS/390 V2R10 )
Yes, of course i had gone through the ISPF Planning and customization library guide. But before preceding i need your valuable inputs and suggestions on how to proceed with this activity. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| ...suggestions on how to proceed with this activity. |
I guess that the only thing in japanese would be the texts hard coded in the panels
the variable names should be in plain english
the only reasonable suggestion is to ...
start the donkey work of translating the panel hard coded text. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| I've previously seen reference to English/Korean panels being achieved with "ISPF DTL CONV Conversion utility". Don't know anything about it myself. |
|
| Back to top |
|
|
sri_gans
New User
Joined: 03 Nov 2007
Posts: 10
Location: Chennai
|
|
|
|
Thank you for the information.
When i was going through the ISPF Planning and customization guide, got a chance to look on the interesting part which talks about changing the ISPF default language ( ENGLISH ) to the target language ( Based on the CSECT and LANGUAGE supported by IBM, and the language pack ordered )
And it talks on replacing about ISPMAIN LMOD based on the language requirement. So i think this might help me. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| i have been required for migrating ISPF panels which is in the Japanese langugae to English. |
Are you referring to panels that are part of the ISPF product or are you referring to locally written panels? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
I guess that the TS is referring to home grown panels!
it would seem silly to translate to english program product panels  |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| it would seem silly to translate to english program product panels |
Agreed.
But the TS never actually mentioned 'translation', but only migration. And in their second post, mentions configuration / settings more than anything else, so I do not think it is a translation issue.
So, I asked for clarification. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| Currently i have been required for migrating ISPF panels which is in the Japanese langugae to English |
well... the sentence seems clear to me...
if a product is delivered with multi language libraries, then the installation manual will tell everything
so no need to ask us to do the reading and explaining
more reasonable to interpret migration as translation
|
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
| sri_gans wrote: |
| ...but the administrators ( System programmers ) need to access the same panels in English and if required in japanese... |
So the panels have to exist both in Japanese and in English, and one must be able to switch between languages.
Maybe I would add (on the menu and/or on the top line of the panels) a small option
J for Japanese and E for English, the field set to J and protected for End Users.
The product would issue:
| Code: |
If LANG = 'J' Then
DISPLAY PANEL(japanese)
Else
DISPLAY PANEL(English) |
But too many things are unknown about the TS restrictions |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
There could be several such panels. Rather than change program logic, I think just swap out the panel library.
| Code: |
If LANG = 'J' Then
"LIBDEF ISPPLIB DATASET ID('proj.ISPPJPN')"
Else
"LIBDEF ISPPLIB DATASET ID('proj.ISPPENU')"
"SELECT PANEL(abc) PASSLIB"
|
|
|
| Back to top |
|
|
sri_gans
New User
Joined: 03 Nov 2007
Posts: 10
Location: Chennai
|
|
|
|
Hi All,
Thanks for your comments. May be what i was planned on this requirement is to have separate LOGON PROCS which will be mapped accordingly to the ISPPLIB,SYSEXEC and other concatenations based on the two different ( English and Japanese) laguage requirements. ( By having two different ISPMAIN for two different laguage )
Please let me know your ideas. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
| Back to top |
|
|
sri_gans
New User
Joined: 03 Nov 2007
Posts: 10
Location: Chennai
|
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
Currently i have been required for migrating ISPF panels which is in the Japanese langugae to English. The objective of this migration should be Business users/End users need to access the ISPF panels in Japanese but the administrators ( System programmers ) need to access the same panels in English and if required in japanese. ( The OS version is OS/390 V2R10 )
Yes, of course i had gone through the ISPF Planning and customization library guide. But before preceding i need your valuable inputs and suggestions on how to proceed with this activity. |
to put it shortly, what do You want from us ?
a pat on the shoulder, well... pat pat pat
You read the manual go ahead!
the next time use a better wording ... migrate means you have something , must transform in something else!
in this case ISPF comes with a full set of panels for each multicolture environment
just follow the manual instruction on how to use them
nuff said!
it would be strange if if You' d find somebody with a current experience on it os390 2.10 has been out of maintenance for quite a bit of time
anyway Youi failed to read properly the 2.10 manuals,
they provide the same solution as the latest ISPF
as described here
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/isppla04/3.18?ACTION=MATCHES&REQUEST=default+language&TYPE=FUZZY&SHELF=ISPBKM10.bks&DT=20000714140145&CASE=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT
looks we are just wasting time becaus You did not read thoroughly the manuals
the ISPMAIN stuff is just to save the hassle of specifying a language for ISPF or PDF invocation!
if You still want to change the default language , for any ISPF version
it would be wiser to allocate a load dataset to hold the modified modules
done that for the latest release, have a different load library for each different set of defaults and concatenate the proper library in the logon procedure
the saving is changing the default language for old ISF is minimal
anyway since the process is clearly described, You have no reason to ask, it would not take more than a few minutes to test |
|
| Back to top |
|
|
|
|
