Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
DB2 with error
I am having difficulty compiling a COBOL program with DB2. When I bind, I get a message that the file was not found.
?
I am a newbie in database administration. I would like to know if there is a checklist for DB2 DATASETs so that I can identify which file is missing and proceed with its recovery.
?
I would be very grateful if you could point me to a jcl/proc to validate the DB2 structure and ensure that it is working. I read somewhere that the IBMUSER user was not recommended for accessing DB2. Is this correct?
?
Thank you for your attention.
|
If you look in SYS1.SAMPLIB PDS or in SYS1.ASAMLIB you will find several examples to follow. regards; Rahim??? ??
On Friday, September 27, 2024 at 08:59:21 AM CDT, Vagner R. Bellacosa <vagnerbellacosa@...> wrote:
I am having difficulty compiling a COBOL program with DB2. When I bind, I get a message that the file was not found.
?
I am a newbie in database administration. I would like to know if there is a checklist for DB2 DATASETs so that I can identify which file is missing and proceed with its recovery.
?
I would be very grateful if you could point me to a jcl/proc to validate the DB2 structure and ensure that it is working. I read somewhere that the IBMUSER user was not recommended for accessing DB2. Is this correct?
?
Thank you for your attention.
|
开云体育Yes IBMUSER has restricted access to
many system components and you have not specified what system
version you are using i.e., MVS 3.8, os390, zOS etc along with the
version of it
If using MVS use HERC02 although HERC01 has higher privileges but too high for a normal user. Do not use sysproc privileges if not needed as you can damage the system easily - bit like running in Windows as administrator or Linux as root. On 27/09/2024 14:33, Vagner R. Bellacosa via groups.io wrote:
|
开云体育Hi Vagner,that is not just a file that is missing, it is the DB2 Catalog Database of that subsystem that is unavailable, and it mentions the table where the package info is stored. There should be a SYSADM user to work with DB2 although I doubt this is an authorization problem; this is a DB2 internal error. As to why the catalog is unavailable, the reason code specifies that DB2 is unable to update the system log range dataset, where it keeps the offsets of the log of the before- and after- images. You might have a problem there with mounts and volumes or volume attributes, and it would be good to run the print log inventory standalone utility to see what is there, e.g. what the names of the sys logrange dataset is and its availability for your userid.? Some hints: please paste these messages as text and not as graphics. It would make people much more motivated to look up the reason codes for you, if they can copy and paste them into the manuals (or the web, if you dig that slow IBM web experience). Maybe change these subsystem and lpar names for other reasons. best regards, 搁别苍é.
|
First from ISPF 3.4 list DSN* files.? There are Bind examples in DSN*.SANLJCL file; but first you need to ensure DB2 is up and running from SPUFI? which is under More option from SPF main menu.? You need to ensure the use of correct SUBSYSTEM ID ? which is the first line in your BIND cards.? The name in the Parentheses is the Db2 Subsystem ID. ? you should be able to run a query under SPUFI say? SELECT * FROM SYSIBM.SYSTABLES;? With DSN1 as the default ID; otherwise you have to figure out the correct subsystem ID by poking around DSN* PDS files. //SYSTSIN DD * ? DSN S(DSN1) regards; Rahim ?? |
to navigate to use esc to dismiss