ISPF editor option

raghav08 · New User Joined: 03 Jun 2008 Posts: 94 Location: Bangalore

Hi,

If i try to use HI (HILITE) / JCK or any other ISPF commands in ISPF editor getting error "not valid command" with the only datasets with starting qualifier my userid (userid.*), not with dev/prod datasets.

I checked with PROFILE, HILITE was OFF, tried to ON it, still getting error "invalid command".

But all these were working fine few days back.

Please let me know how to reset the profile with my user id.

raghav08 · New User Joined: 03 Jun 2008 Posts: 94 Location: Bangalore

Hi,

See the below PROFILE,

***************************** Top of Data ******************
....JCLLIB (FIXED - 400)....RECOVERY ON....NUMBER ON STD....
....CAPS ON....HEX OFF....NULLS OFF....TABS OFF.............
....AUTOSAVE ON....AUTONUM OFF....AUTOLIST OFF....STATS ON..
....PROFILE UNLOCK....IMACRO NONE....PACK OFF....NOTE ON....
....HILITE OFF CURSOR FIND..................................

When try to do HILITE ON getting error message "Option unavailable".Mean while, in "COLORING :" option under HI, i couldn't save any changes.Currently under HI option "COLORING:" is "DO NOT COLOR PROGRAM", but it suppose to be "COLOR PROGRAM".[/Search]

Paddy · Posted: Thu Jul 03, 2008 3:35 pm

hi raghav08,

Probably your profile is locked. See your security manager for to get this options.

raghav08 · New User Joined: 03 Jun 2008 Posts: 94 Location: Bangalore

Paddy,

But you can see --- "PROFILE UNLOCK" status in PROFILE.
Still you are asking to contact RACF admin?

Bill Dennis · Posted: Thu Jul 03, 2008 6:35 pm

Perhaps a 400 byte LRECL file is unable to use HI LITE and other options? It's not the standard 80 bytes.

raghav08 · New User Joined: 03 Jun 2008 Posts: 94 Location: Bangalore

Bill,

You are right, i verified for other libraries having 80 bytes standard LRECL, HILITE is working.

Thanks a lot for your update, haven't knew that.

superk · Posted: Thu Jul 03, 2008 6:59 pm

For a JCLLIB, I recommend using a dataset of RECFM=FB and LRECL=254. And yes, HILITE will work.

Bill Dennis · Posted: Thu Jul 03, 2008 7:09 pm

kevin,

care to elaborate on why such a large LRECL (254) for JCL?

superk · Posted: Thu Jul 03, 2008 7:16 pm

It's great if you ever need to use longer-than-80 byte SYSIN records. There's no real downside to it. Although, I wish it would solve the problem with PARM having to be no more than 100 bytes, and still having to be broken-up across multiple 80-byte records.

Paddy · Posted: Thu Jul 03, 2008 8:29 pm

hi again,

UNLOCK is a possibility to lock profile for particular file. This macro is handled by user. I not correctly looked at your profile and now i see FB 400. The max length record for hilite is 254.

best Regards.

Paddy

gcicchet · Posted: Fri Jul 04, 2008 7:14 am

Hi Kevin,

my understanding of a SYSIN DD * is it denotes an 80 byte record.

So I don't understand how you can use longer than 80 byte SYSIN's unless it points to a dataset.

If I submit a job with a SYSIN DD * and the data is longer than 80 bytes, only the first 80 bytes are visible after the job is submitted to the INTRDR.

Gerry

superk · Posted: Fri Jul 04, 2008 7:51 am

Let me re-phrase that a bit to be instream data, not necessarily SYSIN data, although I consider both to be the same in concept.

gcicchet · Posted: Fri Jul 04, 2008 8:33 am

Hi Kevin,

Maybe be I'm barking up the wrong tree.

I submitted a job with SYSUT1 DD * and still only 80 bytes is submiited, data > 80 is lost.

Gerry

dick scherrer · Posted: Fri Jul 04, 2008 8:44 am

Hi,

Once again, late to the party. . .

I believe it is this - "DD *" - rather than the ddname.

If some of my memory is still hanging in, i believe the length of in-stream data is an installation parameter.

d

gcicchet · Posted: Fri Jul 04, 2008 9:43 am

Thanks Dick I was not aware of the installation parameter

Gerry