COBOL Programming :: RE: Two digit Date format

May 7, 2016, 1:41 am

≫ Next: CLIST & REXX :: Need Help to Define 36 Input Fields (1 Byte) in REXX

≪ Previous: COBOL Programming :: RE: Getting soc4 on internal table in cobol

Author: Bill Woodger
Subject: Reply to: Two digit Date format
Posted: Sat May 07, 2016 2:11 pm (GMT 5.5)

If your data are reliable, it is even simpler:

Code:

01 SOURCE-FIELD PIC X(30) VALUE "1/1/2016".
01 RESULT-FIELD.
05 RF-DD PIC 99.
05 FILLER PIC X VALUE "/".
05 RF-MM PIC 99.
05 FILLER PIC X VALUE "/".
05 RF-YYYY PIC XXXX.
...
UNSTRING SOURCE-FIELD DELIMITED BY "/"
INTO RF-DD RF-MM RF-YYYY

I normally define date-fields as PIC X. Here I have 99 for the DD and MM as I want the leading-zero-fill which is automatically associated with a MOVE to a numeric field (the UNSTRING ends up using the same rules as MOVE).

Note that the YYYY is PIC X because I don't want the properties of a numeric for a MOVE. I want left-justified and right-truncation.

If desperate for some odd reason to use 9s for the YYYY, include an additional value (SPACE) on the DELIMITED BY.

↧

CLIST & REXX :: Need Help to Define 36 Input Fields (1 Byte) in REXX

May 7, 2016, 2:38 am

≫ Next: CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

≪ Previous: COBOL Programming :: RE: Two digit Date format

Author: satish.ms10
Subject: Need Help to Define 36 Input Fields (1 Byte) in REXX
Posted: Sat May 07, 2016 3:08 pm (GMT 5.5)

Hi All,

Thanks for all your support.

I have situation to define 36 fields of each 1 byte for user input.

My input panel should look like

Code:

INPUT PANEL

F01: _ F02: _ F03: _ F04: _ F05: _ F06: _

F07: _ F08: _ F09: _ F10: _ F11: _ F12: _

F13: _ F14: _ F15: _ F16: _ F17: _ F18: _

.....

.....

F31: _ F32: _ F33: _ F34: _ F35: _ F36: _

I am unable to find that how to define these many 1 byte Input fields?

Can you help me with some pointers?

Thanks in advance.
_________________
Thanx,
Sati

↧

CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

May 7, 2016, 5:46 am

≫ Next: CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

≪ Previous: CLIST & REXX :: Need Help to Define 36 Input Fields (1 Byte) in REXX

Author: enrico-sorichetti
Subject: Reply to: Need Help to Define 36 Input Fields (1 Byte) in REXX
Posted: Sat May 07, 2016 6:16 pm (GMT 5.5)

read the ISPF manuals about the

Code:

.ZVARS

construct
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort

↧

CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

May 8, 2016, 4:31 am

≫ Next: PL/I & Assembler :: And yet another PL/I RFE to vote for (or not)

≪ Previous: CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

Author: satish.ms10
Posted: Sun May 08, 2016 5:01 pm (GMT 5.5)

Thank you so much Enrico.

I am able to fulfill my requirements with .ZVARS.

Thanks,
Satish
_________________
Thanx,
Sati

↧

PL/I & Assembler :: And yet another PL/I RFE to vote for (or not)

May 8, 2016, 12:30 pm

≫ Next: DFSORT/ICETOOL :: RE: Convert Timestamp Value

≪ Previous: CLIST & REXX :: RE: Need Help to Define 36 Input Fields (1 Byte) in REXX

Author: prino
Subject: And yet another PL/I RFE to vote for (or not)
Posted: Mon May 09, 2016 1:00 am (GMT 5.5)

Enhance readability/usability of Attribute/Xref Table

As usual, an IBM ID is required to vote, and just as usual, you may get a 500 error by clicking the above...
_________________
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
No programming here

↧

DFSORT/ICETOOL :: RE: Convert Timestamp Value

May 8, 2016, 6:54 pm

