To trigger an event from Operating system(OS):
login to os with sidadm
sapevt event=<backgroup job event @ sm64> name=<sid> mshost=<hostname>
Showing posts with label an. Show all posts
Showing posts with label an. Show all posts
Sunday, 16 February 2025
Background job administration - To trigger an event from Operating system(OS)
Thursday, 24 September 2020
How to release an elastic ip to avoid unwanted billing in AWS
This will provide you procedure for Disassociate public ip which is already assigned to EC2 instance and Release public IP which is associate to AWS account. To avoid unwanted billing with unwanted public ip.
Practical steps:
- From the Elastic ip page --> Right click on the Elastic IP --> Disassociate address.
- Then the below conformation screen will appears, conform it.
By the above steps, the fixed public ip which is assigned to one EC2 will be removed. As usually for every time when EC2 instance restarts new public ip will be assigned.
By the below releasing address process:
the public ip will be removed from AWS account to avoid unwanted billing, if the public ip is not longer use.
conform it in the conformation screen.
Monday, 21 September 2020
How to make changes in assigning security groups for an existing security groups in EC2
From the EC2 instance launching page --> right click on the instance --> Networking -->Change Security Groups.
Assign or un assign security groups by checkbox &Click on Assign Security Groups.
Wednesday, 17 April 2019
Background Jobs notes 6: Event based background job scheduling
Event based background job scheduling
Based on jobs are successfully completed, (nested jobs).once the completion of one successfully job another job need to schedule.
eg:
1. After an event: ABAP program/cmd.
2.After a (predessor) job: once after completing job1--> job2
3.operation mode: only planed operation mode the BG job need to schedule.
step 2:click on Create.
step 3:provide details: --> event name
-->Description
step 4: sm36
--> provide general data
-->ABAP program( in Step)
step 5: in start condition --> choose After an event
step 6: sm37 --> check the status with Event based filter.
step 7: sm64 --> trigger the event.
eg:
1. After an event: ABAP program/cmd.
2.After a (predessor) job: once after completing job1--> job2
3.operation mode: only planed operation mode the BG job need to schedule.
Creation of Event
step 1:T-code: sm64 (Background events: overview & Administration).
step 2:click on Create.
-->Description
step 4: sm36
--> provide general data
-->ABAP program( in Step)
step 5: in start condition --> choose After an event
step 6: sm37 --> check the status with Event based filter.
step 7: sm64 --> trigger the event.
Subscribe to:
Posts (Atom)