Thanks once again.
We were able to issue a "SET FCTL" command inside STATN and then Text
and view the entire STDLIST appropriately with all the Suprtool and
Suprlink output record counts.
To roll this back, we just had to issue a "SET NOFCTL" command. This
command has to be executed because the "SET FCTL" command is a permanent
one, irrespective of whether you exit out of STATN or logout of your
session.
With Best Regards
Raghu Rao
________________________________
From: Neil Armstrong [mailto:[log in to unmask]]
Sent: Monday, March 24, 2008 10:49 AM
To: Rao, Raghu; [log in to unmask]; [log in to unmask]
Subject: RE: Job run listing does not show some line numbers
Dear Raghu,
An educated guess would be in how the spool file is moved and/or being
listed. What happens if you
list with Display functions on? A guess would be that CCTL was munged in
one of the moves/copies.
I am not sure that I understand how the output files/stdlists are
processed and who or what is looking
at them, but that is where I would start to look. The first step is to
list them with display functions, you
may see that the lines are there but with an extra or odd escape
sequence.
Sincerely,
Neil Armstrong
Robelle
-----Original Message-----
From: Rao, Raghu [mailto:[log in to unmask]]
Sent: Monday, March 24, 2008 10:32 AM
To: [log in to unmask]; [log in to unmask]
Subject: Job run listing does not show some line numbers
Hi all,
We observed a strange problem over the weekend. Our production
jobs run and produce output file as usual in OUT.HPSPOOL. From there,
its picked up by CONMAN and then eventually moved to STATN. The original
copy from OUT.HPSPOOL is purged and the history of last 50 jobs runs are
maintained in the STATN records.
We have a job that runs daily. The job as such completed
successfully fine and does not show any abend or aborts. The job
executes Suprtool step. It's a fairly simple step and has been running
fine all these years. The job run listing shows perfectly fine on Friday
nights run, but is missing some line numbers in the Thursday nights run.
The line numbers on the job run listing 417, 433 and 453-454 appear fine
on the Friday's run. These lines are basically the output count from the
Suprtool and Suprlink statements.
384 :SUPR
385
389 SUPRTOOL/iX/Copyright Robelle Solutions Technology
Inc. 1981-2003.
390 (Version 4.7.02) FRI, MAR 21, 2008, 11:48 PM Type H
for help.
391 >
392 INPUT xcg200ws
393 >
394 DEFINE link-key,1,11,BYTE
395 >
396 DEFINE record-body,91,610,BYTE
397 >
398 DEFINE zip-code,7,10,BYTE
399 >
400 DEFINE id-num,17,10,BYTE
401 >
402 DEFINE bus-seg,1,6,BYTE
403 >
404 DEFINE last-name,27,14,BYTE
405 >
406 DEFINE card-date,41,50,BYTE
407 >
408 SORT link-key
409 >
410 EXTRACT link-key, zip-code, id-num, bus-seg
411 >
412 EXTRACT last-name, card-date, record-body
413 >
414 OUTPUT xcg200wt, LINK
415 >
416 XEQ
417 IN=101, OUT=101. CPU-Sec=1. Wall-Sec=1.
418
419 >
420 >
421 LINK INPUT xcg200wt BY link-key
424 Suprlink/iX/Copyright Robelle Solutions Technology
Inc. 1988-2003
425 (Version 4.7.02) FRI, MAR 21, 2008, 11:48 PM Type H
for Help.
427 >
428 LINK LINK xcg200tq BY link-key OPTIONALLY
429 >
430 LINK OUTPUT xcg200wu
431 >
432 LINK EXIT
433 In=101. Out=101. CPU-Sec=1. Wall-Sec=1.
434 >
435 >
436 INPUT xcg200wu
437 >
438 SORT zip-code
439 >
440 SORT id-num
441 >
442 SORT bus-seg
443 >
444 SORT last-name
445 >
446 SORT card-date
447 >
448 EXTRACT zip-code, id-num, bus-seg, last-name,
card-date, record-body, tpv-name
449 >
450 OUTPUT xcg200w2
451 >
452 XEQ
453 Warning: Using Output XCG200W2,Link
454 IN=101, OUT=101. CPU-Sec=1. Wall-Sec=1.
455
But these similar output on Thursday's job run is missing these
line numbers. Basically, the line numbers 417 and 433 are missing and we
are not able to determine the outfile file records counts from those
steps.
384 :SUPR
385
389 SUPRTOOL/iX/Copyright Robelle Solutions Technology
Inc. 1981-2003.
390 (Version 4.7.02) THU, MAR 20, 2008, 11:40 PM Type H
for help.
391 >
392 INPUT xcg200ws
393 >
394 DEFINE link-key,1,11,BYTE
395 >
396 DEFINE record-body,91,610,BYTE
397 >
398 DEFINE zip-code,7,10,BYTE
399 >
400 DEFINE id-num,17,10,BYTE
401 >
402 DEFINE bus-seg,1,6,BYTE
403 >
404 DEFINE last-name,27,14,BYTE
405 >
406 DEFINE card-date,41,50,BYTE
407 >
408 SORT link-key
409 >
410 EXTRACT link-key, zip-code, id-num, bus-seg
411 >
412 EXTRACT last-name, card-date, record-body
413 >
414 OUTPUT xcg200wt, LINK
415 >
416 XEQ
418
419 >
420 >
421 LINK INPUT xcg200wt BY link-key
424 Suprlink/iX/Copyright Robelle Solutions Technology
Inc. 1988-2003
425 (Version 4.7.02) THU, MAR 20, 2008, 11:40 PM Type H
for Help.
427 >
428 LINK LINK xcg200tq BY link-key OPTIONALLY
429 >
430 LINK OUTPUT xcg200wu
431 >
432 LINK EXIT
434 >
435 >
436 INPUT xcg200wu
437 >
438 SORT zip-code
439 >
440 SORT id-num
441 >
442 SORT bus-seg
443 >
444 SORT last-name
445 >
446 SORT card-date
447 >
448 EXTRACT zip-code, id-num, bus-seg, last-name,
card-date, record-body, tpv-name
449 >
450 OUTPUT xcg200w2
451 >
452 XEQ
453 Warning: Using Output XCG200W2,Link
454 IN=88, OUT=88. CPU-Sec=1. Wall-Sec=1.
455
Has anyone else noticted this strange behaviour before ? Is this
a STATN or a SUPRTOOL, SUPRLINK issue ? OR is it time to change my
glasses ?
With Best Regards
Raghu Rao.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