≫ Next: DFSORT/ICETOOL :: RE: Convert Timestamp Value

≪ Previous: PL/I & Assembler :: And yet another PL/I RFE to vote for (or not)

Author: magesh23586
Subject: Reply to: Convert Timestamp Value
Posted: Mon May 09, 2016 7:24 am (GMT 5.5)

This code may help you.

Code:

_________________
Regards,
Magesh

↧

DFSORT/ICETOOL :: RE: Convert Timestamp Value

May 8, 2016, 7:48 pm

≫ Next: DFSORT/ICETOOL :: RE: Convert Timestamp Value

≪ Previous: DFSORT/ICETOOL :: RE: Convert Timestamp Value

Author: magesh23586
Subject: Reply to: Convert Timestamp Value
Posted: Mon May 09, 2016 8:18 am (GMT 5.5)

Missed +12 addition.

Code:

OPTION COPY
INREC IFTHEN=(WHEN=INIT,OVERLAY=(1,3,
CHANGE=(3,C'JAN',C'01',
C'FEB',C'02',
C'MAR',C'03',
C'APR',C'04',
C'MAY',C'05',
C'JUN',C'06',
C'JUL',C'07',
C'AUG',C'08',
C'SEP',C'09',
C'OCT',C'10',
C'NOV',C'11',
C'DEC',C'12'),
NOMATCH=(C'00'),
13:13,2,FS,ZD,LENGTH=2)),
IFTHEN=(WHEN=(25,2,CH,EQ,C'PM',AND,13,2,CH,NE,C'12'),
OVERLAY=(13:13,2,ZD,ADD,+12,LENGTH=3)),
IFTHEN=(WHEN=(25,2,CH,EQ,C'AM',AND,13,2,CH,EQ,C'12'),
OVERLAY=(13:C'00')),
IFTHEN=(WHEN=NONE,OVERLAY=(13:13,2))
OUTREC BUILD=(8,4,1,2,5,2,13,2,16,2,19,2,22,3)

_________________
Regards,
Magesh

↧

DFSORT/ICETOOL :: RE: Convert Timestamp Value

May 8, 2016, 9:32 pm

≫ Next: COBOL Programming :: RE: Two digit Date format

≪ Previous: DFSORT/ICETOOL :: RE: Convert Timestamp Value

Author: mrdinesh
Subject: Reply to: Convert Timestamp Value
Posted: Mon May 09, 2016 10:02 am (GMT 5.5)

Hi Magesh,

Thanks for your Help. I was able to convert the timestamp with a different Sortcard, but similar to the one you posted.

Code:

OPTION COPY
INREC IFTHEN=(WHEN=(05,1,CH,EQ,C' '),OVERLAY=(05:C'0'),HIT=NEXT),
IFTHEN=(WHEN=(13,1,CH,EQ,C' '),OVERLAY=(13:C'0'),HIT=NEXT),
IFTHEN=(WHEN=(25,2,CH,EQ,C'PM',AND,13,2,CH,NE,C'12'),
OVERLAY=(13:13,2,ZD,ADD,+12,TO=ZD,LENGTH=2),HIT=NEXT),
IFTHEN=(WHEN=(25,2,CH,EQ,C'AM',AND,13,2,CH,EQ,C'12'),
OVERLAY=(13:C'00'))
OUTREC BUILD=(8,4,1,3,CHANGE=(2,C'Jan',C'01',C'Feb',C'02',
C'Mar',C'03',C'Apr',C'04',C'May',C'05',C'Jun',C'06',
C'Jul',C'07',C'Aug',C'08',C'Sep',C'09',C'Oct',C'10',
C'Nov',C'11',C'Dec',C'12'),NOMATCH=(C' '),
5,2,13,2,16,2,19,2,22,3)

Just have one small question - Is there any way to ignore the lower cases. In this I have to build the sort with only lower cases since the input file contains smaller cases. (This is not a real big issue, but anyhow the above sort solves the requirement).

Thanks.

↧

COBOL Programming :: RE: Two digit Date format

May 8, 2016, 9:48 pm

