Assembly language files dependencies provided by AWS Blu Insights rely only on the Call statement.
The call expression implies a dependency on another ASM file.
CALL filename
this expression must start at the 10th column of a line and filename
is the name of an ASM file in the project.Those statements also address an ENTRY
defined in an ASM or Cobol file.
The call on a CSECT section defined in the same file will not produce any dependency.
Similar to CALL but we have different options before the call.
As in several other dependencies we expect a margin (at least 9 character) at the beginning of each ASM line.
MCALL target
MCALL GO target
MCALL NO GO target
MCALL NO, GO target
With those statements we expect to find another ASM program but in fact, the target could be of any type..
The link created will be of type “Call”
This statement handles various options that doesn’t affect the expected dependency. With this statement, we expect to match MFS objects (generated by IMS).
CALL CBLTDLI, ISRT, ARG1, ARG2, ARG3 target
This statement will call an object named target and create a dependency of kind “IMS message invocation”.
The COPY expression implies a dependency on a CPY file from assembler.
COPY filename
where filename
is the name of an CPY file in the project.The link created will be of type “Copy”.
The LOAD expression implies a dependency on another file.
LOAD EP=filename
where filename
is the name of a file in the project.The link created will be of type “Load entry”.
In assembler there is a bunch of default operations, each one of them can be override if there is a MACRO file with the name of the operation in the project.
OPERATION ARG1 ARG2...
implies a dependency on a MACRO file named OPERATION.MACRO
or OPERATION.MAC
in your project. For those calls, we only display a link if the macro file exists, we don't handle missing macros.
The link created will be of type "Macro Call”.
In assembler, there are string that are executed as code. The PUNCH statement is an operation that executes those strings. We handle several statements in PUNCH.
The PUNCH ENTRY expression implies a dependency on another program in the project.
PUNCH 'ENTRY filename'
where filename
is the name of a file in the project.The link created will be of type “Punch entry”.
The PUNCH INCLUDE expression implies a dependency on another program in the project.
PUNCH 'INCLUDE SYSLIB filename'
where filename
is the name of a file in the project.The link created will be of type “Punch include”.
The SETAF expression implies a linking on another program in the project.
SETAF filename
where filename
is the name of a file in the project.The link created will be of type “Linkage”.
The SETCF expression implies a linking on another program in the project.
SETCF filename
where filename
is the name of a file in the project.The link created will be of type “Linkage”.
The SVC expression implies a dependency on another program in the project.
SVC filename
where filename
is the name of a file in the project.The SVC statement also references a MACRO file (.MAC or .MACRO).
The link created will be of type “Supervisor call”.
The USING expression implies a dependency on another program in the project.
USING filename
where filename
is the name of a file in the project.The link created will be of type “Using”.
The V call expression implies a linkage on another program in the project.
... R1,=V(filename)
where filename
is the name of a file in the project.This statement can be used in arguments of different instructions. =V(filename)
create a link to the targeted file.
The link created will be of type “Linkage”.