Swith to lowercase in ISPF skeleton

[stanvanoers]

Hello,
Is it possible to change to lowercase in a Skeleton.

Example
P is a variable defined in a Panel, lets say XXXX
For OMVS segment I define in SKELETON
omvs(home('/var/ansible/home/&P'))

Result is omvs(home('/var/ansible/home/XXXX')) but I want to have omvs(home('/var/ansible/home/xxxx'))
Anybody any idea how to solve
With kind regards
Stan van oers

[sergeyken]

I used skeletons about 10+ years ago.

AFAIR there is the option of using REXX inside of the skeleton.

Control statements

Code: Select all

. . . . . .
)REXX
. . . use TRANSLATE function to convert &P to uppercase/lowercase . . . . .
)ENDREXX
. . . . .

[willy jensen]

No problems with lowercase characters, though the skeleton commands themselves must be in uppercase.
That panel variable P should then be defined as CAPS(NO). Or use a instream converter REXX as shown above.
By the way, the syntax is:
)REXX P
transform P
)ENDREXX

[Pedro]

re: That panel variable P should then be defined as CAPS(NO)

I think Willy is on to something. The user would normally type without setting the case, but the default panel attribute is to translate to uppercase. You might solve your problem by explicitly specifying CAPS(NO) in the panel definition.

Design wise, I think you should honor the case if the user explicitly specifies mixed case, like 'xxXx'.

a tangent: When I was a developer at IBM, we received a requirement to allow mixed case in IMS operator commands. We had a prolonged discussion about what that meant. fyi. It is clear that it was not uppercase, but people thought mixed case only meant to allow lowercase. The customer wanted to allow any mixture of lowercase and uppercase.

[willy jensen]

Pedros reply got me thinking that just blindly converting to lowercase might not be such a good idea. OMVS filenames are mixed case, so the user might actually want to have a mixture of upper- and lowercase in the name.