≫ Next: DFSORT/ICETOOL :: RE: Convert Timestamp Value

≪ Previous: DFSORT/ICETOOL :: RE: Convert Timestamp Value

Author: abdulrafi
Posted: Mon May 09, 2016 10:18 am (GMT 5.5)

Thanks Bill and Robert for your kind help.
_________________
Thanks,
Abdul Rafi

↧

DFSORT/ICETOOL :: RE: Convert Timestamp Value

May 8, 2016, 9:58 pm

≫ Next: DFSORT/ICETOOL :: RE: Performing addition using JCL sort card

≪ Previous: COBOL Programming :: RE: Two digit Date format

Author: Bill Woodger
Subject: Reply to: Convert Timestamp Value
Posted: Mon May 09, 2016 10:28 am (GMT 5.5)

Why do you want the NOMATCH for the monts? What's your actual problem with the months and lower-case?

If you use CHANGE for the blank parts o the hours (first character of time) won't that do it? Then your IFTHEN is just for PM less than 12?

Why jam all your code together like that? You worked from magesh23586's example, which has better formatting than most, then decided to make it harder to read and change?

If you follow my suggestions, you'll greatly reduce the amount of code. Why not make what is left easier to read?

↧

DFSORT/ICETOOL :: RE: Performing addition using JCL sort card

May 8, 2016, 11:33 pm

≫ Next: CLIST & REXX :: REXX Screen not working due to LINKEDIT issue

≪ Previous: DFSORT/ICETOOL :: RE: Convert Timestamp Value

Author: Shaheen Shaik
Posted: Mon May 09, 2016 12:03 pm (GMT 5.5)

Thank you all for your answers.

_________________
Shanthanu

↧

CLIST & REXX :: REXX Screen not working due to LINKEDIT issue

May 9, 2016, 1:14 am

≫ Next: CLIST & REXX :: RE: REXX Screen not working due to LINKEDIT issue

≪ Previous: DFSORT/ICETOOL :: RE: Performing addition using JCL sort card

Author: sundarkudos
Subject: REXX Screen not working due to LINKEDIT issue
Posted: Mon May 09, 2016 1:44 pm (GMT 5.5)

Hi All,

When I compile a PL/I DB2 program on a Z/OS v1.13 machine running with DB2 V8.1 and Enterprise PL/I v4.2, below warnings are encountered during Bind process. REXX screen which is linked this PL/I DB2 component started failing due to this.

The same program was then compiled with PL/I v1.1 and DB2 v8.1 setup, which did not throw any of these warnings and the REXX screen also working fine. For some reason, the link step is added with DSNHLI, DSNELI and DSNALI to the load module and which in turn mess up the setup done for PL/I v4.2. Has anyone ever seen this behavior before?? Please guide me to resolve this issue.

IEW2480W A711 EXTERNAL SYMBOL DSNHLI OF TYPE LD WAS ALREADY DEFINED AS A SYMBOL OF TYPE LD IN SECTION DSNELI.
IEW2482W A712 THE ORIGINAL DEFINITION WAS IN A MODULE IDENTIFIED BY DDNAME SYSLIB. THE DUPLICATE DEFINITION IS IN
SECTION DSNALI IN A MODULE IDENTIFIED BY DDNAME SYSLIB.
IEW2480W A711 EXTERNAL SYMBOL DSNWLI OF TYPE LD WAS ALREADY DEFINED AS A SYMBOL OF TYPE LD IN SECTION DSNELI.
IEW2482W A712 THE ORIGINAL DEFINITION WAS IN A MODULE IDENTIFIED BY DDNAME SYSLIB. THE DUPLICATE DEFINITION IS IN
SECTION DSNALI IN A MODULE IDENTIFIED BY DDNAME SYSLIB.

and, the module map is below

E478 DSNELI * CSECT 296 SYSLIB 08 DSNHLI
E494 DSNWLI LABEL
E4A4 DSNHLI LABEL

FD28 DSNALI * CSECT 310 SYSLIB 08 DSNALI
FD42 DSNASP LABEL
FD48 DSNHLI2 LABEL
FD54 DSNWLI2 LABEL

