How can I use the dryrun parameter?

Hi Experts,

In the description of dryrun parameter, I see it can generate a dryrun report, and I tried to use the sm.cfg as below to start a dryrun servlet. But after the test team run the Load Runner script on the dryrun servlet, I cannot see any dryrun report. How can I get it?

sm.cfg --------------

sm
sm -httpPort:13087 -httpsPort:13450 -log:../logs/sm_13087_integration.log -debugnode
sm -httpPort:13089 -httpsPort:13452 -log:../logs/sm_13089_dryrun.log -debugnode -dryrun
sm -httpPort:13090 -httpsPort:13453 -log:../logs/sm_13090_debug.log -debugnode -debugdbquery:999 -RTM:3
#
# start background schedulers
#
sm system.start
sm -sync

 

Best Regards,

Robert

  • This parameter creates a log file in the server's RUN folder. Have you check the RUN folder for your report ? Search for the string, "Dry Run Report"  in the RUN folder.

    Have a look at the online help for more info. https://docs.microfocus.com/SM/9.61/Codeless/Content/parameters/reference/parameter_dryrun.htm?Highlight=dryrun

  • Thanks for the reply, I cannot find it in the RUN folder.

  • Try the most simple scenario as a check on the dryrun.

    In the RUN folder, just run the command sm -dryrun -httpPort:13089  -debugnode 

    See if you get any errors or if it now produces any log.

     

     

  • Verified Answer

    I just tried sm -dryrun -httpPort:13081 and then killed that sm command with a Ctrl-C.

    It did not generate a log in RUN folder but in sm.log. You can test if that works for you and then tried with the -log parameter to separate it from the sm.log. Not sure if dryrun needs to be the 1st parameter to work. That's the only difference I can notice at this stage.

    3400( 5300) 11/16/2018 10:19:33 RTE I Command line: sm -dryrun -httpPort:13081
    3400( 5300) 11/16/2018 10:19:33 RTE I Process sm 9.40.0015 () System: 13081 (0x784DFB00) on PC (x64 64-bit) running Windows (6.2 Build 9200) Timezone GMT 10:00 daylight Locale en_US from btp01sm55
    3400( 5300) 11/16/2018 10:19:33 RTE I Process attaching to resources with key 0x784DFB00
    3400( 5300) 11/16/2018 10:19:34 RTE I JVM successfully created
    3400( 5300) 11/16/2018 10:19:34 JRTE I Java version: 1.7.0_67
    3400( 4884) 11/16/2018 10:19:34 JRTE I Starting Memory Monitoring thread to check for memory every 15 seconds.
    3400( 4884) 11/16/2018 10:19:34 RTE I Using "utalloc" memory manager, mode [0]
    3400( 5300) 11/16/2018 10:19:36 RTE I Host network address: 16.43.98.254
    3400( 5300) 11/16/2018 10:19:36 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'sm941'.
    3400( 5300) 11/16/2018 10:19:36 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.
    3400( 5300) 11/16/2018 10:19:36 RTE I API=SQLConnect
    3400( 5300) 11/16/2018 10:19:36 RTE I Connection established to dbtype 'sqlserver' database 'smdb' user 'smAdmin'
    3400( 5300) 11/16/2018 10:19:36 RTE I Connected to Data source 'smdb' SQL server 'BTP01SM55' version: 11.0.7001 through SQL driver version: 6.3.9600 using database 'sm941' as user 'smAdmin'
    3400( 5300) 11/16/2018 10:19:36 RTE I MS SQL Server collation 'SQL_Latin1_General_CP1_CI_AS', varchar codepage 1252, comparison 196609: case insensitive, accent sensitive
    3400( 5300) 11/16/2018 10:19:36 RTE I Application Version: 9.40.0015
    3400( 5300) 11/16/2018 10:19:36 JRTE I JGroups 3.2.0.Final
    3400( 5300) 11/16/2018 10:19:38 JRTE I Setting License Information from cluster.
    3400( 5300) 11/16/2018 10:19:38 JRTE I LicenseData has been updated.
    3400( 5300) 11/16/2018 10:19:38 JRTE I Channel connected: btp01sm55:13080; address: btp01sm55-26380
    3400( 5300) 11/16/2018 10:19:38 JRTE I Timeout value in milliseconds for Jgroups remote procedure calls: 5000
    3400( 5300) 11/16/2018 10:19:38 JRTE I Service Manager Library loaded.
    3400( 5300) 11/16/2018 10:19:40 initializing LWSSO from default LWSSO configuration location
    3400( 5300) 11/16/2018 10:19:40 com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager was not initialized explicitly. Trying to initialize it implicitly from lwssofmconf.xml
    3400( 5300) 11/16/2018 10:19:40 StringEncrypter [ isUseEncryption = false] : One or any of configuration files is not provided ...
    3400( 5300) 11/16/2018 10:19:40 Building of configuration completed in 565 milliseconds.
    3400( 5300) 11/16/2018 10:19:41 Loading application from META-INF/core/wink-providers.
    3400( 5300) 11/16/2018 10:19:42 Loading application from jar:file:/C:/Program Files (x86)/HP/Service Manager 9.40/Server/RUN/lib/wink-json-provider-1.0-incubating.jar!/META-INF/wink-application.
    3400( 5300) 11/16/2018 10:19:42 JRTE I Initializing Service Manager servlet "SM 7 Servlet"
    3400( 5300) 11/16/2018 10:19:42 JRTE I Initializing Service Manager servlet "SM Servlet"
    3400( 5300) 11/16/2018 10:19:42 Loading application from META-INF/core/wink-providers.
    3400( 5300) 11/16/2018 10:19:42 Loading application from jar:file:/C:/Program Files (x86)/HP/Service Manager 9.40/Server/RUN/lib/wink-json-provider-1.0-incubating.jar!/META-INF/wink-application.
    3400( 5300) 11/16/2018 10:19:43 JRTE I Initializing Service Manager servlet "SM 7 Servlet"
    3400( 5300) 11/16/2018 10:19:43 JRTE I Initializing Service Manager servlet "SM Servlet"
    3400( 5300) 11/16/2018 10:19:43 Initializing Coyote HTTP/1.1 on http-13081
    3400( 5300) 11/16/2018 10:19:43 Starting Coyote HTTP/1.1 on http-13081
    3400( 5300) 11/16/2018 10:19:43 JRTE I Started Tomcat - HTTP port is 13081
    11/16/2018 10:19:43 RTE I CTRL-C received, terminating process
    3400( 5300) 11/16/2018 10:19:46 JRTE I HSStats is not available, to turn on use log4jDebug:com.hp.ov.sm.common.resource.HSStats
    3400( 5300) 11/16/2018 10:19:46 Stopping Coyote HTTP/1.1 on http-13081
    3400( 5300) 11/16/2018 10:19:46 RTE I -Memory : S(650616) O(309108) MAX(1357228) - MALLOC's Total(17884)
    3400( 5300) 11/16/2018 10:19:46 RTE I Thread termination in progress
    3400( 5300) 11/16/2018 10:19:46 RTE D ####### Dry Run Report #######
    3400( 5300) 11/16/2018 10:19:46 RTE I ------ Shared Memory ------
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I Shared Memory Release 9.40.15
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I Current Size 32000000
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I Segment Allocation 9018184
    3400( 5300) 11/16/2018 10:19:46 RTE I Large Block Allocation 8631552
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I Unused Space 14350264 (44%)
    3400( 5300) 11/16/2018 10:19:46 RTE I Free Space 22035056 (68%)
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I
    3400( 5300) 11/16/2018 10:19:46 RTE I Shared Memory Type Allocations Frees Allocated
    3400( 5300) 11/16/2018 10:19:46 RTE I ------------------ ----------- ----------- -----------
    3400( 5300) 11/16/2018 10:19:46 RTE I Not named 91 24 321200
    3400( 5300) 11/16/2018 10:19:46 RTE I User blocks 29 8 43008
    3400( 5300) 11/16/2018 10:19:46 RTE I Messages 0 0 0
    3400( 5300) 11/16/2018 10:19:46 RTE I Resource locks 0 0 0
    3400( 5300) 11/16/2018 10:19:46 RTE I Database Services 493 0 22352
    3400( 5300) 11/16/2018 10:19:46 RTE I Cache overhead 1 0 39936
    3400( 5300) 11/16/2018 10:19:46 RTE I Application cache 1947 51 2719888
    3400( 5300) 11/16/2018 10:19:46 RTE I DBDICT cache 1175040 1173754 4882304
    3400( 5300) 11/16/2018 10:19:46 RTE I SQL descriptor cache 2566 2236 544128
    3400( 5300) 11/16/2018 10:19:46 RTE I Join/ERD/Type cache 376 0 1033728
    3400( 5300) 11/16/2018 10:19:46 RTE I String Type cache 22194 21436 265632
    3400( 5300) 11/16/2018 10:19:46 RTE I IR Expert cache 371 0 92768
    3400( 5300) 11/16/2018 10:19:46 RTE I Diagnostic Services 0 0 0
    3400( 5300) 11/16/2018 10:19:46 RTE D Sessions PeakMemoryUsage: 1357228, MemoryUsage: 584488, MemoryOverhead:358756, TotalAllocations:17925
    3400( 5300) 11/16/2018 10:19:46 RTE D ####### End DryRun Report #######
    3400( 5300) 11/16/2018 10:19:46 RTE I Process termination cleanup complete (exit code=0)

  • Thanks Jas1, as you told, I found the Dry Run Report in sm.log. So this is a document misleading. The document told me to seek the report in RUN folder, and it is wrong.

    And thanks all the other clicks and replies to this discussion.

  • Good idea. I am reporting this to the document team. They are very responsive. There's a "Send Help Center feedback" at the bottom right of the screen if you ever want to report documentation issue.