AS 400 job scheduler details
W J Malsbury
I am trying to complete/change some documentation and that would be very
beneficial.
Thanks in advance.
--
WJ Malsbury
Pieter Zegwaart
QGPL)
Object can (of course) be saved and restored but you can't edit it, and
thats a big shame.
pieter
"W J Malsbury" <mals...@telus.net> wrote in message
news:Tl989.256$Il4....@news2.telusplanet.net...
Tim M
the schedule.
"Pieter Zegwaart" <zegw...@wanadoo.nl> wrote in message
news:fGb89.873$AU.1...@castor.casema.net...
René H. Hartman
It's the *JOBSCD type object QJOBSCD in QUSRSYS (or something close, I'm
typing from memory here. Anyway, there's only one type *JOBSCD object in
QUSRSYS, if I remember correctly).
--
Vriendelijke groeten / Kind regards
René H. Hartman
R.H. Hartman Automatiserings Consultancy
www.hac-maarssen.nl
-----= Posted via Newsfeed.Com, Uncensored Usenet News =-----
http://www.newsfeed.com - The #1 Newsgroup Service in the World!
-----== 100,000 Groups! - 19 Servers! - Unlimited Download! =-----
Pieter Zegwaart
items from other jobschedulars (read: an others AS/400) is impossible. Had
IBM stored this schedule info in an otherway it would have been more
conveniant.
Pieter
"Tim M" <scot...@cox.net.xyz> wrote in message
news:y1j89.37925$hg.3...@news1.central.cox.net...
Mike Buglass
> Yes Tim there are commands to manipulate the schedule, however
> importing items from other jobschedulars (read: an others AS/400)
> is impossible. Had IBM stored this schedule info in an otherway it
> would have been more conveniant.
>
> Pieter
>
>
Not quite impossible. APIs exist that allow you to retrieve the
schedule entries (look in the information center under programming/CL &
APIs/API for details - I cannot remember the actual APIs at the
moment).
You could use the APIs to find the schedule entries and then CHGJOBSCDE
to update them as needed (I used them to merge schedule entries from
multiple machines to a single machine).
--
Mike Buglass
Philippe...@hardis.fr
will not be a free product.... IBM JobScheduleur (5722JS1), or ROBOT/400,
or SYSAUTO etc
Jouster
putting it on a 400.
ALL of the zillion files are flat files that do NOT have DDS
definitions. (Accessed via Cobol only) In time, we will be able
convert some to database files and be able to make quick patches with
SQL, etc.
Meanwhile, is there a third party vendor that has a utility that will
allow file editing of records of any length?
SPF and File Aid come to mind for the larger mainframes. Is there
something like that for the 400?
Cheers Don
°º°`°º°ø,¸¸,ø°º°`°º°ø,¸¸,ø°º
Denny Davis
any file, data based or not, in character or hex mode.
If you are interesed, I can email you the source.
You should also look at www.wrkdbf.com
This is a great little file editor. Better yet,it is FREE thanks to
Bill Reger at Levitz Furniture. It is not as fast as some of the
commercial products, but it has all the features.
Don't know how it will work with non-DB files.
The commercial product DBU has a good work around for getting at
non-DB files and making them look like they were. It was created for
working in the S36 environment on a 400.
Denny
On Fri, 11 Oct 2002 17:57:23 -0500, Jouster <jou...@charter.net>
wrote:
Njål Fisketjøn
>Meanwhile, is there a third party vendor that has a utility that will
>allow file editing of records of any length?
>
>SPF and File Aid come to mind for the larger mainframes. Is there
>something like that for the 400?
The AS/400 has a tool called EDTF (Edit File)
--
Njål Fisketjøn, FIGU DATA AS
n...@figu.no / http://www.figu.no
Jouster
Using WRKSPLF, requires a lot of keystrokes to send a file to the
printer. Is there a "smart way" to avoid having to always having to
key the printer name, press F10, scroll down and specify options like
Print on both sides, etc. Can a command be set up that I could enter
next to the spool file, like 'P' instead of '2'?
Jouster
X'ing them out. I have not discovered how to redisplay them wo exiting
the session.
Anyone know?
Thanks, Don
Shane Mingins
--
shanem...@yahoo.com.clothes
remove clothes before replying
"Jouster" <jou...@charter.net> wrote in message
news:h36kqucndt6ejf6dm...@4ax.com...
Denny Davis
On Sun, 13 Oct 2002 20:08:06 -0500, Jouster <jou...@charter.net>
wrote:
Martin Rowe
> I like the ability to exclude source lines from display in SEU, by
> X'ing them out. I have not discovered how to redisplay them wo exiting
> the session.
Don
F5=refresh to unhide them all, or you can selectivly unhide blocks with
SF/SFn (show first line/first n lines) or SL/SLn (show last line/last n
lines). Hit F1 with the cursor on a line number to see all the line
commands available.
Regards, Martin
--
mar...@dbg400.net jam...@firstlinux.net http://www.dbg400.net /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ /
Source free test environment tools and others (file/spool/misc) X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
Martin Rowe
If the report always has the same unique file name, and you always want it
to have the same attributes (duplex, output queue, etc), you can do a
CHGPRTF on the printer file (not the spool file) to permanently change the
way it will be generated[1].
Otherwise you might want to look at something like Brad Stones SPLTOOL[2]
which acts as a WRKSPLF replacement and includes user defined options. That
would let you set up your 'P' option as above.
I also have a free WRKSPLF/WRKOUTQ replacement[3] that, although it doesn't
include user options, could be tweaked to add them as it comes as source
code. If you're new to iSeries, then I guess you won't be that experienced
in RPG & CL, so you might not be able to go that route.
Regards, Martin
[1] That is, unless the program that produces it determines those attributes
at run time.
[2] http://www.spltool.com
[3] http://www.dbg400.net/usroutq.html
Charles Wilt
from the WRKSPLF screen to do so.
With the assistance level set to Intermediate, you'll have a command line
at the bottom of the screen. This allows you to specify options without
prompting. For example, to have a spool file go to a different printer I
put a '2' on the spool file and a 'DEV(MYOTHERPRT)' on the command line.
To figure out the Keywords your need, ie the DEV above, press F11 while
in the prompt screen.
HTH,
Charles
In article <oq5kqu84g7kqmf43j...@4ax.com>,
jou...@charter.net says...
Steve Landess
> allow file editing of records of any length?
>
There is a freeware utility called WRKDBF...
see www.wrkdbf.com to download it.
There is another one (NOT free) that is very good. DBU (Data Base Utility)
is distributed by Prodata. see http://www.prodatacomputer.com/dbu.htm
Charles Wilt
from the WRKSPLF screen to do so.
With the assistance level set to Intermediate, you'll have a command line
at the bottom of the screen. This allows you to specify options without
prompting. For example, to have a spool file go to a different printer I
put a '2' on the spool file and a 'DEV(MYOTHERPRT)' on the command line.
To figure out the Keywords your need, ie the DEV above, press F11 while
in the prompt screen.
HTH,
Charles
In article <oq5kqu84g7kqmf43j...@4ax.com>,
jou...@charter.net says...
Charles Wilt
screens. All IBM screens that have multiple assistance levels use the
F21 to set.
Charles
Alex Nubla
I am sort of partial to Questview since I used to work for the company
and I know Dave McKenzie real well (the guy who wrote it). Contact:
http://www.questview.com/
I would also recommend DBU from Prodata. You can reach them at
http://www.prodatacomputer.com/
These 2 are the leading Database Utility for the iSeries. Since I am
lucky enough to have both tools here at my client presently, I revert
to both software using their strengths.
1. Questview retains/remembers the last prompt request.
2. Questview has more flexibility when scanning fields or field names.
3. Questview has better flexibility in OPNQRYF.
4. Questivew has a Programmer & User Audience - allowing you to create
a program from Questview that can be used by user. DBU only creates a
"Programmer View" program.
5. Questview does not break long fields
6. You can change the File you are viewing on the fly from Questview.
In DBU, you have to go to DBR to change the file name.
7. DBU updates user space & data areas.
8. DBU has a better Database Relation Screen (DBR). Questview is
overwhelming with colors. I would change my session attributes to
remove column seperator on turquoise for better viewing. Questview
however show Unique Keys while DBU does not.
9. Questview has a Joiner Utility
10. DBU had DBUAUT first. View now has VIEWAUTH. This provides further
restriction to users using the utility.
11. DBU handles update of DDM Files. Questview doesn't support this.
12. DBU sold more copies than Questview. Both are priced similarly.
Here's their detailed comparison. You be the judge:
http://www.questview.com/features.htm
http://www.prodatacomputer.com/DbuFtrs.htm
For further list, check out this site.
http://213.176.1.196:800/Default/www.mcpressonline.com/mc/.3d317b9a
Regards,
Alex Nubla
http://www.as400journal.com
Jouster <jou...@charter.net> wrote in message news:<mblequ076fb3cubon...@4ax.com>...
Jouster
record definitions and generates DDS? Pretty straightforward, but I
just don't have the time to do it right now.
Customsoft
I have something originally used to convert DASDL to DDS in a Unisys
to AS/400 conversion. It was then modified to do 01 Cobol records.
It runs on a PC, compiles using Microfocus Cobol (DOS).
The field names are F0001, F0002, etc. but there is a COLHDG and an
ALIAS with the real field names.
Here is a sample input 01 record...
032200 01 FWRS-REC.
032400 03 FWRS-COMPANY-NO PIC 9(02).
032500 03 FWRS-WAREHOUSE PIC X(02).
032600 03 FWRS-SERIAL-START PIC X(07).
032700 03 FWRS-SERIAL-END PIC 9(04).
032800 03 FWRS-COMMENT PIC X(10).
032900 03 FWRS-RICK-NO PIC 9(04).
033000 03 FWRS-TIER-NO PIC 9(02).
033100 03 FWRS-DIST-CODE PIC 9(03).
033200 03 FWRS-BARRELS PIC S9(04).
033300 03 FWRS-ENTRY-DATE PIC 9(06).
033400 03 FWRS-STATUS-FLAG PIC X(01).
033500 03 FWRS-INITIALS PIC X(03).
033600 03 FWRS-ADD-DATE PIC 9(06).
033700 03 FWRS-ADD-TIME PIC 9(08).
033800 03 FWRS-CHANGE-DATE PIC 9(06).
033900 03 FWRS-CHANGE-TIME PIC 9(08).
And the DDS output created..
R WRS
A F0001 2S 0 ALIAS(WRS_COMPANY_NO)
A COLHDG('COMPANY' 'NO' )
A F0002 2 ALIAS(WRS_WAREHOUSE)
A COLHDG('WAREHOUSE' )
A F0003 7 ALIAS(WRS_SERIAL_START)
A COLHDG('SERIAL' 'START' )
A F0004 4S 0 ALIAS(WRS_SERIAL_END)
A COLHDG('SERIAL' 'END' )
A F0005 10 ALIAS(WRS_COMMENT)
A COLHDG('COMMENT' )
A F0006 4S 0 ALIAS(WRS_RICK_NO)
A COLHDG('RICK' 'NO' )
A F0007 2S 0 ALIAS(WRS_TIER_NO)
A COLHDG('TIER' 'NO' )
A F0008 3S 0 ALIAS(WRS_DIST_CODE)
A COLHDG('DIST' 'CODE' )
A F0009 4S 0 ALIAS(WRS_BARRELS)
A COLHDG('BARRELS' )
A F0010 6S 0 ALIAS(WRS_ENTRY_DATE)
A COLHDG('ENTRY' 'DATE' )
A F0011 1 ALIAS(WRS_STATUS_FLAG)
A COLHDG('STATUS' 'FLAG' )
A F0012 3 ALIAS(WRS_INITIALS)
A COLHDG('INITIALS' )
A F0013 6S 0 ALIAS(WRS_ADD_DATE)
A COLHDG('ADD' 'DATE' )
A F0014 8S 0 ALIAS(WRS_ADD_TIME)
A COLHDG('ADD' 'TIME' )
A F0015 6S 0 ALIAS(WRS_CHANGE_DATE)
A COLHDG('CHANGE' 'DATE' )
A F0016 8S 0 ALIAS(WRS_CHANGE_TIME)
A COLHDG('CHANGE' 'TIME' )
I think it drops group field names.
Let me know if you are still interested.
Phil
Jouster <jou...@charter.net> wrote in message news:<k1krrug3g07rt5qe1...@4ax.com>...
Michael
mainframe COBOL application to the AS/400. The app had over a thousand
internally defined files and over 14,000 unique field data names. All 1,200
plus file definitions were in copy books. However, common fields in
separate files often had different names, e.g. MAST-SOCIAL-NUM, TRANS-SSN,
etc. Further, a given field could be DISPLAY format in one file and PACKED,
in another.
We wanted to build a /400 data base with common readable field names and
consistent field attributes.
We tackled this problem in 3 phases.
Phase I
We created a dummy COBOL program with a giant DATA DIVISION that had all
1,200 copy books. We used the /400 COBOL compiler to parse this source code
and set the CRTLBLPGM control parameters to print a data map. We then
converted the map from a spool file to a database table of field names and
attributes.
Phase II
We parsed multi word names like WRK-SS-NUM into WRK, SS, and NUM. We then
used the database JOIN function to link records in the field names file to
other similar records in the same file joining by words in the field name,
by field length, by relative position in the record etc. We then manually
edited this table to flag common fields and establish meaningful field names
and consistent attributes.
Phase III
We used the field names and attribute file to build DDS for all 1,200 files
in the application.
As I said above this was all several years ago in a former job. I still
have good friends in that company. If your project is big enough for this
kind of an approach I will be happy to check if the utility we built still
exists. Even if it does not the outline above may be of some use.
Michael Sicilian
"Jouster" <jou...@charter.net> wrote in message
news:k1krrug3g07rt5qe1...@4ax.com...