Error screenshot is below::

**************************************************
*** SQL ERROR ENCOUNTERED AT 17.22
*** ON 09/05/16
*** PROGRAM ==> SGPI01R
*** SQLCODE ==> -927
*** FUNCTION ==> PREPARE BATCH_SQL FROM :SQL_STMT
*** TABLE NAME ==>
***-----------------------------------------------
*** ERROR MESSAGE : -
*** SQLCODE = -927, ERROR: THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN

*** THE CONNECTING ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD B

*** INVOKED UNDER THE DSN COMMAND

***
*** SQLSTATE = 51006 SQLSTATE RETURN CODE

*** SQLERRP = DSNELI SQL PROCEDURE DETECTING ERROR

***

***
************************************************** IDI0055E Fault Analyzer pro
cessing excluded because 4 meg of 31 bit storage is not currently available
IDI0087I 11.8 Meg of 31 bit storage could be provided by SETPROG LPA,ADD,MOD=(I
DIDA),DSN=LNKLST
IDI0126I Recovery fault recording fault ID F87207 assigned in history file SYSU
.IFA.AAQ3.HIST
IGD01008I SYSU.IFA.GDP3.D160509.T072201.SSU24: IS SMS MANAGED BY DEFAULT
IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO SYSU.IFA.GDP3.D160509.T072201.SSU2
4
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=3000
TIME=17.22.01 SEQ=02240 CPU=0000 ASID=0121
PSW AT TIME OF ERROR 078D1E00 802BAB2A ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=002BAA88 OFFSET=000000A2
NAME=VABENDL
DATA AT PSW 002BAB24 - 00181610 0A0D5820 60041222
GR 0: 80000000 1: 80000BB8
2: 002BAAEE 3: 260B5604
4: 260BBAE0 5: 00000000
6: A60C72F8 7: 002CC6EC
8: 000000A8 9: 002CB438
A: 002BAA88 B: 0000000E
C: 0028CBD8 D: 002CF360
E: 802BAB12 F: 002BADD0
END OF SYMPTOM DUMP
IRX0250E System abend code 0C4, reason code 00000017.
IRX0255E Abend in host command SETMSG or address environment routine ISPEXEC.

Thanks,
Sundar

↧

CLIST & REXX :: RE: REXX Screen not working due to LINKEDIT issue

May 9, 2016, 2:29 am

≫ Next: JCL & VSAM :: CPU time Vs Number of records

≪ Previous: CLIST & REXX :: REXX Screen not working due to LINKEDIT issue

Author: enrico-sorichetti
Subject: Reply to: REXX Screen not working due to LINKEDIT issue
Posted: Mon May 09, 2016 2:59 pm (GMT 5.5)

speak to Your support to understand the changes done/NOT DONE
when migrating to Enterprise PL/I v4.2

NOT a REXX/ISPF problem yet!

after 8 years You should know better how to ask for help
and ...
THERE ARE NO REXX SCREENS

at what time are You getting the abend
the info provide is completely useless
wiserto describe better the environment and the flow of the process
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort

↧

JCL & VSAM :: CPU time Vs Number of records

May 9, 2016, 3:35 am

≫ Next: JCL & VSAM :: RE: CPU time Vs Number of records

≪ Previous: CLIST & REXX :: RE: REXX Screen not working due to LINKEDIT issue

Author: Nileshkul
Subject: CPU time Vs Number of records
Posted: Mon May 09, 2016 4:05 pm (GMT 5.5)

Dear All,

I have a VSAM file which is fairly constant volume - sort of control data.

The file is read in batch. It has around 200 K records. The file is read in batch modules via keys. If I reduce record count to 20 K (i.e. 10% of original), will the keyed reads perform faster in batch? And if yes will that be considerable improvement to CPU time?

Thanks,
Nilesh.

↧

JCL & VSAM :: RE: CPU time Vs Number of records

May 9, 2016, 3:59 am

≫ Next: JCL & VSAM :: RE: CPU time Vs Number of records

≪ Previous: JCL & VSAM :: CPU time Vs Number of records

