|
View previous topic :: View next topic
|
| Author |
Message |
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
I have a variable in REXX that contains lower case. When I do a SAY command on the variable right before I VPUT the variable, it shows as lower case.
| Code: |
187 *-* SAY HOMEL
>V> "u/gs3324 "
|
On the receiving ISPF Panel, the value of HOMEL display's in upper case after it is VPUT.
| Code: |
ADDRESS ISPEXEC "VPUT (HOMEL) ASIS"
|
Any suggestions as to why it displays as upper case rather than lower case? |
|
| Back to top |
|
 |
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Check the panel definition. Make sure the field attributes defined in the )ATTR section does not specify CAPS(ON) |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
| I am actually specifying CAPS(OFF) on every definition in the (ATTR section. |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
You need to do the following as your command is coded wrong. I also
put the variable in the profile pool in this example.
"VPUT (HOMEL)" ASIS PROFILE |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
the command is coded the right way
( maybe with the wrong assumption about casing )
| Quote: |
ASIS Specifies that the variables are to be copied to the pool in which they already exist or that they are to be copied to the shared pool, if they are new. If the variables exist in both the shared and profile pools, they are copied to the shared pool only.
|
the ASIS does not refer to capitalization, but rather to the pool where the variable will be saved
the problem must be somewhere else
running the dialog in test mode with a breakpoint after the VPUT
You can check what happens to the variables |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
You are correct as it work either way. There is a problem else wheres
as the ASIS was not really need when the CAPS(OFF) is coded on the
panel as it worked both ways. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Can you provide a short example with rexx and panel, that demonstrates the problem? |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
I previously had about 10 lines of symbols defined in the )ATTR section. The manual stated that you cannot use the CAPS parameter when using a TYPE(TEXT) definition. The )BODY section was using combinations of symbols to acheive the different colors for the panel.
What I did to fix my problem was redesign the panel from scratch. I cleared out most of the definitions in the )ATTR section and left a few basic ones like:
| Code: |
)ATTR
+ TYPE(TEXT) SKIP(OFF) COLOR(BLUE) INTENS(HIGH)
_ TYPE(INPUT) SKIP(OFF) INTENS(HIGH) CAPS(OFF)
@ TYPE(TEXT) INTENS(LOW) SKIP(ON) COLOR(YELLOW)
|
I made the )BODY section more basic as well.
| Code: |
)BODY
%--------------- O M V S L O O K U P D I S P L A Y -----------------
%OPTION ===>_ZCMD
+ Message:%_MSG + @Press Enter To Continue<=== +
+ SYSA/J/S =>:%_OMVSA + HOME=>%_HOMEA +
+ PROGRAM=>%_PGMA +
+ SYST =====>:%_OMVST + HOME=>%_HOMET +
+ PROGRAM=>%_PGMT +
|
The HOME and PROGRAM fields then starting displaying as lower case.
Thanks to everyone for their invaluable input. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
I am glad you were able to fix your problem.
A quick comment about your panel:
1. you seem to have two attribute characters '%_' next to each other... I think you can remove the '%' that appears before your input fields.
2. If you want your users to be able the jump from your panel (for example, typing '=3.4' and pressing Enter), I think the input field needs to be preceded by two equal sign and a greater than sign: '==>_field'. |
|
| Back to top |
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 1702
Location: Australia
|
|
|
|
Hi Pedro,
can you please explain :-
| Quote: |
| 2. If you want your users to be able the jump from your panel (for example, typing '=3.4' and pressing Enter), I think the input field needs to be preceded by two equal sign and a greater than sign: '==>_field'. |
Why does it need two equal sign and greater than sign, isn't this just TEXT ?
Gerry |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
I guess there are times when '=' might be valid data rather than jump command. So, not every input field allows a jump.
I guess my advice was somewhat old... look at dialog developers guide, www-03.ibm.com/systems/z/os/zos/bkserv/r9pdf/#ispf and search for NOJUMP for a better description. |
|
| Back to top |
|
|
|
|
