SQL statement history storage

Hitting the wrong button in iSeries can cause a serious headache. If you have exited an STRSQL session without saving and want to retrieve your lost information, you may be out of luck. But Scott Ingvaldson explains where SQL statement history is stored, and how it can be retrieved.

I was using the standard STRSQL command and exited after use. When I exited I chose option 2=Exit without saving...

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please login.

You have exceeded the maximum character limit.

Please provide a Corporate E-mail Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

session, instead of option 1=Save and exit session. Now I have lost all my cumulative SQL history. Do you know where this data was kept? I may be able to restore it from my last backup. I have been unable to locate where the SQL statement history is kept.

Interactive SQL statement history is kept in an object named ISQLST-usrprf-devicename in the library QRECOVERY.

You can display the statement history with this command:
DMPSYSOBJ ISQLSTuuuuuddddd QRECOVERY TYPE(19) SUBTYPE(EE)

Unfortunately, Qrecovery does not get saved with the standard save commands. Unless you have explicitly saved objects from Qrecovery, I don't think you'll have anything to restore. If you had lost your SQL statement history due to changing your device name you might be able to retrieve it with the above command.

A more permanent way to save your statement history when exiting SQL is to use option 4=Save session in source file.

This was last published in April 2008

Dig Deeper on iSeries SQL commands and statements

All
Get Started
Problem Solve

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

Meet all of our AS/400 experts

View all AS/400 questions and answers

Running AS/400 query to find records based on date

Tracking data changes on IBM i with triggers

Convert a numeric physical file to a character in SQL without leading zeros

Inserting data from a CTE into a file in SQL

Running AS/400 query to find records based on date

Tracking data changes on IBM i with triggers

Convert a numeric physical file to a character in SQL without leading zeros

Inserting data from a CTE into a file in SQL

Running AS/400 query to find records based on date

Tracking data changes on IBM i with triggers

Convert a numeric physical file to a character in SQL without leading zeros

Inserting data from a CTE into a file in SQL

Please create a username to comment.

3 ways to benefit from open source infrastructure

IBM mainframes face competitive pressures inside and out

Linux features beyond server management

Dig Deeper on iSeries SQL commands and statements

Related Q&A from Scott Ingvaldson

Have a question for an expert?

Start the conversation

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

Please create a username to comment.