Author: Robert Sample
Posted: Mon May 09, 2016 4:29 pm (GMT 5.5)

Have you read the Demystifying VSAM Redbook? If not you need to. Direct (keyed) reads use the index component. A LISTCAT will tell you how many levels the index has and hence how many accesses will be needed for each record retrieval. However, you will NOT be reducing CPU usage much by this change.
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth

↧

JCL & VSAM :: RE: CPU time Vs Number of records

May 9, 2016, 5:12 am

≫ Next: COBOL Programming :: RE: Facing xml parser exception 798761

≪ Previous: JCL & VSAM :: RE: CPU time Vs Number of records

Author: Robert Sample
Posted: Mon May 09, 2016 5:42 pm (GMT 5.5)

Follow-up: have you talked to your site support group? If the data set (only Unix System Services has files on a z/OS system) is read only by key, BLSR should provide some performance improvement -- as long as BLSR is installed and functional at your site. Whether or not it is, only someone at your site can tell you.

And is your goal to reduce CPU usage? If so, reducing the number of records in a VSAM data set that is directly read anyway should be just about the LAST place you should look for CPU reductions!
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth

↧

COBOL Programming :: RE: Facing xml parser exception 798761

May 9, 2016, 7:21 am

≫ Next: COBOL Programming :: RE: Facing xml parser exception 798761

≪ Previous: JCL & VSAM :: RE: CPU time Vs Number of records

Author: muralikrishnan_new
Subject: Reply to: Facing xml parser exception 798761
Posted: Mon May 09, 2016 7:51 pm (GMT 5.5)

Hi Murugan,
Sorry for the late response. I am just sharing the my piece of code. Hope it would help you.

a) It seems the XML-parse in cobol will work for only single string. Hence I tried to convert the input as mentioned below,

Code:

<Name> <FirstName>Jack</FirstName><LastName>Nicholson</LastName> </Name>

b) I have read the file and formed each segment as single string using the String function.

Please find below the piece of code,

Code:

IDENTIFICATION DIVISION.
PROGRAM-ID. COBGG.
ENVIRONMENT DIVISION.
INPUT-OUTPUT SECTION.

FILE-CONTROL.
SELECT I-INXML ASSIGN TO INXML
FILE STATUS IS WS-INXML-FS.

SELECT U-UTXML ASSIGN TO UTXML.

DATA DIVISION.
*-------------

FILE SECTION.
*-------------
FD I-INXML
RECORD IS VARYING FROM 1 TO 121 DEPENDING ON WS-REC-LT
RECORDING MODE IS V.

01 XML-TEST-DOC PIC X(121).

FD U-UTXML
LABEL RECORD STANDARD
RECORDING MODE F
BLOCK 0 RECORDS.

01 UTXML-REC.
02 FNAME PIC X(35) VALUE SPACES.
02 LNAME PIC X(35) VALUE SPACES.

WORKING-STORAGE SECTION.
*=========================================

01 WS-WV.
*--------
03 WS-INXML-FS PIC 9(02).
03 WS-INXML-EOF PIC X(01).
03 WS-XML-DOC PIC X(121) VALUE SPACES.
03 WS-XML-DATA PIC X(121) VALUE SPACES.
03 WS-XML-PPR-DATA PIC X(5000) VALUE SPACES.
03 WS-POINTER-VAL PIC S9(06).
03 WS-REC-LT PIC S9(03) COMP.
03 WS-CRT-TAG PIC X(20) VALUE SPACES.
03 WS-NAME-CNT PIC S9(09) PACKED-DECIMAL.
03 WS-TOT-NAME-CNT PIC S9(09) PACKED-DECIMAL.
03 WS-TLLY-CNT PIC S9(03) PACKED-DECIMAL.
03 WS-TLR-SPC-CNT PIC S9(03) PACKED-DECIMAL.
03 WS-LD-SPC-CNT PIC S9(03) PACKED-DECIMAL.
03 WS-TOT-SPC-CNT PIC S9(03) PACKED-DECIMAL.
03 WS-LTH-XML-VL PIC S9(03) PACKED-DECIMAL.
03 WS-STG-STT-POS PIC S9(03) PACKED-DECIMAL.

