Please give MORE information. Like some of the previous questions you have posted, you have a knack for making things complicated.
What (Application Programming) Language are you talking about. Where have you ever seen this term mentioned? Can you show us a specific Google link? Or was it just someone mouthing empty words?
Also, when people are trying to help you, and they ask for additional information (in regard to your problem), a reply (even if to say "It's fixed") would be appreciated. Thank you.
I really appreciate the helps extended by the helpboard previously.
Regarding the current problem, it is related to the LINKs card for COBOL programs. Fractional links are the one which are not complete by itself and they got linked to some other links.... ( this is what I know about them.. and which I wanna clarify )
OR IT HAS SOMETHING TO DO WITH THE ENTRY, MODE and NAME PARAMETER in the link card.
INCLUDE SYSLIB(SIWRLOG)
LIBRARY *(SIPRMFRT)
ENTRY SIPRM
MODE AMODE(31),RMODE(ANY)
NAME SIAR02(R)
Once again I will appreciate ur help...
Regards,
Sushil _________________ "Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity."
Thanks for the useful information. The link cards you have shown are fairly standard (in many shops). So far as trying to come up with some definition for "fractional link", I wonder if perhaps you are talking about what most people might refer to "static linkage".
In some shops, you might have the following scenario:-
1: Assemble/Compile each of the programs into Objects. One Object Module per Source Module. But DO NOT Link-edit at this stage.
2: Using Cards (like the ones you have shown), you now (statically) Link-edit various collections of Object Modules into a single (large) Load-Module.
In these cases, the individual programs are never actually link-edited all by themselves, so you'll never find (say) a Load Module name corresponding to each of the original Source programs. And this being the case, you'll need to come up with what you could call a "composite name" for the single (large) Load Module that you will finally create. I have seen this type of thing done for IMS online systems, as well as massive Batch Assembler systems. It is done for performance reasons.
Joined: 10 Dec 2004 Posts: 110 Topics: 8 Location: Colorado USA
Posted: Tue Jan 31, 2006 1:37 pm Post subject:
Quote:
It is done for performance reasons.
In addition, I believe it is also done for control. For example, you might have a program called XYZ. If you do a static call to this program then you can be sure that you are getting your copy of that program.
I work for an insurance software vendor. Our calls are mostly static. Each of the modules are in fact linked seperatly, and then "composite" load modules are built as needed.
This can be done with explicit INCLUDE statements, or if you have the CALL option of the linkage editor turned on, then the syslib will be used to try to automatically resolve the external references.
In addition, you can replace a single CSECT in an existing composite, by doing an include for the module you wish to replace, followed by an include for the composite. However, since this new copy of the CSECT will be first in the load module that is created, you must code an ENTRY statement.
Finally, I have not heard the term "Fractional Link", but I surmise that it is a load module which does not have all of its external references resolved. As such, it may or may not be executable depending on whether or not these unresolved modules are ever really called. If you execute a module with unresolved external references, and on of them is in fact called you will get a S0C1 abend.
To add more on this I guess fractional links are those which are linked to some other links, so that the load generated will correspond to link at top level in the hierarchy ( the composite one !!) and one thing which is sure is that there will be no corresponding load module generated for fractional links... !!
Thanks a lot . this is making more sense to me now _________________ "Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity."
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
