Having completed an array of changes to your COBOL source, you save and make one last JCL tweak. Before submitting the job, you remember the scripts your colleague told you to update. Using the Remote Systems view, you browse the z/OS UNIX file hierarchy for your shell scripts. All bases covered, it’s time to ensure the prototype works as expected. After running tests, you’re confident the new feature is stable. Sure there are CALL statements to modify but the new programs won’t be ready for at least a few days. That can wait, you tell yourself. Now you can depart for that vacation, confident most of the loose ends are tied up. Off you go for a week of bliss on some exotic beach. Watching waves crash down upon the sand, work worries get washed away…. as does your recollection of your recent work activities. Thankfully, the new Remote Edit History view, provided in the IBM z/OS Explorer Aqua family of products, does remember!

Remote Edit History view

The Remote Edit History view keeps track of whenever you open a remote resource for editing. It remembers the MVS data set members and sequential data sets you edit as well as those files you edit on z/OS UNIX. If you’re using z/OS projects, it remembers those edits too. If you forgot what you were doing weeks (or days… or hours) ago, you can get back to being productive quickly.

By default, the Remote Edit History view shows up in the lower left pane of the Remote System Explorer (RSE) perspective. If you need to open the view, go to the Window menu and select Show View -> Other… Remote Systems -> Remote Edit History.

You’ll see a table of the resources you recently opened in editors. Entries for resources on disconnected systems will show up in grey. Having just returned from vacation, you’re reminded of those recent COBOL changes and those CALL statements you need to modify! If you wish to edit a resource, just double-click on the entry and then RSE will connect, find your resource and open.

Once you’re connected, you can use the context menu to locate the underlying remote resource in a view, such as the Remote Systems view.

The Remote Edit History view lets you clear history items you’re not interested in. You can clear an individual item or the whole list. You can decide how many edit history entries to keep by using the Edit History Limit view action (the default is 30).

The Remote Edit History entries are automatically maintained regardless of whether the view is open or not. While not be pressed to use it today, rest assured remote edit history is available should your mind change later. Whether you’re returning to work after a hiatus or you like the single-click navigation to your edit sessions, this view will help keep you prolific and close to your code.

For more new features, see the announcement for IBM Application Delivery Foundation for z Systems V3.1.1.

1 comment on"Staying Close to Code with Remote Edit History"

  1. Looks like a useful enhancement.

Join The Discussion

Your email address will not be published. Required fields are marked *