brainchime.com Latest Questions

Admin
Asked: 2024-10-06T04:03:54+05:30 In:

How to change STRSQL session to use library list?

Hi, I have set the library DEVLIB on top of the library list by running the command addlible lib(devlib) from the command line, so that file PF1 should get picked from that library as I am running one SQL select query from STRSQL session on IBM i green screen without qualifying the file name with the library name select * from pf1 and getting error PF1 in DEVELOPER type *FILE not found i.e. SQL0204.

I can see that I put the library DEVLIB on the library list and in error i.e. coming on STRSQL session mentions library DEVELOPER which is the same as my user profile name. However, I checked on the machine and there is no library with my user profile created yet, and still, if I create it let’s say then why it’s not picking from the actual library present on top of the library list? Why it is not searching that file in the library list first?

As an alternative, I have to qualify the library name with the file name in the SQL query select * from devlib.pf1 on STRSQL session to get the results which ran fine and gave me the resulting rows.

But again another error caught up here when qualifying the file name with the library name using slash(/) instead of dot(.), the SQL query is select * from devlib/pf1 and got another error while running this query which is Qualified object name PF1 not valid. i.e. SQL5016 cause was mentioned here:

Cause . . . . . : One of the following has occurred:
-- The syntax used for the qualified object name is not valid for the
naming option specified. With system naming, the qualified form of an
object name is schema-name/object-name or schema-name.object-name. With SQL
naming the qualified form of an object name is
authorization-name.object-name.
-- The syntax used for the qualified object name is not allowed.
User-defined types, functions, variables, and sequences cannot be qualified
with the schema name using the / separator in the system naming convention
when used in a query.
Recovery . . . : Do one of the following and try the request again:
-- If you want to use the SQL naming convention, specify the SQL naming
option and qualify the object names in the form
authorization-id.object-name.
-- If you want to use the system naming convention, specify the system
naming option and qualify the object names in the form
schema-name/object-name or schema-name.object-name.
-- With the system naming convention, either make sure the user-defined
types, functions, variables can be found in the current path or use the
period form of naming to qualify the object.

Now here, in this error, it talks about the SQL Naming convention thing which is causing both the errors I think. How to change the session attributes of strsql to search library list namely the Naming convention attribute.

as400db2

Related Questions

Leave an answer

Leave an answer

Browse
Browse

Choose from here the video type.

Put Video ID here: https://www.youtube.com/watch?v=sdUUx5FdySs Ex: "sdUUx5FdySs".

2 Answers

  1. Admin

    Looking at both errors SQL0204 and SQL5016 it is clear that the *SQL Naming convention is set as default in your STRSQL session attributes.
    With the *SQL Naming convention being set on your STRSQL session you cannot use the qualifier slash(/) and instead, you have to only rely on using dot(.) as a qualifier. Also, with the *SQL naming convention it will search for the file/table in the schema name same as the user profile on the IBM i system.
    Therefore, both errors SQL0204 i.e. PF in DEVELOPER type *FILE not found, and SQL5016 i.e. Qualified object name PF1 not valid. are valid errors and they are more of a type of Diagnostic error.
    Therefore, to fix this problem use both slash(/) and dot(.) as a qualifier and run SQL queries without the need to qualify file/table with library name and instead search in the set library list in the same session you need to change the STRSQL session attribute namely Naming convention. So, please change the Naming convention attribute from *SQL to *SYS. You can do so by these steps:

    • On STRSQL session press F13 (shift + F1). It will show the following options: 
      Interactive SQL Session Services

Select one of the following: 

1. Change session attributes 
2. Print current session 
3. Remove all entries from current session 
4. Save session in source file 











Selection 
     1
    • Take option 1 to change session attributes. It will show the following menu: 
      Change Session Attributes 

Type choices, press Enter. 

Statement processing . . . . . *RUN *RUN, *VLD, *SYN 
SELECT output . . . . . . . . 1 1=Display, 2=Printer 
3=File 
Commitment control . . . . . . *NONE *NONE, *CHG, *CS, *ALL, *RR 
*NC, *UR, *RS 
Date format . . . . . . . . . u *JOB, *USA, *ISO, *EUR, *JIS
*MDY, *DMY, *YMD, *JUL 
Date separator . . . . . . . . '/' *JOB, '/', '.', ',', '-' 
' ', *BLANK 
Time format . . . . . . . . . *HMS *HMS, *USA, *ISO 
*EUR, *JIS 
Time separator . . . . . . . . ':' *JOB, ':', '.', ',' 
' ', *BLANK 
Data refresh . . . . . . . . . *ALWAYS *ALWAYS, *FORWARD 
Allow copy data . . . . . . . *YES *YES, *OPTIMIZE, *NO 
Naming convention . . . . . . *SQL *SYS, *SQL
    • Change the Naming convention from *SQL to *SYS.
    • Exit from the menu.
    • Exit from the STRSQL session.
    • Now add the library to the library list from the command line using the command ADDLIBLE LIB(DEVLIB). Go back to the STRSQL session and run SQL queries without qualifying the library name with file/table name or even using any qualifier either slash(/) or dot(.) if you are qualifying the file/table name.
  2. Admin

    You can change the Naming convention attribute using various ways at different places.

    • In the Interactive STRSQL environment: Use the key F13(Shift + F1) to change SQL session attributes on STRSQL  session.
    • In Embedded SQL programs: You can use the following code as the first statement before the first executable line in the program.
      EXEX SQL
      SET option naming = *SYS
      or
      EXEX SQL
      SET option naming = *SQL
    • With RUNSQLSTM command: Use the following command
      RUNSQLSTM SRCFILE(libname/srcpf) SRCMBR(srcmbr)
      COMMIT(*none) DFTRDBCOL(libname) DBGVIEW(*source)
      NAMING(*SYS)
      or
      RUNSQLSTM SRCFILE(libname/srcpf) SRCMBR(srcmbr)
      COMMIT(*none) DFTRDBCOL(libname) DBGVIEW(*source)
      NAMING(*SQL)
    • In ACS: define in the connection, Preferences -> Database -> Naming convention -> SQL(*SQL) or System(*SYS)