PROCEDURE DIVISION.
*-------------------

PERFORM START-XML-PARSE.

PERFORM PROCESS-XML-PARSE
UNTIL WS-INXML-EOF=HIGH-VALUES

PERFORM END-OF-XML-PARSE.

STOP RUN.

******************************************A-LEVEL*********** *****

START-XML-PARSE.
*-------------------

PERFORM INITIALIZE-PGM.

PERFORM OPEN-FILE.

PROCESS-XML-PARSE.
*-------------------

PERFORM PROC-XML-PARSE.

END-OF-XML-PARSE.
*-------------------

PERFORM CLOSE-FILE.

******************************************Z-LEVEL*********** *****

INITIALIZE-PGM.
*--------------

MOVE LOW-VALUES TO WS-INXML-EOF.
MOVE 1 TO WS-POINTER-VAL.
MOVE ZEROES TO WS-TOT-CNT.
MOVE ZEROES TO WS-TLLY-CNT.
MOVE ZEROES TO WS-NAME-TOT-CNT.

OPEN-FILE.
*--------------

OPEN INPUT I-INXML.
OPEN OUTPUT U-UTXML.

IF WS-INXML-FS = '00'
CONTINUE
ELSE
DISPLAY 'STATUS OPEN' WS-INXML-FS
STOP RUN
END-IF

CLOSE-FILE.
*----------------

CLOSE I-INXML
U-UTXML.

PROC-XML-PARSE.
*--------------------

MOVE SPACES TO WS-XML-DOC.

READ I-INXML INTO WS-XML-DOC
AT END
MOVE HIGH-VALUES TO WS-INXML-EOF
NOT AT END
PERFORM STAGE-XML-TEXT
END-READ.

IF WS-INXML-FS = '00'
CONTINUE
ELSE
DISPLAY'FILE STATUS' WS-INXML-FS
END-IF.

STAGE-XML-TEXT.
*----------------

MOVE ZEROES TO WS-TLLY-CNT.

INSPECT WS-XML-DOC TALLYING WS-TLLY-CNT FOR ALL 'NAME'
IF WS-TLLY-CNT > 0
ADD 1 TO WS-NAME-CNT
END-IF

IF WS-NAME-CNT > 0
PERFORM VALID-XML-DATA
END-IF

IF WS-NAME-CNT = 2
PERFORM XML-PARSE-DATA
MOVE SPACES TO WS-XML-PPR-DATA
MOVE SPACES TO WS-XML-DATA
MOVE ZEROES TO WS-NAME-CNT
MOVE 1 TO WS-POINTER-VAL
END-IF.

VALID-XML-DATA.
*-----------------

MOVE ZEROS TO WS-TLR-SPC-CNT
WS-LD-SPC-CNT
WS-TOT-SPC-CNT
WS-TLLY-CNT.

INSPECT FUNCTION REVERSE(WS-XML-DOC) TALLYING
WS-TLR-SPC-CNT FOR LEADING SPACES

INSPECT WS-XML-DOC TALLYING
WS-LD-SPC-CNT FOR LEADING SPACES

COMPUTE WS-TOT-SPC-CNT = WS-TLR-SPC-CNT +
WS-LD-SPC-CNT
END-COMPUTE

COMPUTE WS-LTH-XML-VL = LENGTH OF WS-XML-DOC -
WS-TOT-SPC-CNT
END-COMPUTE

COMPUTE WS-STG-STT-POS = WS-LD-SPC-CNT + 1
END-COMPUTE

STRING WS-XML-DOC(WS-STG-STT-POS:WS-LTH-XML-VL) DELIMITED
BY SIZE
INTO WS-XML-PPR-DATA
WITH POINTER WS-POINTER-VAL

XML-PARSE-DATA.
*--------------

XML PARSE WS-XML-PPR-DATA PROCESSING PROCEDURE NAMEPARSE
ON EXCEPTION
DISPLAY 'XML DOC ERROR ' XML-CODE
STOP RUN
END-XML.

