what is the maximumm length of account information in job
card of a jcl?
Answers were Sorted based on User's Feedback
Answer / hari krishna
maximum characters can be coded as accounting information is 142
| Is This Answer Correct ? | 4 Yes | 1 No |
Answer / latha
Entire accounting information parameter must not exceed 143
characters :
° Including any commas, which are considered part of the
information.
° Excluding any enclosing parentheses, which are not
considered part of the information
| Is This Answer Correct ? | 3 Yes | 2 No |
Answer / ramya sree sattala
The accounting information in use at your installation.
This information is variable and can be up to 142 bytes
long.
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / reddy
the name of the accounting information is 1-20 alphanumeric
characters... and the data will store in it, and the data
will have the length 142 characters
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / anand sk
The maximum lenght of accounting information is 44
characters.
Refer -
http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?
topic=/com.ibm.zos.r9.ieag100/skp1.htm
| Is This Answer Correct ? | 1 Yes | 3 No |
Can a variable length segment be declared in IMS? If yes, what is the structure; If no, why?
What is meant by bmp mode?
What are common status codes that you come across?
What for procopt is used? List some of them?
What information does a psb contain?
What are the advantages of a hierarchical database?
What is the maximum of key fields and search fields allowed in a segment?
What is the difference between SIBLINGS and TWINS in IMS-DB database
How to write the PCB code ? if in thic PCB i have 3 PSB ?
What is Program Isolation?
What is check pointing, sync point?
how to create a changeman read only audit and update only audit Specifications for the Read only Audit 1) Read HFFD database unqualified. 2) Read FDRT, FDDM, FDAP segments. If FDAP-APP-STS is ‘2’ read the FDAV segment and get the FDAV segment which has FDAV-APV-OPTION as ‘X’ If FDAP-APP-STS is ‘5’ read the HFAC database. Read the ACRT segment qualified based on the key obtained from the FDAP segment from HFFD database. Conditions for writing into output file: a. App Type should be NEWR b. App Status should be 1, 2 & 5. c. Write 50 records per app status. For e.g. first 50 records for App status 1, 2 & 5 each The output file should contain the following fields from the database FDRT-COMP-CTRY-CODE X(03). FDRT-CUST-ID-NUM X(10) FDDM-DEM-SEQ-NUM X(01) FDAP-APP-SEQ X(02) FDAP-JNT-IND X(01) FDAP-APP-STS X(01) FDAV-APV-OPTION X(01) FDAV-APV-DT X(06) FDAV-APV-AMT X(07) ACRT-ACCT-NUM X(06) ACRT-SEG-BUS-TYPE X(02) ACRT-NM1-LAST X(19) ACRT-NM1-SS X(09) ACRT-NM1-1ST X(12) ACRT-NM1-INIT X(01) ACRT-NM1-SFX X(03) ACRT-NM1-TITLE X(02) PSB – DVAN2BMP In case you get a GE for any of the conditions, write to output file along with the details of the database segment which was not found. We need to complete this whole process by tomorrow. Run the audit in DLI mode. 2) Sort the output file created in step 1 on Cust ID, Dem Seq & App Seq. Specifications for the Update Audit 3) Take the output of step 2 as input for an update audit. Details are as follows: Read each record & check the app status. If app status is less than 2 then update the FDAP-NEW- MONEY-ENT to $25000.00 PSB - AUDBMPJ The job would be a BMP job. The test job would be run in IMSE region. Note - The proc (which will be called by the job) and the job should also be present in the change-man package itself. You’ll have a test job in your PDS along with overrides to execute the program in test regions. The job would be a DLI job. The test job would be run in IMSE region. It’ll have the following steps. 1) Delete-define output and error files. 2) Use a copybook for the output layout.