Dave, My SL is actually SLOG with an allowed abbreviation down to two characters. If there was a conflict, I would change the "T" value to 0.
Here is a list of common ones I use: VERB T VERB T ACS 0 QR 0 AOC 0 QSTATS 3 BH 0 QSETSYS 2 BOOK 3 QWAIT 3 BPXMTEXT 2 QW 0 CRPLUS 2 QWSDSF 3 DB2 0 RACF 3 DDN 0 RMF 0 DSL 0 RMM 3 D2X 0 SAS 0 FA 0 SASGRAPH 4 FFST 0 SDSF 2 HCHECKER 2 SDDA 3 HCD 0 SLOG 2 HSEND 3 SDHOLD 3 ICSF 0 SMPE 3 IFIND 0 SVAA 3 IPCS 3 TASID 2 ISHELL 2 TIME 2 ISMF 0 TMISPF 2 LISTA 0 TWS 0 LMS 0 T2H 0 LOGR 4 UL 0 LOGRECV 6 VANGUARD 2 MXG 0 VCURSOR 4 MQA 2 VRCICS 2 MXI 2 VPS 2 NDM 2 VVDS 0 NEST 0 WETBL 2 OBROWSE 2 WLM 0 OEDIT 2 WLMQUE 4 OMVS 2 XB 0 QA 0 XE 0 QCDS 2 XMITIP 2 Bob -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Dave Salt Sent: Tuesday, April 28, 2009 2:44 PM To: [email protected] Subject: Re: ISPF Question > On 28 Apr 2009 03:24:34 -0700, [email protected] (Richards, > Robert B.) wrote: > >>Who remembers option numbers? I have used command table entries for >>years and invoke dialogs by their name or a logical abbreviation of >>same. Want RACF? Type RACF. Want ISMF? Type ISMF. 3.4 is DSL (DSLIST), >>SDSF LOG is SL. You get the idea. This brings up a question I've been meaning to ask for a while; does anyone know if there's a way to 'reserve' command table abbreviations? Bob mentioned that he uses 'SL' to invoke the SDSF log, but this is the same abbreviation that's used by SimpList customers to invoke SimpList. This means a site would either have to rename their old 'SL' command to something else, or a different command would have to be used to invoke SimpList (which then wouldn't match with what's documented in the SimpList user guide and online tutorials). In addition to 'SL' there are several other commands that SimpList uses: BR - Browse BRS - Browse in a new session ED - Edit EDS - Edit in a new session SL - Launch SimpList SLS - Launch SimpList in a new session VI - View VIS - View in a new session The trailing 'S' after each command means 'Start a new session'. For example, if someone is browsing a COBOL program and it calls a copybook they want to browse, they could enter 'BRS' on the command line and point the cursor at the copybook. This opens the copybook in a new session (i.e. similar to a new split screen), so the user can swap back and forth between the COBOL program and the copybook. As you can imagine there has already been instances where some of the above commands conflict with commands used at customer sites. This isn't dfficult to overcome because an ISPF dialog allows the SimpList product installer to call the commands anything he or she chooses. But in this case, the renamed commands will no longer match the commands that are documented in the SimpList user guide and online tutorials. Perhaps by listing the commands in an email like this it at least makes people aware of the situation. Meanwhile, it would be really nice if there was a better way to somehow try to reserve commands? Dave Salt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