NAMEPARSE.
*===========

EVALUATE XML-EVENT
WHEN 'END-OF-INPUT'
CONTINUE
WHEN 'START-OF-ELEMENT'
MOVE XML-TEXT TO WS-CRT-TAG
WHEN 'CONTENT-CHARACTERS'
PERFORM CONTENTELEMENT
WHEN 'END-OF-ELEMENT'
PERFORM ENDELEMENT
INITIALIZE WS-CRT-TAG
WHEN 'ERROR'
MOVE '1' TO ERR
WHEN 'EXCEPTION'
DISPLAY 'ZOEFPARSE:XML-EXCEPTION ' XML-CODE

END-EVALUATE.

WRITENAME.
*==========
WRITE UTXML-REC.

CONTENTELEMENT.
EVALUATE WS-CRT-TAG
WHEN 'FIRSTNAME'
MOVE XML-TEXT TO MSG-TYPE-CD
WHEN 'LASTNAME'
MOVE XML-TEXT TO OBJ-CD
END-EVALUATE.

ENDELEMENT.
EVALUATE XML-TEXT
WHEN 'NAME'
PERFORM WRITENAME
INITIALIZE UTXML-REC

END-EVALUATE.

let me know if you face any issues.
_________________
Thanks,
Murali

↧

COBOL Programming :: RE: Facing xml parser exception 798761

May 9, 2016, 7:33 am

≫ Next: JCL & VSAM :: RE: CPU time Vs Number of records

≪ Previous: COBOL Programming :: RE: Facing xml parser exception 798761

Author: Rohit Umarjikar
Posted: Mon May 09, 2016 8:03 pm (GMT 5.5)

Quote:

Sorry for the late response.

You did nothing to be sorry for and in fact you are helping him in a weeks time which is not really late btw you are not obligated to reply it is as and when you want to when you have time

and if he were to be seriously needing help then he would have came back before you even could reply.
_________________
Regards,
Rohit Umarjikar
"Some things Man was never meant to know. For everything else, there's Google"

↧

JCL & VSAM :: RE: CPU time Vs Number of records

May 9, 2016, 7:46 am

≫ Next: DFSORT/ICETOOL :: RE: Performing addition using JCL sort card

≪ Previous: COBOL Programming :: RE: Facing xml parser exception 798761

Author: Rohit Umarjikar
Posted: Mon May 09, 2016 8:16 pm (GMT 5.5)

Welcome!!

Quote:

The file is read in batch. It has around 200 K records. The file is read in batch modules via keys. If I reduce record count to 20 K (i.e. 10% of original), will the keyed reads perform faster in batch? And if yes will that be considerable improvement to CPU time?

1. Why would you reduce the records at first place? Do you not then lose the accounts by doing so, if not then explain why and what are these 200k records?
2.If it is read by keys then, why do you think that a performance issue?
3.Why do not try doing what you say so and let us know?
4. What is current CPU usage for 200k records? What is your expectation that you should see after your change?
5. Take a help here as well as here and check the VSAM definition.
6. Last but not least , look at Robert's Signature and that should suffice the discussion.

Answers to the above question will make others to suggest you in a specific and much better way.
_________________
Regards,
Rohit Umarjikar
"Some things Man was never meant to know. For everything else, there's Google"

↧

DFSORT/ICETOOL :: RE: Performing addition using JCL sort card

May 9, 2016, 8:40 am

≫ Next: DFSORT/ICETOOL :: Use of Parm in SORT

≪ Previous: JCL & VSAM :: RE: CPU time Vs Number of records

Author: Rohit Umarjikar
Posted: Mon May 09, 2016 9:10 pm (GMT 5.5)

Bill, One question in this case does it require to do sort when we only deal with single category i.e. 'IT/it' records or DFSORT smart enough to know not to do sorting here after include? if not then , is there a way we let DFSORT know that to opt out for the sorting in such situations as there is only record all the time in SORTOUT?
_________________
Regards,
Rohit Umarjikar
"Some things Man was never meant to know. For everything else, there's Google"

↧

Latest Images