• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Lesser-Known SEU Commands

    April 12, 2006 Ted Holt

    Dear esteemed, highly skilled, and truly professional colleagues:

    Even though WDSc is my development platform of choice, I have no choice but to use SEU at times. Can you say, “Yuck!”? Occasionally I even have to use SEU remotely through the Windows Telnet client. Can you say, “Double yuck!”? I feel like I’m back in the punch-card days. In any event, I have learned recently that some people make SEU harder than it has to be. Here are a few tips to reduce keystrokes. They’re good for everyday use, and even better when working remotely.

    Tip 1: You don’t have to left-justify SEU line commands.

    Line commands are the ones you key over the sequence numbers that run down the left side of the screen. (You don’t have to left-justify commands on the SEU command line either, but that’s beside the point.) If you’re still repeatedly pressing the left-arrow key until you reach the first digit of the sequence number before typing C or M or A or whatever, stop it!

    Tip 2: Use RP instead of C and B.

    The RP command repeats a line. Don’t type C over the first digit of the sequence number of one line and B over the first digit of the next line. Type RP anywhere in the line.

    Tip 3: You can insert more than one new line at a time.

    Follow the I command with a number. If the last digit of the number happens to be the same as the digit in the sequence number, key a space after the number. I frequently use the command I20 to insert 20 new lines at once, especially when editing a CL member. Any lines you don’t key into do not get inserted into the member.

    Tip 4: Use the X and XX commands to temporarily hide text.

    This is especially helpful when you’re working on a monolithic program, where something is defined or calculated in one part of the program and used many lines away. Temporarily hiding the code between the definition and calculation lets you see both parts of the program at once. This has saved me from spelling a variable name one way in one place and another way elsewhere on many occasions. Press F5 to redisplay the hidden lines.

    Tip 5: Print only the parts of the source you need.

    The LLP command prints part of a source member. Type LLP twice in the member–on the sequence numbers of the first and last lines to be printed. If any of the intervening lines have been hidden by the X or XX commands, they will not be printed.

    If you have other SEU tips you’d like to share, please send them my way.

    –Ted

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Tags:

    Sponsored by
    JAMS Software

    One Scheduler. IBM i, Windows, Linux, and More.

    IBM i teams trust JAMS to schedule and orchestrate jobs across every platform in their environment. Centralized visibility, cross-platform dependency management, and alerts that reach the right person before the business feels it.

    Fewer than 5% of IBM i shops run IBM i only. The rest are managing cross-platform dependencies — often without a clear picture of how they connect. JAMS draws that map, enforces those dependencies automatically, and gives your team a single place to monitor, manage, and recover when something goes wrong.

    If you are running hundreds of CL scripts and custom RPG processes, bring them as-is. JAMS runs them exactly as they do today — except now they are visible, monitored, and part of an orchestrated workflow instead of scattered across folders only one person knows about.

    No consumption-based pricing. No surprise bills when your workload spikes. You pay based on how many machines JAMS talks to — that’s it.

    Learn More → https://jamsscheduler.com/lp/ibm-i

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Sponsored Links

    COMMON:  Join us at the Fall 2006 conference, September 17-21, in Miami Beach, Florida
    BCD:  Try WebSmart - the easiest and most complete iSeries Web development tool
    Xperia:  Fully integrated suite of applications for small- to mid-sized companies

    SQL Goodies in DB2 for i5/OS V5R4, Part 1 Admin Alert: Another Way to Move Devices Between Systems

    Leave a ReplyCancel reply

Volume 6, Number 15 -- April 12, 2006
THIS ISSUE SPONSORED BY:

T.L. Ashford
WorksRight Software
Bug Busters Software Engineering

Table of Contents

  • SQL Goodies in DB2 for i5/OS V5R4, Part 1
  • Lesser-Known SEU Commands
  • Admin Alert: Another Way to Move Devices Between Systems

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • Oracle Dips A Toe Into IBM’s EBCDIC World
  • When Your Small IBM i Team Is Really A Team Of One
  • Guru: Putting Failure Handling In Its Place
  • Inside The Security Enhancements In ACS
  • IBM i PTF Guide, Volume 28, Number 28: A Crazy Number of Security Vulnerability Patches
  • IBM i PTF Guide, Volume 28, Number 29
  • Inside The Encryption Key Management Changes In IBM i 7.6
  • FalconStor Moved To The Blue Lagoon, And Is Poised For Growth Because Of It
  • Guru: Claude’s SQL Tip
  • Astera Makes Extracting Legacy Report Data an AI Specialty

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle