|
View previous topic :: View next topic
|
| Author |
Message |
nag.kolli
New User
Joined: 20 Apr 2007
Posts: 5
Location: Hyderabad
|
|
|
|
1. There are two files and to find the matched records....
matched records are to be writeen to third file and non matched records to the forth file.
I need in depth explination of Procedure Divsion.
2. My input file contains
abcd 1
abcd 2
abcd 3
abcd 4
......
......
abcd 15
and i need output as only
1
2
3
4
.
.
15
PLZ SOLVE IT through jcl
3. There are Vsam base, alternative index , path in prodcution
So all these files corrupted and next how to proceed.
4.Major difference between Joins and subquerys?
5.what is -805,-904 how you resove it? |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
1. There are stickys in the Application Programming forum that discuss this type of thing.
2. Can't with JCL. A utility like DFSORT, SYNCSORT, ezytrieve, or REXX could accomplish the parsing.
3. Drain the vsam with sort or repro. redefine the vsam. repro back to the new file.
4. Joins are found in the FROM clause, subqueries normally in the WHERE clauses.
5. -805
| Quote: |
REASON:
PROGRAM NAME location name.collection id.program name.consistency token NOT FOUND IN PLAN plan name
DESCRIPTION:
An attempt was made to execute the application program 'location name.collection id.program name.consistency token' (this token can be 'location name..program name.consistency token' if the current package set special register is blank for the local program execution) that has not been found due to one or more or the following reasons: * The program 'program name' has not been bound as the member part of the application plan 'plan name' or * The 'collection id' in the PKLIST was not correct when the application plan 'plan name' was bound or * The current package set special register was not set correctly or * The 'location name' in the CURRENTSERVER was not correct when the application plan 'plan name' was bound, or * The application was not connected to the proper location or * The location id in the package list was not correct when the application 'plan name' was bound or * The DBRM of the version of the application program being executed was not bound.
USER ACTION:
Based on the above reasons, the programmer can perform the following operations to correct the error. * Bind the program 'program name' as the member part of the application plan 'plan name' or * Correct the collection id in the PKLIST and bind the application plan 'plan name' or * Set the current package set special register correctly or * Put the correct 'location name' in the CURRENTSERVER of the BIND command and bind the application plan 'plan name' or * Connect to the correct RDB name or * Correct the location id in the PKLIST and bind the application plan 'plan name' or * Bind the DBRM of the version of the application program to be executed
|
-905
| Quote: |
REASON:
UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED,RESOURCE NAME = resource name LIMIT = limit amount1 CPU SECONDS (limit amount2 SERVICE UNITS) DERIVED FROM limit source
DESCRIPTION:
The execution of the SQL statement was terminated because a resource limit was exceeded.The name of the resource whose limit was exceeded is 'resource name'. It is also the name of the column in the resource limit specification table from which the limit was derived. The limit that was exceeded in CPU seconds is 'limit amount1' and in service units it is 'limit amount2'.The 'resource name' may be ASUTIME, which is the number of CPU seconds permitted for each SQL statement. The maximum number of CPU seconds permitted is 'limit amount1'. The maximum number in service units is 'limit amount2'.The source used to derive the limit amount is 'limit source' and is either the name of a resource limit specification table or a 'system parameter'.If the source is a system parameter, the resource limit specification table did not contain an applicable entry or an error occurred while accessing the table. In either case, the limit is obtained from an install (system) parameter.
USER ACTION:
Determine why this SQL statement took so long and take appropriate action. Consider simplifying the SQL statement, restructuring tables and indexes, or contacting the installation group responsible for maintaining the resource limit specification tables. An application program that receives this return code can execute additional SQL statements.
|
|
|
| Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007
Posts: 632
Location: Wisconsin
|
|
|
|
| Joins are found in the FROM clause, subqueries normally in the WHERE clauses. Joins aren't always in the FROM clause. Implicit joins happen in the WHERE clause. I never specifically write the JOIN statement unless I have to. |
|
| Back to top |
|
|
diwa_thilak
Active User
.jpg)
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
1. You can use a two file match program logic. i.e use a key in the input files and based on the key write the records in the output file.
Ex : If Key1 (from file1) < Key2 (file 2)
Write record from file1 into ONLY FILE1 record file.
If Key1 (from file1) > Key2 (file 2)
Write record from file2 into ONLY FILE2 record file
If Key1 (from file1) = Key2 (file 2)
Write record from file1/2 into BOTH file.
2. Try to use OUTREC function to get the desired output.
Cheers,
Diwakar
----------------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
|
|
