Technology Questions

No. The mode is specified via the SYSCTL DD card in the JCL.

Check EIBRESP after the call or use the HANDLE condition.

1)Divide by zero        – This is raised when any number is attempted to divide by zero.

2)TOO MANY ROWS   - A SELECT INTO statement returns more than one row.

3)CASE_NOT_FOUND - No choice in the WHEN clause of a case statement is selected.

4)LOGIN_DENIED      - An attempt to login with an invalid username or password.

5)PROGRAM_ERROR  - An internal PL/SQL problem.

First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug. Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:

Critical

High

Medium

Low

Cosmetic

A database trigger is procedural code that is automatically executed in response to certain events on a particular table or view in a database. The trigger is mostly used for maintaining the integrity of the information on the database.

Syntax:

CREATE OR REPLACE TRIGGER [Trigger Name] [Before / After / Instead Of]

ON [schema].[table]

<PL/SQL subprogram>

Types of PL/SQL triggers : 

> Row trigger          - The trigger fires for each ROW affected.

> Statement trigger - The trigger is fired once when the condition is matched

> Before and After trigger - The BEFORE trigger run the trigger action before the insert, update or delete statement. The AFTER trigger runs the trigger action after the insert, update or delete statement is executes.

If any one want to restrict Trans-ID to single user, enter trans-id with ENQ. It won't allow any one else to use the same trans-id.