S36 Information

[minishoppe]

Re: S36 Information

Hi GLS,

I think I can look at the objects in the library when it shows me after taking command "B" browse on the library members and it shows me object type "O".

Thanks,
Mini

[GLS400]

Re: S36 Information

Hi minishoppe:

File Attributes:
I=indexed
S=Sequential
X=Alternate Index (logical)
D=Demand

A demand file is usually full and the records are processed by relative record number. The only time I've seen demand files used on the system 36 is with MAPICS. Is that what you are running there?


Object type O is an Object......Compiled program

Best of Luck
GLS

[minishoppe]

Re: S36 Information

Thanks GLS.

How can I see the member type is RPG program or OCL or a display file or a DB file.

Please let me know.

Thanks,

Mini

[GLS400]

Re: S36 Information

Hi Mini:

Sorry but those memory cells have long ago been burned out. If you can send a print screen of what you see when you do the libr mylib command I may be able to help.

GLS

[minishoppe]

Re: S36 Information

Hi GLS,

Here is the screenshot attached when I run the command "File" but it displays me not exact DB file structure and showing the something else and I also want to know, how can I see the files from particular library.

I have taken the inventory of RPG programs and Procedures already.

Thanks for this.

Please advise the above problem.

Regards,
Mini

[FaStOnE]

Re: S36 Information

On the S/36, you're not going to see a File Structure like you would on the iSeries. DDS (File Specifications) didn't show up until the AS/400 took center stage back in June, 1986.

The only way I know of to check a file structure on the S/36 was to find the RPG (Most likely RPGII) and to look for the I-Specs inside. This would give you a "look" at the definition of the DB. But, most likely it would only show you what was needed for that specific program. In other words, the DB might have an LRECL of 128 bytes, but only use bytes 23 through 50 for a specific program.

I know that what GLS and others have told you is confusing, but the System/36 use and admin went to the wayside so long ago, that we really can't remember all the commands to recommend a course of action for you.

You are VERY lucky in the fact that it looks like you have POP installed on that system. Otherwise, you would have to find all the commands (SEU, SDA, etc) and run them individually.

Again, if you're lucky, you might find IDDU file descriptions for your DBs. But, that wasn't always used. Most programmers used the method I described above.

Good luck!

-R

[GLS400]

Re: S36 Information

Hi minishoppe:

Fastone is correct. The only way to get your file layouts is

1. Locate a RPG program with all fields defined.
2. Hope someone has defined IDDU against the the file of interest
3. Locate the documentation

Best of Luck
GLS

[minishoppe]

Re: S36 Information

Thanks GLS and Fastone for your response.

If these are the only ways to get the files information then have to follow it.
Thanks again.

Mini

[minishoppe]

Re: S36 Information

Also..How can I find the display files..? Can anyone advise..?

[FaStOnE]

Re: S36 Information

S/36 screens are defined with format specifications (S and D in column 6), that must be compiled with a program called $SFGR (the screen format generator).

From what I remember (and this is from brain cells that have long been inebriated more than a few times) the Display files had to be defined INTERNALLY. So, you had specifications that defined the display (just like the old O-Specs for reports)

I know it's a pain .. but, that's just the way it was.

-R

[DeadManWalks]

Re: S36 Information

Ture, the display files used buffer ofsets in the "O" specs to send the data out. The screen were Read to get the information in.

I have an example;

Input;

I* FORMAT-$$CREF                                     
I                                        1   1 $SCRID
I                                        2   2 $CCD  
I                                        3  27 $DES 

OutPut;

OCRT     E                $$CREF                 
O                                   K8 '$$CREF  '
O                         $INO       6           
O                         $REF      13           
O                         $DNO      19              
O                         @#Z001Y   27           
O                         $DES      53 

[arrow483]

Re: S36 Information

Some shops never used IDDU. You may find F & I specs (look like RPG specs, but just File and Input) for the files. These often had a member name that looked like the file name.

A period in a file name indicated "group" files. This allowed the pgmr to save all the C. files in a single command. Some places would use them to group files by application or location (somewhat like we use libraries or schemas today).

[minishoppe]

Re: S36 Information

Hi Guys,

Thanks for your response..these are really helpful to push my work ahead.

Can you please anyone put some light on the Migartion of S/36 application to AS400 Native S/36 environment.

Would there be any need to any changes when we will migrate it to AS400 S/36 Environment.

Please advise.

Thanks,
Mini

[FaStOnE]

Re: S36 Information

Migration to S/36 environment isn't too bad, but yes, there are some minor changes that would need to be made. Mostly due to the fact that there are a few commands on the S/36 that aren't directly migrated. I sincerely don't remember what they are, but... there are some.

[GLS400]

Re: S36 Information

Hi Mini:

If you're going to migrate to the S36 environment here is a good place to start.

http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c4141520.pdf

You will definately need to know what communications will be used including PC support and/or any modems etc.

As far as the code goes it is 99% directly compatible.

Best of Luck
GLS